You receive the "Microsoft Project was unable to establish a connection with the selected Microsoft Project Server" error message when you log on to Microsoft Project Server (837653)


The information in this article applies to:

  • Microsoft Office Project Server 2003
  • Microsoft Office Project Professional 2003
  • Microsoft Project Server 2002
  • Microsoft Project Professional 2002
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry

SYMPTOMS

When you log on and connect to Microsoft Office Project Server 2003 by using Microsoft Office Project Professional 2003 or when you log on and connect to Microsoft Project Server 2002 by using Microsoft Project Professional 2002, you may intermittently experience both of the following symptoms:
  • You receive an error message that is similar to the following:
    Connection failed:
    SQLState: '01000'
    SQL Server Error: 53
    [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect())
    Connection failed:
    SQLState '08001'
    SQL Server Error: 17
    [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.
  • After you receive the first error message, you are prompted to type your user name and password to log on to Microsoft SQL Server. When you do this, you receive the following error message:
    Microsoft Project

    Cannot Connect

    Microsoft Project was unable to establish a connection with the selected Microsoft Project Server. This could be caused by a loss of network connectivity, invalid username or password, lack of an enterprise global template, problems with the Microsoft Project Server or database, or your Microsoft Project Server may not have enterprise features enabled.

CAUSE

This issue may occur if either of the following conditions is true:
  • You connect to Project Server 2003 or to Microsoft Project Server 2002 over a slow link or from a remote location that is outside the local area network (LAN), and an issue exists that prevents the host name of the computer that is running SQL Server from resolving correctly.
  • A Group Policy setting was applied to your computer that changed the regional settings of your computer.

RESOLUTION

To resolve this issue, use one of the following methods, depending on the version of Microsoft Project Server that you are running.

Microsoft Project Server 2002

If you are running Microsoft Project Server 2002, edit the registry of the Web server to use the IP address of the computer that is running SQL Server. On the computer that is running Microsoft Internet Information Services (IIS), edit the connectInfo registry entry in the following registry key to use the IP address of the computer that is running SQL Server:

HKEY_LOCAL_MACHINE\Software\Microsoft\Office\10.0\MS Project\WebClient Server\ProjectServer\Datasets\Application

To do this, follow these steps:

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
  1. Click Start, and then click Run.
  2. In the Open box, type regedit, and then click OK.
  3. Locate the following key registry key:

    HKEY_LOCAL_MACHINE\Software\Microsoft\Office\10.0\MS Project\WebClient Server\ProjectServer\Datasets\Application

  4. In the right pane, double-click connectInfo.
  5. In the Value data box, change the ServerName entry in the Data Source=ServerName part of the string to the IP address of the computer that is running SQL Server.

    For example, the string in the Value data box may look similar to the following, where IPAddress is the IP address of the computer that is running SQL Server:

    Provider=SQLOLEDB;User ID=MsProjectServerUser; Password=Password;Persist Security Info=False;Initial Catalog=ProjectServer;Data Source=IPAddress

  6. Click OK, and then quit Registry Editor.

Project Server 2003

If you are running Project Server 2003, use the ConnInfo.exe tool to edit the registry of the server to use the IP address of the computer that is running SQL Server. To do this, follow these steps:
  1. Locate the folder that contains the ConnInfo.exe tool, and then double-click ConnInfo.exe.

    The ConnInfo.exe tool is located in the Drive:\Program Files\Microsoft Office Project Server 2003\Bin\1033 folder of the computer that is running Project Server 2003. To download the ConnInfo.exe tool, visit the following Microsoft Web site:

    http://www.microsoft.com/downloads/details.aspx?FamilyID=1d30b672-baa0-4030-b036-323b216d7264&displaylang=en

  2. In the Project Server 2003 Connection Information dialog box, click either Single database configuration or Partitioned database configuration.
  3. In the SQL Server box, type the IP address of the computer that is running SQL Server, click Save, click OK, and then click Exit.

MORE INFORMATION

For additional information about how to troubleshoot a similar error message that may occur when you log on to Microsoft Project Server 2002, click the following article number to view the article in the Microsoft Knowledge Base:

818047 You receive the "Microsoft SQL Server login" error message when you connect to Microsoft Project Server

For more information about Microsoft Project Server 2002, visit the following Microsoft Web site:

http://www.microsoft.com/office/previous/project/default.asp

Modification Type:MinorLast Reviewed:5/9/2006
Keywords:kberrmsg kbprb KB837653 kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.