VBScript error when accepting task updates from Resources

[Christina]

I have a PM that just started receiving the following error when she attempts
to accept task updates from her resources:

VBScript : Microsoft Office Project Web Access 2003
You need Microsoft Project Professional 2002 or Microsoft Office Project
Professional 2003 in order to perform this action.

If you are using either of these versions, verify that a correct account for
the Project Server has been set up and selected by pointo to Enterpirise
Options (Tools Menu) and then clicking Microsoft Office Project SErver
Accounts. If you are unable to start Project with the correct account,
contact your server administrator to make sure that the enterprise features
have been enabled on the Project Server.


We are running Project Server 2003 and Microsoft Project Pro 2003. I have
verified that her project server account works and tested the connection from
Microsoft project and it was successful. I even created a brand new account
just to see if the only one was corrupt (?). I logged into her computer
under my username and had the same problem when trying to accept a task
update but I don't have these problems on my own PC. So I'm thinking it's
PC-specific?

Does anyone have any thoughts???

Thanks!
Christina

 

[James Fraser]

I have a PM that just started receiving the following error when she attempts
to accept task updates from her resources:

VBScript : Microsoft Office Project Web Access 2003
You need Microsoft Project Professional 2002 or Microsoft Office Project
Professional 2003 in order to perform this action.

Make sure that the account set up in Project Professional uses the
_exact_ same URL as what the user is using to access PWA. If one is
http://server/projectserver and the other is https://server/projectserver
or any other mis match, you will get this error. For some users is a
sporadic error, because they may use different shortcuts or type in
the PW URL sometimes, so it may be slightly different from time to
time.

Other common differences include: http://servername.domain.com/projectserver
instead of http://servername/projectserver


James Fraser

 

[Christina]

James-

That turned out to be the issue. Strange. I'm guessing the user recently
changed her IE favorite for PWA to the other URL (?) In any event, after
changing her favorite to point to the same URL as was entered in Project, she
is now able to accept udpates without receiving that error.

Thank you so much for your help!
Christina