Resolving Project Server Spooler Errors

Errors received during publish operations to the Project Server database from Project Professional are displayed in the Microsoft Office Project Server Spooler dialog box. Each error identified by the Project Server Spooler includes the following information:
  • Message TypeThe publishing operation that failed.
  • ErrorA short description of the error and the error code.
  • TimeThe time of the error.
  • Project FileThe name of the file associated with the error.
  • ServerThe path name for the computer running Project Server 2003 that is interacting with Project Professional at the time of the error.
  • ManagerThe resource running Project Professional at the time of the error.
  • Affected User Account(s)The user account or user accounts affected by or causing the error.

Project Server Spooler Errors

A variety of errors can be reported in the Project Server Spooler. This section describes the most common errors, and provides recommendations for each. Project Server Spooler errors are listed in numerical order by error code; for example, 0x8c040003, 0x8c04000d,and so on. The error code can be found at the beginning of each Project Server Spooler error description.
NoteDATABASE and SYSTEM ERROR errors do not share the same pattern as the rest of the Project Server Spooler errors. To determine the cause of these types of errors, you will need to look in the Event Log for Project Server 2003.

Generic Error During Database Access or Update (0x8c040003)

The Project Server Scheduled Process Service failed to connect to the Project Server database.

Possible Causes

  • The settings on the computer running Project Server 2003 are incorrect.
  • There is a (temporary) database problem on the server hosting the Project Server database.
  • There is a general (temporary) system or services problem.

To resolve this Project Server Spooler error

  1. Ensure that all Project Server services are functioning correctly. Restart any Project Server service that is not functioning correctly. To determine which services may need to be restarted, analyze the Event Log on the computer running Project Server 2003. In some cases, you will need to restart the computer running Project Server 2003.
  2. When you are finished, retry the publishing operation that failed.

Data Corruption in Project Server Database (0x8c040004)

The MSP_WEB_ADMIN or MSP_WEB_RESERVED_DATA tables have been corrupted, or contain more than one record.

To resolve this Project Server Spooler error

  • Restore the records in the MSP_WEB_ADMIN and/or the MSP_WEB_RESERVED_DATA tables.

MSP_WEB_ADMIN Table Not Initialized (0x8c040005)

The MSP_WEB_ADMIN table has been corrupted or contains more than one record.

To resolve this Project Server Spooler error

  • Restore the record in the MSP_WEB_ADMIN table.

Invalid Resource Name (0x8c04000b)

The name of the resource involved with a publishing operation is invalid.

Possible Causes

  • The name of the resource involved in a publishing operation is empty, contains spaces, or contains invalid characters (a list separator, for example).

To resolve this Project Server Spooler error

  1. Verify that the resource names involved in a publishing operation are valid. Fix all invalid resource names.
  2. When you are finished, retry the publishing operation that failed.

Domain Validation of Windows Account Failed (0x8c04000c)

The Windows account used by a publishing operation failed to validate with the computer running Project Server 2003.

Possible Causes

  • The Windows account has the wrong domain or user name.
  • The domain is unavailable for user validation at the time of the publishing operation.

To resolve this Project Server Spooler error

  1. Verify that the domain and user names are correct and that the domain is available.
  2. When you are finished, retry the publishing operation that failed.

Resource Already Exists (0x8c04000d)

A resource account already exists in the Project Server database. Duplicate resource accounts are not allowed.

Possible Causes

  • The information used by a user account associated with a publishing operation already exists for another user in the Project Server database.

To resolve this Project Server Spooler error

  1. Check the MSP_WEB_RESOURCES table in the Project Server database for duplicate resources.
  2. In Project Professional, point to Tools and select Options to open the Options dialog box. On the General tab, ensure that the resource does not conflict with an existing Windows or Project Server user account in the Project Server database.
  3. Add the Windows User Account field to the Resource Sheet view in Project Professional. This will help to identify the resource names and minimize the risk of saving duplicate resources.

Windows Authentication Only (0x8c040014)

If Project Server 2003 is configured to allow only Windows authentication, this error will be generated when a user attempts to add Project Server user accounts.

Possible Causes

  • Project Server 2003 is configured to accept Windows authentication only.

To resolve this Project Server Spooler error

  • If your organization requires that non-Windows authenticated users be able to log on to the computer running Project Server 2003 by using Project Professional, configure the authentication method as either Project Server or Mixed.

Project Server Authentication Only (0x8c040015)

If Project Server 2003 is configured to allow only Project Server user authentication, this error will be generated when a user attempts to add Windows user accounts.

Possible Causes

  • Project Server 2003 is configured to accept Project Server authentication only.

To resolve this Project Server Spooler error

  • If your organization requires that non-Project Server authenticated users should be allowed to log on to the computer running Project Server 2003 by using Project Professional, configure the authentication method as either Windows or Mixed.

All Authentication Types Disallowed (0x8c040016)

Both Windows and Project Server user accounts are unable to authenticate to the computer running Project Server 2003.

Possible Causes

  • There is a database corruption error. Contact your Project Server administrator and/or check the Project Server Event Viewer to determine the error.

To resolve this Project Server Spooler error

  • Restore the correct value for user authentication in the WADMIN_AUTHENTICATION_TYPE field in the MSP_WEB_ ADMIN table in the Project Server database.

Manager Not Allowed to Create a New Account (0x8c040017)

You will get this error if you attempt to create a duplicate user account or a user account that is not specified correctly. This error can also occur when you attempt to publish projects to the Project Server database from Project Professional while you are in offline mode (not connected to the computer running Project Server 2003).

Possible Causes

  • The domain\user name combination for the resource is specified incorrectly.

To resolve this Project Server Spooler error

  1. Double-check that you have specified the correct domain\user name combination for the resource
  2. Log on to Project Web Access as an administrator. Click Admin, and then click Manage Organization. Allow the Create Manager Accounts from Microsoft Project and Create Accounts from Microsoft Project permissions. Close Project Professional.
  3. Restart Project Professional and connect to the computer running Project Server 2003.

Beta or Evaluation Version Has Expired (0x8c040027)

A beta or evaluation version of Project Server has expired.

Possible Causes

  • Beta and evaluation versions of Project Server 2003 are designed to expire after 90 days.

To resolve this Project Server Spooler error

  • Install a non-beta or non-expiring version of Project Server 2003.

Manager Requires Authentication for Publish Operation (0x8c040028)

This error occurs when a project manager's user account does not exist (in the Project Server database) and when creating accounts during publishing is not allowed.

Possible Causes

  • A project manager is attempting to publish a project to the Project Server database when the project manager does not have a user account (either Project Server or Windows authenticated) in the Project Server database.

To resolve this Project Server Spooler error

  • Create the user account for the project manager by using Project Web Access.

Insufficient Manager Permissions for Publish (0x8c040029)

The user does not have permission to publish projects to the Project Server database from Project Professional.

Possible Causes

  • The user has not been granted the Save Project category permission in Project Web Access.
  • The user does not belong to a Project Server security category that has been granted the Save Project category permission.

To resolve this Project Server Spooler error

  • Grant the Save Project permission to the user or to a category of which the user is a member.

Windows Account Already Exists (0x8c040031)

You cannot create duplicate Windows user accounts in Project Server 2003. For all Windows authenticated user accounts, the Windows User Account and E-mail fields must be unique to a single user.

Possible Causes

  • A resource with the same Windows User Account and E-mail information already exists in the Project Server database.

Session Has Expired (0x8c040032)

The connection to the computer running Project Server 2003 was inactive for too long or has been terminated.

Possible Causes

  • The connection to the computer running Project Server 2003 expired because it was inactive.

To resolve this Project Server Spooler error

  • Repeat the previous publishing operation to initiate a new connection to the computer running Project Server 2003.
– or –
Increase server session expiration time.
NoteFor more information about increasing the server session expiration time, see the section \Configuration\SessionMgr in Appendix F, Project Server Registry Settings, Services, and Application Folders, of the Microsoft Office Project Server 2003 Administrator's Guide.

Cannot Create Manager Account From Project Professional (0x8c04003c)

A user has attempted to create a manager account, but does not have permission to create accounts in the Project Server database by using Project Professional.

Possible Causes

  • By default, Project Server 2003 does not allow users to create user accounts in the Project Server database by using Project Professional. The Create Accounts from Microsoft Office Project, Create Accounts when Delegating Tasks, and Create Accounts when Requesting Status Reports permissions are denied at the organizational level upon initial installation of Project Server 2003. Project Professional users will receive this error message if one or more of these permissions are allowed and the user does not have permission to create users in the Project Server database.

To resolve this Project Server Spooler error

  • Create user accounts by using the Manage Users and Groups pages in Project Web Access.

Cannot Publish Master Project (0x8c04003f)

Project Server can be configured to deny the publishing of master projects to the Project Server database.

Possible Causes

  • The Allow master projects to be published to Microsoft Project Server option is disabled on the Server configuration page that is available from the Admin page in Project Web Access.

To resolve this Project Server Spooler error

  • Use the Administrative project option when saving projects to the Project Server database. Administrative projects provide some of the functionality of a master project if you cannot publish a master project to the Project Server database.
– or –
Enable the Allow master projects to be published to Microsoft Project Server option in the Server configuration page that is available from the Admin page in Project Web Access.

Cannot Publish Non-Enterprise Resources (0x8c040040)

Project Server 2003 can be configured to only accept projects for which the resources that are assigned to tasks belong to the Enterprise Resource Pool.

Possible Causes

  • The user has assigned a resource that does not belong to the Enterprise Resource Pool to a task in the project.

To resolve this Project Server Spooler error

  • Add the resources that are assigned to tasks in the project to the Enterprise Resource Pool.
– or –
Assign a new resource that belongs to the Enterprise Resource Pool to the task.

Cannot Publish Non-Enterprise Projects on This Server (0x8c040041)

Project Server 2003 can be configured to only accept projects that are validated against the Enterprise Global Template when saved to the Project Server database.

Possible Causes

  • The Allow only enterprise projects to be published to this server option is enabled on the Server configuration page that is available from the Admin page in Project Web Access.

To resolve this Project Server Spooler error

  • Deselect the Allow only enterprise projects to be published to this server option on the Server configuration page that is available from the Admin page in Project Web Access.
– or –
Publish the project as an enterprise project.

Page 1 of 8