M
MXE02332
Hi everybody,
I met really strange behavior of Project Web Access (PWA) on Project Server
2007.
I logged on PWA with the user called PrjSrvAdmin which is the install user
of Project Server 2007 and participates in AD's Domain Admins group. Then I
created a PWA user called 'Test PM' based on an AD account in Domain Users
group.
Then PrjSrvAdmin added 'Test PM' to 'Project Managers' group of PWA.
I logged on a PC with 'Test PM' AD account, started Project Professional
2007 which is configured to connect to the Project Server 2007, created a new
project file, assigned some tasks to 'Test PM' himself and 'PrjSrvAdmin',
saved and published the new project file to the Project Server 2007.
And 'Test PM' started PWA with IE 6.0. Naturally I saw some tasks assigned
to 'Test PM' on the top page of PWA.
Then I moved to 'My Tasks' page and click the name of any task assigned to
'Test PM', I always got the 403 error page. The 403 error page is not
customized error page of Share Point Services but the non-customized 403
error page of IE 6.0.
When I clicked 'New' -> 'Task' menu, I also got the same non-customized 403
error page of IE.
But when I clicked the upsidedown small triangle of any task assigned to
'Test PM', I could add/edit a memo to the task without seeing 403 error page.
Then I logged on PC with PrjSrvAdmin account, opened PWA with IE and added
'Test PM' both to 'Project Managers' group and 'Administrators' group. Now
'Test PM' is one of 'Administrators' of PWA.
Then I logged on PC with 'Test PM' account, opened PWA and click any task
assigned to 'Test PM', AGAIN I saw non-customized 403 error page.
I tried to make all other resources of the test project participate in
'Administrators' group of PWA and did the same thing. But I always got the
same non-customized 403 error page.
But only when I logged on PC with 'PrjSrvAdmin' account and opened PWA, I
didn't get the 403 error page by trying to edit the tasks assigned to
'PrjSrvAdmin'.
This means only the Project Server 2007 install user (PrjSrvAdmin) can edit
his own tasks on PWA. So PWA is now totally useless for us.
Why do this kind of strange things happen?
Project Server2007 and PWA is installed on Windows 2003 Server Standard SP1.
The Project Server 2007 is installed on the same machine of SQL 2005
Standard and it is the only Project Server 2007 in our company's network.
When I installed these products, I exactly followed Project Server 2007
Setup manual downloaded from Microsoft web site.
In our company, we are running thre previous version of Project Server with
Project Professional 2002 for about 2 years and no 403 error problem at all.
The previous version of Project Server is installed on the different servers
from those for Project Server 2007.
Could anyone give me a suggestion?
Best regards,
I met really strange behavior of Project Web Access (PWA) on Project Server
2007.
I logged on PWA with the user called PrjSrvAdmin which is the install user
of Project Server 2007 and participates in AD's Domain Admins group. Then I
created a PWA user called 'Test PM' based on an AD account in Domain Users
group.
Then PrjSrvAdmin added 'Test PM' to 'Project Managers' group of PWA.
I logged on a PC with 'Test PM' AD account, started Project Professional
2007 which is configured to connect to the Project Server 2007, created a new
project file, assigned some tasks to 'Test PM' himself and 'PrjSrvAdmin',
saved and published the new project file to the Project Server 2007.
And 'Test PM' started PWA with IE 6.0. Naturally I saw some tasks assigned
to 'Test PM' on the top page of PWA.
Then I moved to 'My Tasks' page and click the name of any task assigned to
'Test PM', I always got the 403 error page. The 403 error page is not
customized error page of Share Point Services but the non-customized 403
error page of IE 6.0.
When I clicked 'New' -> 'Task' menu, I also got the same non-customized 403
error page of IE.
But when I clicked the upsidedown small triangle of any task assigned to
'Test PM', I could add/edit a memo to the task without seeing 403 error page.
Then I logged on PC with PrjSrvAdmin account, opened PWA with IE and added
'Test PM' both to 'Project Managers' group and 'Administrators' group. Now
'Test PM' is one of 'Administrators' of PWA.
Then I logged on PC with 'Test PM' account, opened PWA and click any task
assigned to 'Test PM', AGAIN I saw non-customized 403 error page.
I tried to make all other resources of the test project participate in
'Administrators' group of PWA and did the same thing. But I always got the
same non-customized 403 error page.
But only when I logged on PC with 'PrjSrvAdmin' account and opened PWA, I
didn't get the 403 error page by trying to edit the tasks assigned to
'PrjSrvAdmin'.
This means only the Project Server 2007 install user (PrjSrvAdmin) can edit
his own tasks on PWA. So PWA is now totally useless for us.
Why do this kind of strange things happen?
Project Server2007 and PWA is installed on Windows 2003 Server Standard SP1.
The Project Server 2007 is installed on the same machine of SQL 2005
Standard and it is the only Project Server 2007 in our company's network.
When I installed these products, I exactly followed Project Server 2007
Setup manual downloaded from Microsoft web site.
In our company, we are running thre previous version of Project Server with
Project Professional 2002 for about 2 years and no 403 error problem at all.
The previous version of Project Server is installed on the different servers
from those for Project Server 2007.
Could anyone give me a suggestion?
Best regards,