J
Jonathan Yong
I have a issue with a recent Project Server 2003 deployment project.
When I save and publish a project using
Project Pro from a client PC to the server, sometimes it return me a
error like the following :
-----------------------------------------
The server at 'http://someserver/projectserver' return the following
error to Project.
HTTP/1.1 100 Continue 0x000000000x004e045b
-----------------------------------------
Despite the error message, the project actually get saved to the
database. However, one very serious consequence is when a project
manager want to do task update approval.
When the project manager accept task update from the resource in Web
Access, the project will be opened in Project Pro and the update is
saved to the project plan. When the above error occur, although the
changes is saved to the project plan and database, it trigger another
error in the Web Access. Web Access displayed a message saying that the
update is not done and the task update is still in the waiting for
approval state.
When I did the test in one of the user PC, that user almost have no
chance of getting any of the task update to be approved.
This error occur quite often when saving and publishing project and it
only happen when I do this from a client PC. If I save and publish
project from the server itself, I won't get this error at all.
I did monitor the server utilization. But I notice even when I am saving
a project to the server, the CPU utilization on the server remail very
low and there is still plenty of memory. The CPU utilization only bump
up when the view notification service kick in.
I suspect this could be a network problem. Has anyone encounter this
problem before ? Is there any way or tools to find out whether it is in
fact a network performance issue ?
We are using two server deployment. One is running SQL Server 2000 SP3a
on Windows Server 2003 SP1. The other server is running Project Server
2003 SP1, WSS SP1, IIS6 and Windows Server 2003 SP1.
When I save and publish a project using
Project Pro from a client PC to the server, sometimes it return me a
error like the following :
-----------------------------------------
The server at 'http://someserver/projectserver' return the following
error to Project.
HTTP/1.1 100 Continue 0x000000000x004e045b
-----------------------------------------
Despite the error message, the project actually get saved to the
database. However, one very serious consequence is when a project
manager want to do task update approval.
When the project manager accept task update from the resource in Web
Access, the project will be opened in Project Pro and the update is
saved to the project plan. When the above error occur, although the
changes is saved to the project plan and database, it trigger another
error in the Web Access. Web Access displayed a message saying that the
update is not done and the task update is still in the waiting for
approval state.
When I did the test in one of the user PC, that user almost have no
chance of getting any of the task update to be approved.
This error occur quite often when saving and publishing project and it
only happen when I do this from a client PC. If I save and publish
project from the server itself, I won't get this error at all.
I did monitor the server utilization. But I notice even when I am saving
a project to the server, the CPU utilization on the server remail very
low and there is still plenty of memory. The CPU utilization only bump
up when the view notification service kick in.
I suspect this could be a network problem. Has anyone encounter this
problem before ? Is there any way or tools to find out whether it is in
fact a network performance issue ?
We are using two server deployment. One is running SQL Server 2000 SP3a
on Windows Server 2003 SP1. The other server is running Project Server
2003 SP1, WSS SP1, IIS6 and Windows Server 2003 SP1.