Microsoft Project Server 2010 and Microsoft Dynamics AX 2012 Integration Issue Resolver

Resolving issues with the integration of Microsoft Project Server 2010 and Microsoft Dynamics AX 2012 can be sometimes very difficult, especially if you do not know where to start looking for the issues. That is why I’ve created this document, to help basically myself the next time I need to fix and Integration.

Before you start debugging the issue, confirm the following:

  1. Do a restart of the AOS server and the Project Server
  2. Run a full Compile on the AOT
  3. Run a full Compile on the CIL
  4. Restart IIS on the project server
  5. Restart Services on project server
    1. “Project integration service”
    2. “Project proxy Service”
  • Check Event Log for any errors
  • Restart Service on Project / AOS Server
    “Microsoft Dynamics AX 2012 Synchronization Service”
    Check Event Log for any errors
  • Within the “Microsoft Dynamics AX Configuration Utility”
    Refresh the WCF
    You might want to check the Configuration by logging into the system for the user that is logged in for the “Microsoft Dynamics AX 2012 Synchronization Service”
  • Make sure the 2 batch jobs are running:
    “Updates for Microsoft Project Server Integration”
    “Process transactions for synchronisation service”
  • Make sure the Batch server is setup and running
  • You Must Manually Run PSCONFIG after Installing SharePoint 2010 Patches
    Open an Administrative command prompt.
    Change directory to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN
    Run PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures
  • Resolving Errors

    Error: ”Microsoft Project Server integration settings” form, Integration status stuck in “in progress”

    Error: “Integration log”, Transactions status stuck in Waiting


    i. Check the Default Business Connector setting for the Business Connector user. You might have to log into the system with the user that is running the Service to make sure the business connector setting is correct
    ii. The Batch Job History for:
    1. Updates for Microsoft Project Server Integration
    2. Process transactions for synchronisation service
    3. History of the Batch Job: “Process transactions for synchronisation service” is “Cancelled”
    a. Remove the Batch Job: “Process transactions for synchronisation service”
    b. Reinstall the Batch job, by running the Class:
    i. SyncTransProcess
    c. To Manually run / debug the class: SyncTransProcess, create a new job, with the following code:
    SyncTransProcess s = new SyncTransProcess();

    4. When running Project Server Provisioning you get error: failed
    a. Error:
    i. Failed to provision site PWA with error: Microsoft.Office.Project.Server.Administration.ProvisionException: Post provision setup failed. —> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. —> Microsoft.SharePoint.Upgrade.SPUpgradeCompatibilityException: There is a compatibility range mismatch between the Web server and database “ProjectServer_Published”, and connections to the data have been blocked to due to this incompatibility. This can happen when a content database has not been upgraded to be within the compatibility range of the Web server, or if the database has been upgraded to a higher level than the web server. The Web server and the database must be upgraded to the same version and build level to return to compatibility range.
    b. When:
    i. Sharepoint Central Administration > Manage Service Applications > Project Server > Create Project Web App Site
    c. Fix:
    i. Run the PSConfig command from above to upgrade all websites

    5. Error within Browse:
    a. Error Message: “An unexpected error has occurred.
    Troubleshoot issues with Microsoft SharePoint Foundation.
    Correlation ID: a0ffa929-3fb6-4cbf-87f1-a34dfa89f112
    Date and Time: 11/8/2013 2:43:56 PM“
    b. When:
    Within the Browser, when accessing the Projects Website.
    c. Resolve:
    i. Download:
    ii. Open ULSViewer
    iii. Filter according to CorrelationId
    iv. View Error message

    6. Integration Log Errors
    a. Error 1:
    An error occurred while synchronizing Project entity type of Name:”EXCHANGE SERVER”


    An error occurred while creating the Project compound entity of EntityId:0cfcb10d-4053-4281-a42f-d0bcde7a13e3, Name:”EXCHANGE SERVER” in project server.
    Error: ProjectServerError(s) LastError=CICOAlreadyCheckedOutToYou Instructions: Pass this into PSClientError constructor to access all error information
    PSCLientError Output:

    at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)”
    ii. Resolve:
    1. Check in all Objects on the Project Server.
    2. Within Integration log, Click Action, Resynchronize.

    b. Error 2:
    An error occurred while synchronizing Project entity type of Name:”HR”
    An error occurred while creating the Project compound entity of EntityId:d48e03fe-15f4-48a5-88a9-1859b8ca0e3a, Name:”HR” in project server.
    The underlying connection was closed: An unexpected error occurred on a receive.
    Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
    An existing connection was forcibly closed by the remote host
    at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request) at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Microsoft.Dynamics.SyncServices.Library.PSIProxy.Project.ReadProjectList() at Microsoft.Dynamics.SyncServices.Library.ProjServerQuery.ReadProjectUIDByName(String projName) at Microsoft.Dynamics.SyncServices.Adapter.PSEntityAdapter.CreateProject(IDataContainer ProjectContainer) at Microsoft.Dynamics.SyncServices.Adapter.PSEntityAdapter.CreateCompoundEntity(IDataContainer CompoundContainer)
    at Microsoft.Dynamics.SyncServices.Adapter.PSEntityAdapter.CreateCompoundEntity(IDataContainer CompoundContainer) at Microsoft.Dynamics.SyncServices.EntityManager.SynchronizeEntityTrans(String companyId, Guid syncTransId, SerializableContainer _sEntityTrans)
    ii. Resolve:
    1. Within Integration log, Click Action, Resynchronize.

    This entry was posted in Microsoft Dynamics AX 2012, Project Server 2010. Bookmark the permalink.

    One Response to Microsoft Project Server 2010 and Microsoft Dynamics AX 2012 Integration Issue Resolver

    1. Gokula Doss says:

      ICS is currently using MS Dynamics AX 2012 R2 CU7 with Project Management and Accounting (PMA) implemented along with Finance, HR, Trade & Logistics, Discrete and Production modules. The functionalities of PMA on AX 2012 is not even on par with basic features available on MS Project Standard 2007.

      We are using MS Project Server 2013 & Share Point 2013. We would welcome suggestions, leads, your experiences and any potential consulting services based on your own hands-on successful implementation of automated interfaces between MS Project Server 2013 and AX 2012 R2 or R3.
      Gokula Doss
      Please visit our website and contact PMO using the main contact telephone #.[March 22, 2015]

    Leave a Reply

    Your email address will not be published. Required fields are marked *