"Error 5001" error message when you try to log on to Project Server 2003 by using Project Professional 2003 or by using Microsoft Project Web Access

Article translations Article translations
Article ID: 839773 - View products that this article applies to.
For a Microsoft Project Server 2002 version of this article, see 324835.
Expand all | Collapse all

On This Page

SYMPTOMS

When you try to log on to Microsoft Office Project Server 2003 by using Microsoft Office Project Professional 2003 or by using Microsoft Project Web Access, you may receive the following error message:
Microsoft Project was unable to log you on at this time because the Microsoft Project Server database cannot be accessed. Please try again later or check with your Microsoft Project Server administrator. (5001)

CAUSE

This issue may occur if one or more of the following conditions are true:
  • The passwords for the MSProjectUser account and the MSProjectServerUser SQL Server account (or the accounts that perform those roles) do not match the accounts that Project Server 2003 has stored in the registry.
  • The Security Identifier (SID) for the MSProjectUser account and the MSProjectServerUser account (or the accounts that perform those roles) may not match the SID in the Project Server 2003 database. The SIDs may not match if you restore a Project Server 2003 database from one SQL Server to another SQL Server.
  • The program server that runs Microsoft Windows 2000 (any service pack) may not be able to successfully initiate a connection to the database server that runs Microsoft Windows Server 2003. Because Windows Server 2003 includes Microsoft Data Access Components (MDAC) 2.8, for the program server to successfully initiate a connection to the server, it may require matching MDAC components.

    To obtain the latest version of MDAC and for other information about MDAC, visit the following Microsoft Developer Network (MSDN) Web site:
    http://msdn2.microsoft.com/en-us/data/aa937730.aspx
    Note The version of the MDAC on the server is likely MDAC 2.7 Service Pack 1 (SP1) or earlier.
  • The SQL Server or the client computer is configured to have only named pipes.
  • The Pds.dll file and the Pjsvrsecurity.dll file are missing from the %programfiles%\Microsoft Office Project Server 2003\BIN directory.
  • Some Project Server files are corrupted.
  • The DSN that is used to communicate between the Project client and Project Server is damaged.

RESOLUTION

To resolve this issue, use one of the following methods, depending on your situation.

Method 1: Change passwords on accounts

  1. Click Start, point to Programs, point to Microsoft SQL Server, and then click Enterprise Manager.
  2. Locate the server, expand the server, and then click the Security\Logins subfolder.
  3. Right-click the MSProjectServerUser account (or the equivalent account if you manually created the account), and then click Properties.
  4. In the Password box, type a new password, click OK, retype the new password, and then click OK.
  5. Repeat steps 3 and 4 for the MSProjectUser account (or the equivalent account if you manually created the account).

    Note We recommend that you use different passwords for each account.
  6. On the Console menu, click Exit.
  7. Make changes to the Microsoft Project Server virtual directory, and then save the changes.

    For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
    823529 How to use the Site Editor tool to create multiple Microsoft Project Web Access Web sites for Project Server 2003
  8. Log on to the Project Server 2003-based computer by using Project Professional 2003 or by using Microsoft Project Server Web Access.
If you receive the same error message, go to Method 2.

Method 2: Replace the Project Server 2003 accounts

  1. Click Start, point to Programs, point to Microsoft SQL Server, and then click Enterprise Manager.
  2. Locate and then expand the computer that is running SQL Server.
  3. In the Security\Login folder, right-click the MSProjectUser account (or an equivalent account if you manually created the account), and then click Delete.

    When you are prompted to confirm the deletion, click Yes.
  4. Repeat step 3 for the MSProjectServerUser account (or an equivalent account if you manually created the account).
  5. In the Databases\ProjectServer\Users folder, right-click the MSProjectUser account, and then click Delete.

    Repeat this step for the MSProjectServerUser account.
  6. In Enterprise Manager, right-click the Security\Logon folder, and then click New Login.
  7. Click the General tab.

    In the Name box, type the name of the MSProjectUser account.
  8. Click SQL Server Authentication, and then type the value of the password for the MSProjectUser account.
  9. In the Database box, point to the arrow, and then click ProjectServer.
  10. Click the Database Access tab, click to select the ProjectServer check box, and then click to select the MSProjectRole check box.
  11. Click OK, confirm the password, and then click OK.
  12. Right-click the Security\Logon folder, and then click New Login.
  13. Click the General tab.

    In the Name box, type the name of the MSProjectServerUser account.
  14. Click SQL Server Authentication, and then type the value of the password for the MSProjectServerUser account.
  15. In the Database box, point to the arrow, and then click ProjectServer.
  16. Click the Database Access tab, click to select the ProjectServer check box, and then click to select the MSProjectServerRole check box.
  17. Click OK, confirm the password, and then click OK.
  18. On the Console menu, click Exit.
  19. Log on to Project Server 2003 by using Project Professional 2003 or by using Microsoft Project Server Web Access.

Method 3: Run Cliconfg.exe

If the SQL Server or the client computer is configured to have only named pipes, follow these steps:
  1. Run Cliconfg.exe on the Project Server (Web) server or the client computer that is experiencing the problem.
  2. Click to select TCP/IP under Enabled Protocols by order, and then move TCP/IP to the top of the list.

Method 4: Copy the missing .dll files

If the Pds.dll file and the Pjsvrsecurity.dll file are missing from the %programfiles%\Microsoft Office Project Server 2003\BIN directory, copy these files from a working installation.

Method 5: Reinstall Project Server

If some Project Server files are corrupted, reinstall Project Server. To do this, follow these steps:
  1. Back up all databases and the Public Documents SharePoint site.
  2. Uninstall Project Server. Leave the database intact.
  3. Reinstall Project Server. Make sure that you connect to the existing database, the Windows SharePoint Services site, the OLAP server, and the SMTP server.
Note If multiple virtual directories were set up on Project Server, the directories must be re-created by using the Project Server 2003: EditSite utility. This procedure also removes any custom pages from Project Web Access. To download and install the EditSite tool, visit the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?FamilyID=6dc2c83e-54e1-40a9-9bb8-2dd293226b6f&DisplayLang=en

Method 6: Build a new DSN

If the DSN is damaged, build a new DSN by using the Project Server 2003: EditSite tool.

Note The EditSite tool is for Project Server 2003 only. You can use the EditSite tool to create a Project Server 2003-hosted deployment and to modify the properties of existing hosted sites. To download and install the EditSite tool, visit the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?FamilyID=6dc2c83e-54e1-40a9-9bb8-2dd293226b6f&DisplayLang=en

MORE INFORMATION

Note The default files and directories for authentication are as follows:

Main directory - Integrated Windows ONLY
LGNBSC.ASP - Basic
LGNINST.ASP - Windows
LGNINTAU.ASP - Windows
LGNINTPJ.ASP - Windows
LGNPS.ASP - Windows and Anonymous
LGNPSAU.ASP - Windows and Anonymous
LGNPSPJ.ASP - Windows and Anonymous

Properties

Article ID: 839773 - Last Review: September 18, 2011 - Revision: 4.0
APPLIES TO
  • Microsoft Office Project Server 2003
  • Microsoft Office Project Professional 2003
  • Microsoft Office Project Web Access
Keywords: 
kbfix kberrmsg kbprb KB839773

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com