WORKAROUND
To work around this behavior, use the appropriate method for your situation.
Workaround for Cause 1
Use Internet Explorer to verify that the URL is correct. To do this, follow these steps:
- In Microsoft Project, click Options on the Tools menu, and then click the Workgroup tab.
- In the Microsoft Project Central Server URL box, select and copy the URL.
- Start Internet Explorer, and then paste the URL that you copied in step 2 into the Internet Explorer address bar.
- If Internet Explorer successfully displays the Microsoft Project Central logon page, select and copy the URL from the Internet Explorer address bar, and then paste it back in the Microsoft Project Options dialog box.
If Internet Explorer does not successfully display the logon page, check with the Microsoft Project Central server administrator to verify the correct URL.
Workaround for Cause 2
Verify that Internet Explorer is not offline. To do this, follow these steps:
- Start Internet Explorer.
- On the File menu, locate Work Offline.
- If the Work Offline check box is selected, click to clear the Work Offline check box.
Workaround for Cause 3
Verify that the server is available. To do this, follow these steps:
- In Microsoft Project, click Options on the Tools menu, and then click the Workgroup tab.
- In the Microsoft Project Central Server URL box, select and copy the URL.
- Start Internet Explorer, and then paste the URL that you copied in step 2 into the Internet Explorer address bar.
- If Internet Explorer successfully displays the Microsoft Project Central logon page, the server is available.
If Internet Explorer does not successfully display the logon page, have your Web server administrator verify that the server computer is running, that the Internet Services Manager is running on the server, and that the Default Web Site service in Internet Services Manager is not stopped.
Workaround for Cause 4
Verify that anonymous access to the Project Central Database has been enabled, and that the user name and password used for anonymous access are valid. To do this, follow these steps:
NOTE: These steps must be performed by someone who has administrative access to Internet Services Manager on the server that manages the Microsoft Project Central Server Web site.
- Verify that anonymous access is enabled.
- Start Internet Services Manager.
- In the Console Tree (left pane), double-click the server that contains the Microsoft Project Central Web site.
- Under the server, double-click Default Web Site.
- Under Default Web Site, double-click the Project Central virtual directory.
- Under the Project Central virtual directory, select the ISAPI folder.
- In the view pane (right pane), select Pjdbcomm.dll, and then click Properties on the Action menu.
- In the Pjdbcomm.dll Properties dialog box, click the File Security tab.
- Under Anonymous Access and Authentication Control, click Edit, and then verify that the Anonymous Access check box is selected (checked). If it is not selected, anonymous access is not enabled.
- Verify that the user name and password are valid.
- If necessary, click to select the Anonymous Access check box, and then click Edit.
- In the Anonymous User Account dialog box, valid user names for anonymous access are either of the following:
F- IUSR_Computer name (where Computer name is the name of the computer where the Web server is running)
NOTE: If this user name is specified, then the Enable automatic password synchronization option (in IIS version 4) or the Allow IIS to control password option (in IIS version 5) must be selected. - Any valid domain account and password, with the user name entered in the form domain\username
NOTE: If a user name of this type is specified, and if the user account has a password that changes periodically, you must manually change the new password in the Anonymous User Account dialog box. IIS cannot synchronize the password in this situation.
With either type of user name, the specified user cannot be a member of the Guest user group if the Guest group has been disabled.
NOTE: For full functionality with Microsoft Project Central project views, the account used for anonymous access must also have access to the network shares where project files are stored.
Workaround for Cause 5
Verify that the user name that Microsoft Project Central is using to communicate with the database is a valid user account in the database, that the password for the user account is valid, and that the user account has database owner permissions for the Project Central database.
The database user account and password used by Microsoft Project Central to communicate with the Project Central Database are stored in the
UserName and
Password values of the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\9.0\MS Project\WebClient Server\ProjectCentral
NOTE: Either of the following conditions must be true to avoid the error message described in the "Symptoms" section of this article.
Condition 1
Microsoft Project Central is using the same user name as the account that owns the tables (normally the user name that was used to create the tables).
If the user name that Microsoft Project Central is using is not the same user name that owns the tables in the Project Central database, you receive the error message described in the "Symptoms" section of this article, unless Condition 2 is met. This error message occurs even if both users have database owner permissions.
Condition 2
The Project Central database tables are owned by the built-in dbo user account. If the database tables are owned by dbo and the user name that Microsoft Project Central uses has database owner permissions, the error does not occur.
Modify the Scripts to Create the Tables with dbo as Owner
To modify the scripts to create the tables with dbo as owner of the tables instead of a single user, follow these steps in addition to the steps listed in SvrSetup.htm:
- Edit the Crttable.sql script.
- Replace all instances of CREATE TABLE with CREATE TABLE dbo. Note that in the Replace box, CREATE TABLE must have a space character following the text.
- Run the script.
Workaround for Cause 6
Reactivate the project manager's Microsoft Project Central account. To do this, follow these steps:
- Log on to Microsoft Project Central as Administrator.
- Under Admin, click Users.
- Under User Account, select the project manager's account.
- Click Modify User.
- In the Account Status list, click Active.
- Click Save Changes.
Workaround for Cause 7
Set the user mode for Project Central to
Normal. To do this, follow these steps:
- Log on to Microsoft Project Central as Administrator.
- Under Admin, click Server Mode.
- Under Server Mode, click Normal.
- Click Save Changes.
Workaround for Cause 8
Run the SQL scripts as described in Svrsetup.htm. For information about where to find Svrsetup.htm, see the "More Information" section later in this article.
Workaround for Cause 9
Change the Internet options to bypass the proxy server for local addresses. To do this, follow these steps:
- Click Start, point to Settings, and then click Control Panel.
- In Control Panel, double-click the Internet Options icon.
- In the Internet Properties dialog box, click the Connections tab.
- Click LAN Settings.
- Click to select the Bypass proxy server for local addresses check box. Click OK.
- Click OK to close the Internet Properties dialog box.
- Close Control Panel.
Workaround for Cause 10
To resolve this problem, your system administrator or Web server administrator needs to determine the best solution depending on how the local intranet is managed. Some possibilities are:
- Change the IP address for the Default Web Site to a static address.
- Set up a separate Web site for Microsoft Project Central that uses a static IP address.
Workaround for Cause 11
Set
Execute Permissions on the ProjectCentral virtual directory to
Scripts and Executables (in IIS 5.0) or
Execute (including Script) (in IIS 4.0). To do this, follow these steps:
- Start Internet Services Manager.
- Click the plus sign (+) next to Default Web Site.
- Right-click the ProjectCentral virtual directory, and then click Properties on the shortcut menu.
- Click the Virtual Directory tab.
- Use the appropriate method for your version of Microsoft Windows:
Microsoft Windows NT 4.0
Under Permissions, click Execute (including Script).
Microsoft Windows 2000 or Microsoft Windows XP
Under Application Settings, in the Execute Permissions list, click Scripts and Executables.
- Click OK and close Internet Services Manager.