MS Project 2003 Pro SP1 Post-Install Errors

[J]

All,

We implemented MSP 2003 Pro SP1 and the post-SP1 hotfix in our MSP
2003 environment on all of our servers (2 web, 1 app, 1 DB - WIN2K,
IIS5.0, MDAC 2.7 SP1) and all clients on Saturday, 10/30/04. For the
most part, all seems to be going well, with the exception of some
event log entries.

Immediately following the installation, exactly every 30 minutes the
combination of 2 errors (0x800a0cc1, 0x800a0e78) is written to the
event log (below). Also, the viewdrop folder has not emptied since
this upgrade. The views processor has been restarted several times
and the server rebooted once. I've since moved the xml docs out of
viewdrop and have been manually feeding it a couple at a time, which
may be working to process the docs, but very slowly.


Event Type: Error
Event Source: Microsoft Project Server Tracing Eventlog Provider
Event Category: None
Event ID: 2
Date: 11/10/2004
Time: 7:56:11 AM
User: NT AUTHORITY\SYSTEM
Computer: PWN400A0430
Description:
Component: PjSvrNPE
File: C:\Office\dev\project\WebClient\source\server\pjnpe\CPjSvrNPE.cpp
Line: 116
Error Number: 0x800a0cc1
Description: <Description><![CDATA[Assert Detected. The error code was
also included.]]></Description>
___________________________________

Component: ADODB.Fields
Description: <Description><![CDATA[Item cannot be found in the
collection corresponding to the requested name or
ordinal.]]></Description>



Event Type: Error
Event Source: Microsoft Project Server Tracing Eventlog Provider
Event Category: None
Event ID: 2
Date: 11/10/2004
Time: 7:56:11 AM
User: NT AUTHORITY\SYSTEM
Computer: PWN400A0430
Description:
Component: PjSvrNPE
File: C:\Office\dev\project\WebClient\source\utility\pjrecordsetutil.cpp
Line: 105
Error Number: 0x800a0e78
Description: <Description><![CDATA[Assert Detected. The error code was
also included.]]></Description>
___________________________________

Component: ADODB.Recordset
Description: <Description><![CDATA[Operation is not allowed when the
object is closed.]]></Description>

Anyone have any ideas? Any help is appreciated.

Jason

 

[J]

For those interested, the problem appears to be related to the
historical MSP DB that was resident in our production environment. It
had not yet been migrated with the SP1 procedures. After running the
SP1 DB upgrade on this DB, the event log errors went away.