D
Dominic
was working with a client where I had installed Project Server 2003 for them
with SharePoint and SQL Server on a separate Server. On completion of the
install I tested the instance and all functionality worked without problems.
Subsequent to my attending and installing the client changed the port details
for Project Server in IIS as they had another application using Port 80.
We are now having real problems with functionality in Project Web Access.
Trying to add people to groups other than the Team Member group proved
impossible, clicking on save changes after adding someone to a group or after
modifying their details as a user resulted in the process stalling and in
some instances IE itself ended up not responding. We changed the port details
back to Port 80 and this resolved the issue as far as editing user details,
making changes resulted in the changes being saved instantaneously.
Whilst the original problem appeared to have been resolved by changing back
to the original Port 80 setting some of the other functionality in the
Project Web Access Browser still failed to respond. Attempting to view the
resources section resulted in failure each time. Using Project Server
Accounts in Project Pro 2003 resulted in a long wait before the Project 1
Gantt Chart was displayed. Trying to access the SharePoint sites from
Documents, Risks or Issues menu took a very long time as well. In manage
Enterprise features we could edit the OLAP details page but could not get
"Check-In" or Versions sections to respond. The behaviour was gloriously
inconsistent, some menu items in PWA responded instantaneously whereas others
either took forever or failed.
Does anyone here have any suggestions as to where to look to resolve these
issues as at present they are severely compromising the clients adoption of
the tool.
with SharePoint and SQL Server on a separate Server. On completion of the
install I tested the instance and all functionality worked without problems.
Subsequent to my attending and installing the client changed the port details
for Project Server in IIS as they had another application using Port 80.
We are now having real problems with functionality in Project Web Access.
Trying to add people to groups other than the Team Member group proved
impossible, clicking on save changes after adding someone to a group or after
modifying their details as a user resulted in the process stalling and in
some instances IE itself ended up not responding. We changed the port details
back to Port 80 and this resolved the issue as far as editing user details,
making changes resulted in the changes being saved instantaneously.
Whilst the original problem appeared to have been resolved by changing back
to the original Port 80 setting some of the other functionality in the
Project Web Access Browser still failed to respond. Attempting to view the
resources section resulted in failure each time. Using Project Server
Accounts in Project Pro 2003 resulted in a long wait before the Project 1
Gantt Chart was displayed. Trying to access the SharePoint sites from
Documents, Risks or Issues menu took a very long time as well. In manage
Enterprise features we could edit the OLAP details page but could not get
"Check-In" or Versions sections to respond. The behaviour was gloriously
inconsistent, some menu items in PWA responded instantaneously whereas others
either took forever or failed.
Does anyone here have any suggestions as to where to look to resolve these
issues as at present they are severely compromising the clients adoption of
the tool.