Error when you click certain links in the Project center page in Business Portal for Microsoft Dynamics SL

This article helps you fix an issue in which you receive error messages when you click certain links in the Project center page in Business Portal.

Applies to:   Microsoft Dynamics SL 2011
Original KB number:   915315

Symptoms

Consider the following scenarios in Business Portal for Microsoft Dynamics SL and for Microsoft Business Solutions - Solomon:

  • When you click the Time link under the Project center page in Business Portal, you receive the following error message:

    Error retrieving Project Employee information on Time entry

  • When you click the Document Approvals link under the Project center page in Business Portal, you receive the following error message:

    Error in /Application the resource cannot be found in Time and Expense approval

  • Under the Project center page in Business Portal, you receive the following error message in the Communicator Web Part:

    Error retrieving Project Employee information: ERROR

  • When you click the Edit or Reject link under the Executive Line Item Approvals page for an expense item, you receive the following error message:

    ASP Error encountered in: GRFUNCTION.ASP / IsModuleUnlocked Error #424 Object required

Cause

This problem occurs because a valid back-office ID isn't assigned to a role.

Note

In the Manage Business Portal Users pane, the Back Office ID box for a role that is assigned to the Business Portal user contains the default Unspecified value.

Resolution

To resolve this problem, assign a valid back-office ID to the role that does not have a valid back-office ID. To do this, follow these steps:

  1. Sign in to Business Portal as the administrator.
  2. Click Site Settings, and then click Manage Business Portal Users.
  3. In the User List Web part, select the appropriate user ID.
  4. In the User Properties Web part, click the Roles tab.
  5. Assign a valid back-office ID to the role that doesn't have a valid back-office ID.

The issue that is described in the Symptoms section doesn't apply to Microsoft Dynamics SL 7.0.