Microsoft KB Archive/932480

= When you use Microsoft Dynamics Connector for Dynamics GP to integrate records from Microsoft Dynamics GP to Microsoft Dynamics CRM 3.0, the records are not integrated =

Article ID: 932480

Article Last Modified on 8/15/2007

-

APPLIES TO


 * Microsoft Dynamics CRM Connector for Microsoft Dynamics GP, when used with:
 * Microsoft Dynamics CRM 3.0
 * Microsoft Dynamics CRM 3.0

-



SYMPTOMS
When you use Microsoft Dynamics Connector for Dynamics GP to integrate records from Microsoft Dynamics GP to Microsoft Dynamics CRM 3.0, the records are not integrated. Additionally, when you run the uninstall program for Microsoft Dynamics Connector for Dynamics GP, the program cannot remove the eConnect_out entries.

Additionally, the following error message is logged in the Intinstall.log file:

ERROR :RunSqlScripts :RunScriptFile2 :Exception The system cannot find the file specified

at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)

at System.Diagnostics.Process.Start

at Microsoft.MbsIntegration.Setup.SetupUtils.GenericUtils.ExecuteCommand(String execName, String argsList)

at Microsoft.MbsIntegration.Setup.RunSqlScripts.RunScriptFile2(String filePath, String logFilePath, String serverName, String DbName)

ERROR :DBPerms :AddRole :Exception : The role 'int_gpdb_access' does not exist in the current database. int_gpdb_access TESTDOM24\administrator Database=GPDAT;PersistSecurityInfo=False;Server=IDCINT-TEST24\GPDATA;Trusted_Connection=True

ERROR :DBPerms :AddRole :Exception : The role 'int_gpdb_access' does not exist in the current database. int_gpdb_access testdom24\domain admins Database=GPDAT;PersistSecurityInfo=False;Server=IDCINT-TEST24\GPDATA;Trusted_Connection=True

Note The Intinstall.log file is located at the root of the folder in which you installed Microsoft Dynamics Connector for Dynamics GP. This problem occurs if the Microsoft Dynamics GP database belongs to an instance of Microsoft SQL Server 2005.



CAUSE
This problem occurs because the AddGPDBRoles.sql file does not run when you install Microsoft Dynamics Connector for Dynamics GP.

Note The AddGPDBRoles.sql file creates the int_gpdb_access role and the int_gpdynamics_access role for the Microsoft Dynamics GP company database.

The AddGPDBRoles.sql script does not run because the Setup program for the Microsoft Dynamics GP adapter calls the Isqlw method. The instance of Microsoft SQL Server 2005 does not support the Isqlw method.



RESOLUTION
Microsoft Dynamics Connector for Dynamics GP includes the following Setup programs:
 * Microsoft Dynamics GP Adapter
 * Microsoft CRM Integration Server
 * Microsoft CRM Adapter

To resolve this problem, follow these steps before you install Microsoft CRM Integration Server and after you install Microsoft Dynamics GP Adapter:
 * 1) Open SQL Server Management Studio.
 * 2) On the File menu, point to Open, and then click File.
 * 3) Locate and then click the AddGPDBRoles.sql file, and then click Open.

Note By default, the AddGPDBRoles.sql file is in the \Database\GP folder. The  placeholder represents the actual Setup folder for Microsoft Dynamics Connector for Dynamics GP.
 * 1) On the Query menu, click Execute.

Note When this problem occurs, you cannot add the GPAccessUsers object to the int_gpdynamics_access role and to the int_gpdb_access role because these roles have not been created. Therefore, you have to manually add the GPAccessUsers object to the int_gpdynamics_access role and to the int_gpdb_access role after you resolve the problem. To do this, follow these steps:
 * 1) In SQL Server Management Studio, expand the Security folder.
 * 2) Right-click the int_gpdb_access role, and then click Properties.
 * 3) Add the GPAccessUsers object to the role.
 * 4) Repeat steps 2 through 3 for the int_gpdynamics_access role.

Keywords: kberrmsg kbmbsmigrate kbprb kbtshoot KB932480

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.