PWA access post SP2

[Todd Hicks]

I've found a thread or two that I had hoped would solve my problem but I have
thus far been unsuccessful.

I have applied SP2 to my Project Server 2003 installation and now PWA is
giving me the 5001 Project server database cannot be accessed error.
Nothing has changed other than applying the service pack.
oh, and the EditSite tool tests pass.
Any help?

Todd

 

[Gaurav Wason]

Check the database if it is on single user mode or something. Someone else in
news group had the issue that his database was set in single user mode after
installing sp2.

Thanks

 

[Todd Hicks]

Yeah, checked that. Database is not in single user mode.
The app pool has valid credentials and the MSProjectServerUser and
MSProjectUser account have not problems accessing.

Todd

 

[KTreston]

Try logging in with the administrator account and the password initially
used when project server was installed. You'll need to accept the EULA again
just as you did initially.

K Treston
--

 

[Gary L. Chefetz [MVP]]

Todd:

Please describe the steps you took to install the SP. It seems as though
many folks miss some needed steps when doing this.

 

[Todd Hicks]

Gary,
I'm pretty religious about following documentation.
per the instructions,
I executed all the steps below using my network credentials, which is nested
into the local admins group on each system

1. Upgrade the database: I ran the ubgdb112.cmd against the ProjectServer
database on the SQL server using the appropriate arguments for windows
authentication.
2. Install the Project Server service pack:
double click ProjectServer2003SP2-KB887621-FullFile-ENU.exe on the project
server
3. Update the Project template on the SPS/WSS server

Now immediately after I completed step two, i discovered a new app pool that
was configured with an identity of Network Service, and that the Application
at the ProjectServer virtual dir had been renamed and was now running in the
new app pool. Now i did change the app pool identity to that of the original
app pool, and i have since tried switching back and forth between the two
identities, with the same results in both cases.

Todd

 

[Todd Hicks]

I've taken the added steop of recreating the MSProjectUser and the
MSProjectServerUser SQL logins to be sure the passwords were all synch'd.
Ran the EditSite tool again, with positive results.
Todd

 

[Gaurav Wason]

Did you treid this article.

http://support.microsoft.com/?scid=kb;en-us;839773&spid=2525&sid=global

 

[Todd Hicks]

Yup, followed procedure two in that article

 

[Todd Hicks]

Now we are getting somewhere:

found these in my application event log:

Reporting queued error: faulting application PJSCHSVC.EXE, version
11.0.2003.816, faulting module ntdll.dll, version 5.2.3790.0, fault address
0x00007a6d.


Component: ConnectSvc
File:
C:\Office\dev\project\WebClient\source\server\connectorsvc\connectorsvc.cpp
Line: 979
Error Number: 0x80200110
Description: <Description><![CDATA[Invalid Registry configuration, the
service is stopping]]></Description>


Component: ConnectSvc
File:
C:\Office\dev\project\WebClient\source\server\connectorsvc\connectorsvc.cpp
Line: 890
Error Number: 0x80200110
Description: <Description><![CDATA[Invalid Registry
Configuration]]></Description>
___________________________________

Component: ConnectSvc
File:
C:\Office\dev\project\WebClient\source\server\connectorsvc\ListenInfo.cpp
Line: 130
Error Number: 0x80200110
Description: <Description><![CDATA[Reading from registry
failed]]></Description>


Component: ConnectSvc
File:
C:\Office\dev\project\WebClient\source\server\connectorsvc\ListenInfo.cpp
Line: 209
Error Number: 0x80200110
Description: <Description><![CDATA[Project Server URL not specified! The
service cannot continue to run, shutting down.]]></Description>

 

[Todd Hicks]

So these errors occur when i try to start the Project Server Connector
Service, and If i understand them correctly it would seem that either the
registry key is inaccessible or corrupt. Inclined to think the former.

 

[Todd Hicks]

Well, it would seem that the connector service errors are a symptom of the
same issue. Somewhere, someone doesn't have permissions to something.
Forunately this is my predeployment test environment. It would still just be
wrong if i have to reinstall Project server to get this to work. and that's
not something I want to have to do in production.

 

[Todd Hicks]

Back on task this morning and the situation is this:
When attempting to access PWA, I'm challenged for username/password. My
domain credentials are accepted. PWA then presents the web form login withe
the 5001 "Project Server database cannot be accessed" error.

PWA, SQL and SPS are each on separate servers. I have installed SP2 per the
instructions. I have recreated the SQL logins "MSProjectUser" and
"MSProjectServerUser".

Anybody have ideas?