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. Error message when you start the Microsoft Dynamics Project Integration Service for Microsoft Office Project Connector: "Error 1067: The process terminated unexpectedly"

Error message when you start the Microsoft Dynamics Project Integration Service for Microsoft Office Project Connector: "Error 1067: The process terminated unexpectedly"

Symptoms

Consider the following scenario in Microsoft Office Project Connector in Microsoft Dynamics SL:
  • You populate all required fields on the Microsoft Project Connector Setup (PA.MSP.00) screen.
  • You click Save.
  • You click Start to start the Microsoft Office Project Integration Service for Microsoft Office Project Connector.
In this scenario, when you try to start the Project Integration Service for Project Connector, you receive the following error message:

Could not start the Microsoft Dynamics SL Project Integration Service service on Local Computer. Error 1067: The process terminated unexpectedly.


Additionally, you may receive one of the following error messages in MSDSLEventLog:

Error message 1
ServiceUser is not setup in Microsoft Dynamics SL

For more information, see Cause 1.


Error message 2

Error accessing the PSI Proxy – Project Server URL: http://servername:portnumber/PWA/_vti_bin/psi/Microsoft.Dynamics.SL.MSP.CustomPSI.asmx An item with the same key has already been added.

For more information, see Cause 2.

↑ Back to the top

Cause

Cause 1

he Microsoft Dynamics SL databases use SQL Authentication type instead of Windows Authentication type. Microsoft Project Connector requires you to use the Windows Authentication type.

To resolve this problem, see Resolution 1.


Cause 2

This problem occurs if there is more than one ProjectServerSites entry in the Windows Registry on the computer that is running Microsoft Project Server (IIS).

To resolve this problem, see Resolution 2.

↑ Back to the top

Resolution

Resolution 1

Change the authentication type of the database from SQL Authentication to Windows Authentication.

For more information about how to set up Windows Authentication, click the following article number to view the article in the Microsoft Knowledge Base:
942093 How to set up Windows Authentication in Microsoft Dynamics SL 7.0 or later versions


Resolution 2

Remove the additional GUID entry in the ProjectServerSites registry key. To do this, follow these steps.

Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows

  1. Click Start, click Run, and then type regedit.
  2. Locate the following registry subkey:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Dynamics SL\IntServices\ProjectServerSites
  3. Delete both of the registry keys in the ProjectServerSites registry location.
  4. Locate the Microsoft Dynamics SL Project Connector Configuration tool under Administrative Tools on the computer that is running Microsoft Project Server (IIS).
  5. In the Microsoft Dynamics SL Project Connector Configuration tool, select the Run SQL scripts & Update Project Connection Information option, and then run the tool.  

↑ Back to the top

Keywords: kbmbsmigrate, kbmbspartner, kbsurveynew, kbsolomon, kb

↑ Back to the top

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