Microsoft KB Archive/331075

From BetaArchive Wiki
Knowledge Base


SharePoint Team Services subwebs are not automatically created when you publish a project plan to Microsoft Project Server 2002

Article ID: 331075

Article Last Modified on 2/1/2007



APPLIES TO

  • Microsoft Project Server 2002
  • Microsoft Project 2002 Professional Edition
  • Microsoft Office Project Web Access



This article was previously published under Q331075

SYMPTOMS

When you save and publish a project in Microsoft Project Server 2002, the SharePoint Team Services from Microsoft subwebs are not automatically created.

CAUSE

There are two causes for this issue:

  • Cause 1 - SharePoint Team Services is damaged.
  • Cause 2 - An IP address is used instead of a server name in the URL that Microsoft Project Professional 2002 uses to connect to Microsoft Project Server 2002 when you configure Microsoft Project Server accounts.


RESOLUTION

If SharePoint Team Services is damaged, follow these steps:

  1. Log on to Microsoft Project Server 2002 by using administrator permissions.
  2. Click Admin.
  3. Click Manage SharePoint Team Services.
  4. Click Subweb provisioning settings.
  5. Click Go to SharePoint Site Administration.
  6. Click Check Server Health.
  7. Click to select all the Detect check boxes, click to select all the Repair check boxes, and then click OK.
  8. After SharePoint Team Services finishes the process, create a new Microsoft Project plan, and then publish the new plan to the server.

If an IP address is used instead of a server name in the URL that Microsoft Project Professional 2002 uses to connect to Microsoft Project Server 2002 when you configure Microsoft Project Server accounts, follow these steps:

  1. Start Microsoft Project Professional 2002.
  2. On the Tools menu, click Enterprise Options, and then click Microsoft Project Server Accounts.
  3. Change any Microsoft Project Server account that is using an IP address in the URL to a server name. For example, if the URL is http://127.0.0.1/ProjectServer, change the URL to http://ServerName/ProjectServer.


STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Keywords: kbprb KB331075