Microsoft KB Archive/285094

= PRJ2000: Pre-Release Version Has Expired Error When Connecting to Microsoft Project Central =

Article ID: 285094

Article Last Modified on 1/29/2007

-

APPLIES TO


 * Microsoft Project 2000 Standard Edition

-



This article was previously published under Q285094



SYMPTOMS
When you browse to Microsoft Project Central, you receive one of the following error messages.

In Microsoft Project 2000 Service Release 1 (SR-1)
You cannot connect to the Microsoft Project Central server.

There may be a problem with your server installation or with your Microsoft Project Central database. See your Microsoft Project Central Administrator.

In Microsoft Project 2000 (non-SR-1)
http://ServerName/ProjectCentral/Logon/expired.asp

You cannot connect to the Microsoft Project Central server, for one of the following reasons:

1) You are running a pre-release version that has expired.

2) There may be a problem with your server installation or with your Microsoft Project Central database. See your Microsoft Project Central Administrator.



CAUSE
This error message may occur when any of the following conditions is true:
 * 1) The three scripts that set up the Microsoft Project Central database were not run, or there was an error when the Microsoft Project Central database was created (the database was not created properly).
 * 2) The SQL or MSDE service is not running.
 * 3) You installed Microsoft Project Central by using the Install Now option, and when you were prompted to restart the computer, you chose not to restart.
 * 4) The password for the user account that created the Project_CentralDB Database in SQL has been changed, or the user account has been deleted.
 * 5) The authentication method used by SQL Server is set to Windows NT only.
 * 6) The starting point (virtual folder root) for the MSADC virtual directory in Microsoft Internet Information Services (IIS) is blank.



RESOLUTION
To resolve this problem, use the appropriate methods for your situation.

Resolution for Cause 1
Refer to the current server setup document, and follow the steps for installation, which are located at the following Microsoft Web site:

Installation and Customization of Microsoft Project Central

Resolution for Cause 2
Start the SQL or MSDE service. Use the appropriate method for your situation.

When Using Microsoft SQL Server for the Microsoft Project Central Database

 * 1) Click Start, point to Programs, point to Microsoft SQL Server, and then click Service Manager.
 * 2) In the SQL Server Service Manager dialog box, verify that you have the correct server and services selected. By default, the computer name is displayed in the Server box, and MSSQLServer in the Services box.
 * 3) Click the Start/Continue button.

When Using MSDE for the Microsoft Project Central Database

 * 1) Click Start, point to Programs, point to MSDE, and then click Service Manager.
 * 2) In the SQL Server Service Manager dialog box, verify that you have the correct server and services selected. By default, the computer name is displayed in the Server box, and MSSQLServer in the Services box.
 * 3) Click the Start/Continue button.

Resolution for Cause 3
Restart the computer on which Microsoft Project Central was installed.

Resolution for Cause 4
 Click Start, and then click Run. In the Open box, type regedit, and then click OK. Expand the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\9.0\MS Project\WebClient Server\ProjectCentral

 Change the password in the registry key to match the Microsoft SQL Server user account password.

Alternatively, change the SQL Server user account password to match the password shown in the above registry key.

Resolution for Cause 5
NOTE: The following steps make a fundamental change to the setup of Microsoft SQL Server that affects all databases administered by the same server. Review this workaround with your SQL Server administrator before proceeding with these steps.
 * 1) Click Start, point to Programs, point to Microsoft SQL Server, and then click Enterprise Manager.
 * 2) In the SQL Server Enterprise Manager dialog box, right-click the SQL Server name (located under the SQL Server Group) and then click Properties on the shortcut menu.
 * 3) In the SQL Server Properties dialog box, click the Security tab.
 * 4) Under Authentication, click SQL Server and Windows NT.
 * 5) Click Apply, and then click OK.
 * 6) Right-click the SQL Server name, and then click Stop on the shortcut menu. Click Yes when you are prompted.
 * 7) Right-click the SQL Server name, and then click Start on the shortcut menu.

Resolution for Cause 6
If the MSADC virtual directory does not have the correct application name and starting point, the MDAC components will not be available. To correct the application name and starting point, follow these steps.

NOTE: During this process you may receive the following error message:

An Error occurred reading or setting a configuration parameter (0x80080005).

For additional information about how to resolve this error, click the article number below to view the article in the Microsoft Knowledge Base:

248136 Err Msg: An Error Occurred Reading or Setting a Configuration Parameter (80080005)

 Open Internet Service Manager.</li> Click the + symbol next to the computer name.

NOTE: If you are using Microsoft Windows NT 4.0, you must first expand the Internet Information Services folder.</li> Click the + symbol next to Default Web Site.</li> Right-click the MSADC virtual directory, and then click Properties on the shortcut menu.</li> Click the Virtual Directory tab.</li> Under Local Path, click Browse to confirm that the system is pointing to the following path:

[drive]:\program files\common files\system\msadc

</li> In the Application Settings dialog box, the Application Name setting needs to be MSADC. If the setting is blank, click Create to have MSADC appear.

NOTE: If you see the Remove button, click it first. The button text changes to Create, and you can click this button to set the application name.

The Starting Point setting is now:

<Default Web Site>\MSADC

</li> You will now need to stop and restart (cycle) the administrative services for Microsoft Internet Information Server (IIS).</li></ol>

Cycle the IIS Administrative Services
Use the appropriate method for your version of IIS.

Microsoft Internet Information Server (IIS) 5.0:

For IIS 5.0, follow these steps:
 * 1) Open a management console for IIS 5.0.
 * 2) Right-click the computer name, and then click Restart IIS on the shortcut menu.
 * 3) On the next screen, make sure that the Restart Internet Services on   check box is selected.
 * 4) Click OK.

The services begin to shut down and restart.
 * 1) When this process is completed, quit the management console.

Microsoft Internet Information Server (IIS) 4.0:

For IIS 4.0, follow these steps:   To stop all IIS-related services, type NET STOP IISADMIN /Y at the command prompt.

This stops IIS Admin Service and all dependent services.

Below is an example of the output you see after you type this command (the dependent services listed on your computer may vary): <pre class="fixed_text">The following services are dependent on the IIS Admin Service. Stopping the IIS Admin Service will also stop these services.

FTP Publishing Service Microsoft NNTP Service Microsoft SMTP Service World Wide Web Publishing Service A message is then displayed as each service is successfully stopped. </li> At the command prompt, type the NET START command to restart the IIS-related services you use, and press ENTER.

For example, to restart the World Wide Web service, type NET START W3SVC .</li> Determining service names:

To determine the service names, start Registry Editor (type Regedit.exe or Regedt32.exe ) and go to the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services

</li> Under the Services key, the service name that works with the NET STOP and NET START commands is listed.

NOTE: For each service, there is also a Display Name value, which is the name listed under Services in Control Panel, and in the messages displayed after you run the NET STOP and NET START commands. However, you cannot use these display names as a parameter with the NET STOP and NET START commands.</li></ol>

Common IIS-related Services:

Keywords: kbbug kberrmsg kbfix KB285094

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.