T
Tomasz Zajaczkowski
I've got Project Server 2003 installed on Windows 2003 Standard Server (with
SQL 2000 SP3 and Windows SharePoint Services installed on the same machine).
I've configured everything and Project Web Access is fully working (I use
windows authentication). I can also connect from Project Professional 2003
installed on the same machine.
However so far I'm not able to connect from any other machine having Project
Professional 2002 or 2003. I always get the message: "Cannot connect.
Project was unable ..... enterprise features anabled."
I've run a network trace and the HTTP requests sent from both Project
Professional instances are exactly the same (with some insignificant
differences like SQL PID and date/time difference).
I've also checked the SQL trace and all my Project Professional instances
run on all the machines can connect to the database. The first part of the
traces is exactly the same for machines which can and cannot connect (this
one I believe is executed by the Project Server). The secondca, ptured only
from the remote machines, seems fine as well. The only thing I can see there
is that Project is trying to read from MSP_PROJECTS_PROJ_READVIEW table
which is empty - however this does not seem to cause any problems when
accessing from the Project installed on the server machine itself - the
trace does not show any attempt to read this table. Project Professional run
on the server does not seem to connect to DB on its own behalf at all. All
the DB connections in this case use MSProjectServerUser only. When you
connect remotely it uses MSProjectUser. Thus I've even granted all the DB
rights (MSProjectServerRole and DB owner) to MSProjectUser with no result.
Looking at this group I've noticed some people had problems with regional
settings. However in my case this should not be a problem as I have all of
the PCs running with English US (or UK) settings.
The only strange thing I have in my configuration is that I have disabled
TCP/IP connections for SQL Server. I left named pipes only. However as I can
see this should not affect anything as my Project Professional instances can
connect to it.
I would appreciate any help or suggestions where to look for the problem.
Regards,
Tomasz Zajaczkowski
SQL 2000 SP3 and Windows SharePoint Services installed on the same machine).
I've configured everything and Project Web Access is fully working (I use
windows authentication). I can also connect from Project Professional 2003
installed on the same machine.
However so far I'm not able to connect from any other machine having Project
Professional 2002 or 2003. I always get the message: "Cannot connect.
Project was unable ..... enterprise features anabled."
I've run a network trace and the HTTP requests sent from both Project
Professional instances are exactly the same (with some insignificant
differences like SQL PID and date/time difference).
I've also checked the SQL trace and all my Project Professional instances
run on all the machines can connect to the database. The first part of the
traces is exactly the same for machines which can and cannot connect (this
one I believe is executed by the Project Server). The secondca, ptured only
from the remote machines, seems fine as well. The only thing I can see there
is that Project is trying to read from MSP_PROJECTS_PROJ_READVIEW table
which is empty - however this does not seem to cause any problems when
accessing from the Project installed on the server machine itself - the
trace does not show any attempt to read this table. Project Professional run
on the server does not seem to connect to DB on its own behalf at all. All
the DB connections in this case use MSProjectServerUser only. When you
connect remotely it uses MSProjectUser. Thus I've even granted all the DB
rights (MSProjectServerRole and DB owner) to MSProjectUser with no result.
Looking at this group I've noticed some people had problems with regional
settings. However in my case this should not be a problem as I have all of
the PCs running with English US (or UK) settings.
The only strange thing I have in my configuration is that I have disabled
TCP/IP connections for SQL Server. I left named pipes only. However as I can
see this should not affect anything as my Project Professional instances can
connect to it.
I would appreciate any help or suggestions where to look for the problem.
Regards,
Tomasz Zajaczkowski