You receive a "Microsoft Project Server cannot connect to the specified Web server running SharePoint Team Services" error message when you try to connect Microsoft SharePoint Team Services (818846)


The information in this article applies to:

  • Microsoft Project Server 2002
  • Microsoft Project Web Access

SYMPTOMS

When you try to connect Microsoft SharePoint Team Services in Microsoft Project Web Access, you may receive the following error message:
Microsoft Project Server cannot connect to the specified Web server running SharePoint Team Services. The reasons could be:

1. SharePoint Team Services is not installed on http://ServerName:PortNumber.
2. ComputerName\UserName is not in the Windows NT Administrators group on ComputerName.
3. If the local area network has proxy servers for Internet access, the proxy server is not specified in the LAN Settings for the Internet Explorer.
4. The server URL http://ServerName:PortNumber is not correct or the server cannot be accessed at this time.
5. The SharePoint administration port PortNumber is not correct.

For more information on setting up and configuring SharePoint Team Services on a Web server, refer to the Microsoft Project Server Installation Guide on the Microsoft Project Server menu (Start menu, Programs submenu).
Alternatively, when you try to manually create a subweb in Project Web Access, you may receive the following error message:
VBScript: Microsoft Project Web Access Error occurred when creating subweb. Subweb does not seem to exist.

CAUSE

This behavior may be caused by any of the following conditions:
  • The Proxy Configuration may not recognize the SharePoint Team server in the registry.
  • The SharePoint server may be inheriting permissions that do not permit you to completely create a subweb. The subweb is only partially created.
  • The name of your project file may contain special characters.

WORKAROUND

To work around this behavior, use the appropriate method for your situation.

Workaround for Proxy Configuration Issues

Configure Microsoft Project Server for a Proxy Server by running the WinHTTP Proxy Configuration utility. Specify the server name, Internet protocol (IP) address, or Fully Qualified Domain Name of your SharePoint Team Services-enabled server. To do this, follow these steps:
  1. On the computer that has Project Server installed, click Start, click Run, and then type cmd in the Open box.

    This will open a command prompt window.
  2. Change the directory to the location of the ProxyCfg.exe file. For example, type cd c:\program files\microsoft project server\bin.
  3. Type the following command and specify the server name, IP address, and Fully Qualified Domain Name of your SharePoint server in the bypass list:

    proxycfg -d -p "YourProxyServer" "local;ServerName;IPAddress; FQDN"

    If you are not in a proxy server environment, type proxyserver instead of YourProxyServer.
  4. Press ENTER. Information about the proxy server appears.
  5. Type iisreset, and then press ENTER. This action resets the Microsoft Internet Information Services (IIS) server with the new proxy settings.
  6. Log on to Microsoft Web Access as Administrator.
  7. Click Admin, and then click Manage SharePoint Team Services.
  8. On the Connect to Servers page, type your SharePoint Team Services confirmation information. The confirmation information is processed after you install the STSWiz.exe file from the Project Server CD.

    Note The PSComplus.exe utility and DB_DataReader rights must be granted to the SharePoint Database in SQL Server before you connect SharePoint Team Services to Project Server. For a general overview of the installation and connection of SharePoint Team Services to Project Server, see the following Microsoft Knowledge Base Articles:

    322235 How to install and configure SharePoint Team Services for Microsoft Project Server on Windows 2000

    819642 How to configure SharePoint Team Services for Microsoft Project Web Access

  9. Click Save Changes to test the connection of SharePoint Team Services to Project Server.
Note You may have to replace "ServerName" with the actual server name, IP address, or FQDN of your Project Server computer to test connectivity.

Workaround: Subweb Not Completely Created

If you tried to publish a project file or manually create the subweb previously, delete the Subweb folder in IIS first. To do this, follow these steps:
  1. Click Start, point to Administrative Tools, and then click Internet Service Manager.
  2. Expand the Web site where you installed SharePoint Team Services.
  3. Locate the Subweb folder.

    It will have a name that is similar to "101" or "102". Right-click this folder, and then click Delete.
Run Check Server Health to correct settings in SharePoint Team Services:
  1. Log on to Microsoft Web Access as Administrator.
  2. Click Admin, and then click Manage SharePoint Team Services.
  3. Click Subweb Provisioning Settings.
  4. In the Specify the SharePoint Team Services server section, click Go to SharePoint Site Administration.
  5. On the Site Administration page, locate the Server Health section.
  6. Click Check Server Health.
  7. Click to select all the check boxes on the Check Server Health page, and then click OK.
  8. On the Server Health Report menu, click Submit.
When you run Server Health, you must synchronize the Administrator Accounts to SharePoint Team Services. To do this, follow these steps:
  1. Log on to Microsoft Web Access as Administrator.
  2. Click Admin, and then click Manage SharePoint Team Services.
  3. In the Options sections, click Synchronize Administrator Accounts.

Workaround If the Project File Contains Special Characters

Rename the project file without using special characters in the file name, and then republish the project to create the subweb automatically. After you rename the project file, you may also manually create the subweb in Microsoft Project Web Access.
Modification Type:MajorLast Reviewed:3/27/2006
Keywords:kbprb KB818846
©2004 Microsoft Corporation. All rights reserved.