When Project Professional Doesn t Connect to Project Server

When Project Professional Doesn’t Connect to Project Server

When you log onto Project Server from Project Professional 2002, the “Cannot Connect” error is displayed. There are a couple of causes not mentioned in the error message and not documented by KB articles. After you eliminate the causes listed in the error message, consider the following conditions:

“Cannot Connect” Error

In some instances, you’ll receive the “Cannot Connect” error as follows:

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 have enterprise features enabled.


The Project Professional client fails to connect to the Project Server despite the fact that the Test Server Connection functionality in the Project Server Account Creation and Maintenance dialog box reported success.

Cause 1

The default language setting on the client is set to a language other than English and Project Server hasn’t been configured for multiple language support as defined in TechNet under “International Server Deployment: Microsoft Project 2002” (http://www.microsoft.com/technet/treeview/default.asp?url=/technet/ prodtechnol/project/project2002/reskit/ps02/psdply/psntldpl.asp).


Set the client default language to en-us or execute the steps outlined in the previously mentioned TechNet article.

Cause 2

Project Professional was installed prior to logging onto Project Web Access for the first time. It seems that some client systems react badly when Project Professional is installed before the user has logged onto Project Web Access.


Here’s what you must do to correct this problem:

  1. Uninstall Project Professional.

  2. Reboot.

  3. Delete the two Project Server ActiveX objects PJ10enuC Class and PJAdoInfo2 Class if they were installed or partially installed from the Downloaded Programs file folder typically in the Windows directory of Windows XP.

  4. Log onto Project Web Access and accept the ActiveX downloads.

  5. Reinstall Project Professional.

Unable to Make Project Server a Trusted Site

The first time you log onto Project Server from Project Professional, the system detects whether or not the URL is in your Internet Explorer’s Trusted sites security category. Normally you can select the option to make Project Server a trusted site from the logon dialog box. Occasionally, the automation fails and you must do this manually in your browser. To perform this step manually:

  1. Open Internet Explorer.

  2. Navigate to Tools Internet Options.

  3. Select the Security tab and click the Sites button, as shown in Figure 6-5.

    click to expand
    Figure 6-5. Internet Explorer Internet Options dialog box

  4. In the Trusted sites dialog box (see Figure 6-6) uncheck the “Require server verification (https:) for all sites in this zone” option if you haven’t installed an SSL certificate on your server.

    click to expand
    Figure 6-6. Trusted sites dialog box

  5. Fill in the name of the site and click Add.

Implementing Enterprise Portfolio Management with Microsoft Project Server 2002
Implementing Enterprise Portfolio Management with Microsoft Project Server 2002
ISBN: 1590591186
EAN: 2147483647
Year: 2005
Pages: 185

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net