A
Andrzej Lipski
Some of our users are using PWA to access our Project 2002
Server. Everything has been fine for us until about 6
months ago when we rebuilt our Project server. We
imported the project data back in and everything appears
to be working for a few months.
Now when some of our of our PWA users attempt to view an
Issue for one of their assigned projects the form freezes
and they can't do anything with the browser until exactly
60 seconds later.
Looking at the temporary Internet Files, we found that
everything has resolved and after the browser "thaws" no
new updates and access are made to the files located in
cache, and the Issue form does display in the browser.
We just get slow response for every Issue they attempt to
view.
Now we sniffed the packets being passed between the client
and the server and we found that those users that are not
having problems are actually doing an HTTP GET, while the
PWA users that are having problems are doing and HTTP POST
to view the Issue.
Also we found that when we provide the FULL URL into the
browser's address bar (including the Source =, and the
PCUrl data), rather than just using the IssuesShell.asp we
don't have any problems viewing any Issues for that
particular project. Once we navigate back to the Main
Issues page with the Project table, the Source and PCURL
data is reset and we start experiencing the same problems
all over again.
We have already applied the hotfix for KB812643 as a
solution for this problem about 4 or 5 months ago, and are
full up to date for our hotfixes.
Any suggestions are greatly appreciated. Thanks
Andrzej
Server. Everything has been fine for us until about 6
months ago when we rebuilt our Project server. We
imported the project data back in and everything appears
to be working for a few months.
Now when some of our of our PWA users attempt to view an
Issue for one of their assigned projects the form freezes
and they can't do anything with the browser until exactly
60 seconds later.
Looking at the temporary Internet Files, we found that
everything has resolved and after the browser "thaws" no
new updates and access are made to the files located in
cache, and the Issue form does display in the browser.
We just get slow response for every Issue they attempt to
view.
Now we sniffed the packets being passed between the client
and the server and we found that those users that are not
having problems are actually doing an HTTP GET, while the
PWA users that are having problems are doing and HTTP POST
to view the Issue.
Also we found that when we provide the FULL URL into the
browser's address bar (including the Source =, and the
PCUrl data), rather than just using the IssuesShell.asp we
don't have any problems viewing any Issues for that
particular project. Once we navigate back to the Main
Issues page with the Project table, the Source and PCURL
data is reset and we start experiencing the same problems
all over again.
We have already applied the hotfix for KB812643 as a
solution for this problem about 4 or 5 months ago, and are
full up to date for our hotfixes.
Any suggestions are greatly appreciated. Thanks
Andrzej