Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Resources are not integrated when you try to integrate a resource from Microsoft Dynamics SL into Microsoft Office Project Server 2007

Resources are not integrated when you try to integrate a resource from Microsoft Dynamics SL into Microsoft Office Project Server 2007

Symptoms

Consider the following scenario in Microsoft Dynamics SL:
  • You try to integrate a resource from Microsoft Dynamics SL into Microsoft Office Project Server 2007.
  • You review the resource in Project Server 2007.
In this scenario, you notice that the resource is not integrated. Additionally, you may experience one or more of the following symptoms:
  • In MSDSLEventLog, you receive the following error message:

    DSL_2_Project Resource Failed

    Then, you receive the following error message:

    DSL_2_Project Resource: Queue Record:100 Employee:TESTREQ \

    Error:

    System.Web.Services.Protocols.SoapException: ProjectServerError(s) LastError=CustomFieldRequiredValueNotProvided Instructions: Pass this into PSClientError constructor to access all error information

    at Microsoft.Office.Project.Server.WebService.Resource.CreateResources(ResourceDataSet rds, Boolean validateOnly, Boolean autoCheckIn)

    PSCLientError Output:

    CustomFieldRequiredValueNotProvided

    mdpropuid: 70b7854a-fa64-4b4f-8d2d-3cb8da03a126

    Error Message 9994
    ·
  • The value X appears in the Status box on the Queue Status tab in the Microsoft Project Connector Setup (PA.MSP.00) screen for the resource that is being integrated.
  • The Integrated Resource check box is no longer checked in the Employee and Resource Maintenance (PA.EMP.00) screen for the resource that is being integrated.

↑ Back to the top

Cause

Cause 1

The resource name in Microsoft Office Project Server 2007 does not match the resource name in Microsoft Dynamics SL.

To resolve this problem, see Resolution 1.

Cause 2

You created an Enterprise custom field for Resources, and this field is marked as required. 

To resolve this problem, see Resolution 2.

↑ Back to the top

Resolution

Resolution 1

Make sure that the resource name value in Employee and Resource Maintenance (PA.EMP.00) in Microsoft Dynamics SL and the Resource Name in Microsoft Office Project Server 2007 are identical. To do this, follow these steps: 
  1. Locate the Project Web Access (PWA) site.
  2. Click Resource Center, and then locate the Resource Name.
  3. Cross-check the Resource Name in Project Server 2007 with the information that is displayed in Microsoft Dynamics SL in the Name in Project Server box in Employee and Resource Maintenance (PA.EMP.00) screen. These two values must be identical.
  4. If it is necessary, change the value in the Name in Project Server box to match what is displayed in Project Server for the Resource Name.
  5. Try to integrate the employee again.

Resolution 2

Determine whether any Enterprise custom fields are set to Required. To do this, follow these steps: 
  1. Locate the Project Web Access (PWA) site.
  2. Click Server Settings.
  3. Under the Enterprise Data setting, click Enterprise Custom Field Definition.
  4. Check the Required column to see whether any items have a value of Yes.
  5. If the Required column for one or more custom fields is set to Yes, set the column to No.

↑ Back to the top

Keywords: kbmbsmigrate, kbmbspartner, kbsurveynew, kbsolomon, kb

↑ Back to the top

Article Info
Article ID : 2431316
Revision : 1
Created on : 1/7/2017
Published on : 8/5/2011
Exists online : False
Views : 113