You receive a "There is no information to display in this view" error message when you try to access a Project view in Microsoft Project Server 2003 or in Microsoft Project Server 2002

When you try to access a Project View in Microsoft Project Web Access, you may receive the following error message:Additionally, the following event messages are logged in the Application event log:

• Source: Microsoft Project Server Tracing Eventlog Provider
  Type: Warning
  Category: None
  Event ID: 1
  User: NT AUTHORITY\SYSTEM
  Description:
  Component: PCSViews
  File: ViewsDrop.cls
  Line: -1
  Error Number: 0x8000401a
  Description: Automation error
  The server process could not be started because the configured identity is incorrect. Check the username and password.
  

• Source: Microsoft Project Server Tracing Eventlog Provider
  Type: Warning
  Category: None
  Event ID: 1
  User: NT AUTHORITY\SYSTEM
  Description:
  Component: Views Notification Service
  File: Drive :\Proj10\pcportal\source\viewsnotify\ViewNotify.cpp
  Line: 67 Error Number: 0x8000401a
  Description: Failed to create instance of views processing object (PCSViews.ViewsDrop). The service cannot continue to run, shutting down.

• Event Type: Error
  Event Source: Microsoft Project Server Tracing Eventlog Provider
  Event Category: None
  Event ID: 2
  Date: <date>
  Time: <time>
  User: NT AUTHORITY\SYSTEM
  Computer: <Computer_Name>
  Description:
  The description for Event ID ( 2 ) in Source ( Microsoft Project Server Tracing Eventlog Provider ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: File: C:\Proj10\WebClient\source\utility\pjadorsutil2.cpp
  Line: 1691
  Error Number: 0x80004005
  Description: Assert Detected. The error code was also included.

This issue may occur if one of the following conditions is true:

• The Microsoft Data Access Components (MDAC) components that are installed on the server are damaged. This issue may occur if Microsoft Project Central was previously installed on the server.
• The Microsoft Internet Information Services (IIS) Lockdown tool or the URLScan tool is installed on the server, but the tool is not configured correctly.
• You do not have permissions to access the ViewDrop folder on the server.
• The password of the user account that is used to run the Microsoft Project Server Online Analytical Processing (OLAP) Cube component is incorrect.
• The Data Source Name (DSN) that is used to access the database that is used by Project Server is damaged or is deleted.
• The DSN registry entry in one of the following registry subkeys is incorrect, depending on the version of Project Server that you are running:
  • In Project Server 2003, the DSN registry entry is stored in the following registry subkey:
    HKEY_LOCAL_MACHINE\Software\Microsoft\Office\11.0\MS Project\WebClient Server\ProjectServer\Datasets\EnterpriseDatabase
    For example, this issue may occur if the value of the DSN registry entry is not set to PC11DSN.
  • In Project Server 2002, the DSN registry entry is stored in the following registry subkey:
  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\10.0\MS Project\WebClient Server\ProjectServer\Datasets\EnterpriseDatabase
  For example, this issue may occur if the value of the DSN registry entry is not set to PC10DSN.
• The Microsoft Project Server Views Notification Service is not running.
• This issue may occur if there is a problem with the user account that is configured as the identity for COM+ applications in Microsoft Project Server 2002 or in Microsoft Project Server 2003.

Method 1: Install the latest version of MDAC

Install the latest version of MDAC on the server. To obtain the latest version of MDAC, visit the following Microsoft Web site:

Method 2: Verify that the IIS Lockdown Tool or the URLScan tool is configured correctly

Verify that the IIS Lockdown Tool or the URLScan tool is configured correctly on the server. For more information about how to do this, click the following article number to view the article in the Microsoft Knowledge Base:

Method 3: Verify that the correct permissions are set on the ViewDrop folder

The local Administrators group and the System account must have Full Control permissions to the ViewDrop folder. Additionally, the Authenticated Users group and the Internet Guest account must have Read and Write permissions to the ViewDrop folder. To verify the permissions that are configured for the ViewDrop folder, follow these steps:

1. Log on to the server by using your domain user name and password.
   
   Note You must be a member of the local Administrators group or a member of the Domain Admin group to the configure permissions for the folder.
2. Start Windows Explorer, and then locate the ViewDrop folder.
   
   In a default installation of Project Server 2003, the ViewDrop folder is located in the following location:
   C:\Program Files\Microsoft Office Project Server 2003\Bin
   In a default installation of Project Server 2002, the ViewDrop folder is located in the following location:
   C:\Program Files\Microsoft Project Server\Bin
3. Right-click the ViewDrop folder, and then click Properties.
4. Click the Security tab, and then verify that the correct permissions are set on the folder.

For more information about how to configure permissions for files and folders, click the following article numbers to view the articles in the Microsoft Knowledge Base:

Method 4: Specify the correct information for the user account that is configured as the identity for COM+ applications

To specify the correct information for the user account that is configured as the identity for COM+ applications, follow these steps:

1. Run the Microsoft Project Server COM+ Settings tool (PSComplus.exe), and then specify a user account to use as the identity for COM+ applications. If Microsoft Project Server and Microsoft SQL Server are installed on the same computer, make sure that the user is a member of the local Administrators group. If Microsoft Project Server and SQL Server are installed on separate computers, make sure that the user is a Windows domain user account that is a member of the local Administrators group. To do this, follow these steps:
   1. Start Windows Explorer, and then locate the ViewDrop folder.
      
      In a default installation of Project Server 2003, the ViewDrop folder is located in the following location:
      C:\Program Files\Microsoft Office Project Server 2003\Bin
      In a default installation of Project Server 2002, the ViewDrop folder is located in the following location:
      C:\Program Files\Microsoft Project Server\Bin
   2. Double-click PSComplus.exe.
   3. Type the user account name in the Username box, and type the password in the Password box in the following areas:
      • The Analysis Services (OLAP) Access Identity area
      • The SharePoint Team Services Administration Identity area
      • The SharePoint Team Services Database Access Identity area
   4. Click Create\Update COM+ Apps.
2. On the computer that is running SQL Server, use one of the following procedures as appropriate for your situation:
   • If Microsoft Project Server and SQL Server are installed on the same computer, create a new user account, and then add the user account to the local Administrators group. This account must use the same name as the account that you specified as the identity for COM+ applications in step 1. To do this, follow these steps:
     1. Start the Computer Management tool.
     2. Expand System Tools, and then expand Local Users and Groups.
     3. Right-click Users, and then click New User.
     4. Specify the user name and the password, and then click Create.
     5. Right-click the user account that you created, and then click Properties.
     6. Click the Member Of tab, and then click Add.
     7. Click Administrators, click Add, and then click OK two times.
   • If Microsoft Project Server and SQL Server are installed on separate computers, add the Windows domain user account that you specified as the identity for COM+ applications in step 1 to the local Administrators group. To do this, follow these steps:
     1. Start the Computer Management tool.
     2. Expand System Tools, and then expand Local Users and Groups.
     3. Expand Groups.
     4. Right-click Administrators, and then click Properties.
     5. Click Add.
     6. Type the name of the Windows domain user account that you specified as the identity for COM+ applications in step 1, click Check Names, and then click OK two times.
3. Add the user account that you specified in step 2 to the database (db) owner role for the database that is used by Microsoft Project Server. To do this, follow these steps:
   1. Start SQL Server Enterprise Manager.
   2. Expand Microsoft SQL Servers, expand SQL Server Group, expand ServerName, and then expand Security.
   3. Right-click Login, and then click New Login.
   4. Click the General tab, and then specify the name of the user account that you specified in step 2 in the Name box.
   5. Under Authentication, specify the authentication that you want to use.
   6. Click the Database Access tab, and then click to select the ProjectServer check box.
   7. Under Database roles for 'ProjectServer', click to select the db_owner check box, and then click OK.
   8. Exit SQL Server Enterprise Manager.

Method 5: Reset the DSN

Reset the DSN. To do this, follow these steps:

1. If you are running Project Server 2003, start the EditSite tool. If you are running Project Server 2002, start the Site Editor tool.
   
   To obtain the EditSite tool for Project Server 2003, visit the following Microsoft Web site:
   http://www.microsoft.com/downloads/details.aspx?FamilyID=6dc2c83e-54e1-40a9-9bb8-2dd293226b6f&amp;displaylang=en (http://www.microsoft.com/downloads/details.aspx?FamilyID=6dc2c83e-54e1-40a9-9bb8-2dd293226b6f&amp;displaylang=en)
   To obtain the Site Editor tool for Project Server 2002, visit the following Microsoft Web site:
   http://www.microsoft.com/downloads/details.aspx?familyid=123a740b-9512-4a21-89fb-5a20819c20c7&amp;displaylang=en (http://www.microsoft.com/downloads/details.aspx?familyid=123a740b-9512-4a21-89fb-5a20819c20c7&displaylang=en)
2. In the DSN Name box under Site Information, rename the existing DSN by adding a number to the end of the name of it. For example, if you are running Project Server 2002 and the name of the DSN is PC10DSN, rename the DSN to PC10DSN1.
3. Click Save, and then click Yes when you are prompted to delete the old DSN.
4. Click OK when you receive the message that the changes that you made are saved.
5. In the DSN Name box under Site Information, change the name of the DSN to use the original name. To do this, remove the number that you added to the end of the name so that the DSN uses the original name of the DSN. For example, if you renamed the DSN to PC10DSN1 in step 2, change the name to PC10DSN.
6. Click Save, and then click Yes when you are prompted to delete the old DSN.
7. Click OK when you receive the message that the changes that you made are saved.
8. Under Virtual Directory, click Test to verify that connection parameters are configured correctly.
9. Click OK, and then click Exit.

For more information about the tools that are available for Project Server 2003 and Project Server 2002, click the following article number to view the article in the Microsoft Knowledge Base:

Method 6: Configure the correct value for the DSN registry entry

To configure the correct value for the DSN registry entry, follow these steps.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

1. Click Start, click Run, type regedit, and then click OK.
2. Locate, and then click the following registry subkey, depending on your version of Project Server:
   Back to the top

   Project Server 2002

   HKEY_LOCAL_MACHINE\Software\Microsoft\Office\10.0\MS Project\WebClient Server\ProjectServer\Datasets\EnterpriseDatabase\DSN
   Back to the top

   Project Server 2003

   HKEY_LOCAL_MACHINE\Software\Microsoft\Office\11.0\MS Project\WebClient Server\ProjectServer\Datasets\EnterpriseDatabase\DSN
3. On the Edit menu, click Modify.
4. Type the correct name for the DSN in the Value data box, and then click OK.
5. Quit Registry Editor.

Method 7: Restart the Microsoft Project Server Views Notification Service

Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

1. Remove any XML files that are located in the following folder:
   Drive:\Program Files\Microsoft Project Server\Bin\ViewDrop
2. Click Start, point to Administrative Tools, and then click Services.
3. Right-click Microsoft Project Server Views Notification Service, and then click Stop.
4. Tight-click Microsoft Project Server Views Notification Service, and then click Start.

Note You may have to restart the server after you restart the Microsoft Project Server Views Notification Service.