Project Server 2003 PWA errors

[Steve Spence]

Logging in to project server via PWA I get the following under risks and
issues:

There is a problem establishing a connection with the Web server running
Windows SharePoint Services. Contact your system administrator.

Are there any common causes I can check?

 

[julie]

I just came in here to find a fix for this very problem. I found it in the
thread titled:
Setting up users in SharePoint. Here is what it said to do and it worked:
In PWA, Go to Manage Windows SharePoint Services > Manage Sites. Use the
synchronize feature on each site. If that doesn't work, let us know if you
see errors in the server application event log.

 

[Steve Spence]

I've tried the below, but see:

Error!
The account information for the Microsoft Office Project Server WSS Admin
COM+ application is incorrect.
To set the account information, run the PSCOMPlus tool installed with
Project Server, and set the Windows account that the component should run as.
For more information, refer to the Microsoft Office Project Server 2003
Installation Guide on the Microsoft Office Project Server menu (Start menu,
Programs submenu).


I've re-entered the details for PSComPlus several times and on each occasion
the problem goes away briefly and I can progress, any ideas why it appears to
be lost each time?

 

[Gary L. Chefetz [MVP]]

Steve:

How frequently does the setting get wiped out? Does this correlate with
other processes on the machine? Are there security policies in place
preventing COM+ applications from functioning correctly?

 

[Steve Spence]

Hi Gary,

I've not timed it, but I can set it one afternoon and by the morning need to
set it back up.

As to policies, none that I'm aware of.

Regards,
Steve

 

[Gary L. Chefetz [MVP]]

Steve:

In most instances where we've heard of this behavior, the culprit has been
security policies. Talk to your AD folks.

 

[Steve Spence]

Hi Gary,

Actually I've just taken over the systems side of things, so that would be me.

The only additional AD policies we have are restricted rights to run as a
service, and terminal services connections, does the project server user
need rights to do this?

Regards,
Steve

 

[Gary L. Chefetz [MVP]]

Steve:

It's not the SQL accounts that are getting you, it's the AD account you're
using to run the COM+ components.

 

[David]

Gary, thank you for the info.

We experienced the same issue after we migrated into the AD environment with
our GPO settings on our Project Server. (We run WSS on the Project Server.)

We push the GPO settings every 90 minutes. So our problem returned every
ninety minutes. Of course since testing this issue didn't take nintey
minutes, when the issue 'RE-APPEARED' the next morning, we drove ouselves
crazy looking for a batch job which was scheduled during the evening hours
which could have caused this issue.

Resetting our GPO setting worked!

Needless to say, but I will anyway, once again Dale and you have come to the
resecue!

 

[Gary L. Chefetz [MVP]]

Glad to hear we got you pointed in the right direction. Was it prohibition
on running as a service that was knocking them out, or something else?

 

[David]

Our AD server guy indicated that the domain user account specified in the
Project Install needs GPO settings modified to allow the ‘Logon as a batch
job’ security right. --
It's a little more than I need to know but hey.....we're up and running.
Hope that explanation helps.
David