You receive error messages when you publish a plan or an assignment when you work with Project Server 2002 or with Project Server 2003 (903093)


The information in this article applies to:

  • Microsoft Office Project Server 2003
  • Microsoft Project Server 2002

SYMPTOMS

You may experience the following issues when you work with Microsoft Office Project Server 2003 or with Microsoft Project Server 2002:
  • When you publish a Microsoft Project plan to a computer that is running Project Server 2003, you receive the following error message:
    -2146825023 (0x800A0CC1)

    Remote ADO Error: Could not find the object in the collection corresponding to the requested name or ordinal reference.
    Additionally, the following error may be logged in the error log:

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

  • When you click Manage Users and Groups on the Admin page in Microsoft Project Web Access, you receive the following Visual Basic Editor script error message:
    A run time error has occurred.
    Do you wish to debug?

    Line 1941
    Error: Internet Server error: Object /Module not found
    url:http://localhost/...user.asp
  • When you publish a new assignment or a changed assignment, you receive the following error message:
    -2147467259 (0x80004005)

    Unspecified Error.
    Additionally, the following error may be logged in the event log:

    Component: PjMsgHlr
    File: C:\Office\devsp\project\WebClient\source\server\pjmsghlr\MsgHandler.cpp
    Line: 588
    Error Number: 0x80004005
    Description: <Description><![CDATA[Assert Detected. The error code was also included.]></Description>

    Component: PjMsgHlr
    File: C:\Office\devsp\project\WebClient\source\server\pjmsghlr\updatedb.cpp
    Line: 2386
    Error Number: 0x80004005
    Description: <Description><![CDATA[Assert Detected. The error code was also included.]></Description>

    Component: PjMsgHlr File: C:\Office\devsp\project\WebClient\source\server\pjmsghlr\updatedb.cpp
    Line: 4828
    Error Number: 0x80004005
    Description: <Description><![CDATA[Assert Detected. The error code was also included.]></Description>

    Component: PjMsgHlr File: C:\Office\devsp\project\WebClient\source\server\pjmsghlr\updatedb.cpp
    Line: 4682
    Error Number: 0x80004005
    Description: <Description><![CDATA[Assert Detected. The error code was also included.]></Description>

  • When you click Save to save the changes that you made to the Manage Security category on the Admin page in Project Server, you receive the following error message:
    VBScript: Project Server 2003

    An error occurred while completing the operation
    Event ID: 2 - Component pjsvr security
    0x800040E14
  • When you try to see the tasks in a published project plan in Project Web Access, you receive an error message that is similar to the following:
    There is no information to display in this view.

CAUSE

The issues that are described in the "Symptoms" section may occur if the following conditions are true:
  • You installed a hotfix or a service pack for Project Server 2003 or for Project Server 2002.
  • You did not run the scripts that are included with the hotfix or with the service pack that you installed.

RESOLUTION

To resolve these issues, run the upgrade database .cmd script file that is included with the service pack or with the hotfix that you installed.

Note If the database is a partitioned database, run the script against each Project Server database.

To run the upgrade database .cmd script file from a command line, follow these steps:
  1. Click Start, click Run, type cmd in the Open box, and then click OK.
  2. At the command prompt, type cd folder.

    Note In this command, folder is the folder to which you extracted the service pack or the hotfix package.
  3. At the command prompt, type the following command:

    filename.cmd sql_server_name database_name logon password

    Or, if you logged on by using a user account that uses Windows authentication to connect to Microsoft SQL Server, type the following command at the command prompt:

    filename.cmd sql_server_name database_name

    Notes
    • In these commands, filename is the name of the upgrade database .cmd script file. For example, type upgdb111.cmd.
    • If you do not include the system administrator account logon name and the password, the command file assumes Windows authentication is used to connect to SQL Server. If you supply only the SQL server name, the command files assumes that the database name is "ProjectServer".
Modification Type:MinorLast Reviewed:11/2/2005
Keywords:kbsetup kbtshoot kbprb KB903093 kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.