Skip to main content
All CollectionsBusiness System IntegrationsDynamics GP (Standard/Advance)Implementation
Dynamics GP (Standard/Advance) - Configuring a New Client Machine
Dynamics GP (Standard/Advance) - Configuring a New Client Machine
Micah A. Parker avatar
Written by Micah A. Parker
Updated over 2 years ago

Product: Dynamics GP (Standard/Advance)


Whenever you attempt to setup a new client machine to work with Transaction Manager and Dynamics GP (Standard/Advance) you will need to make sure that the Dynamic Link Library (DLL) the client is using is in sync with the SQL Server Stored Procedures that were installed on your Server.

In order to sync your client machine and your SQL Server you'll want to pull the DLL from a working client and install it onto the new client you're looking to configure.

Note:

This does not apply to Terminal Servers. For Terminal Servers you'll simply need to ensure you've configured your Ports for the Integration Service


Install the Integration Service


In order for your new client machine to connect to Transaction Manager - the first thing you'll want to do is install the Integration Service.

Warning:

By default the Integration Service may attempt to run the Dynamics GP setup.exe for the Integration Service - in which it will prompt you for which installation type you wish to use - you'll want to want to make sure you select the Client version otherwise it will attempt to run SQL Server scripts on your server - which will de-sync all other clients.

Integration Service - Dynamics GP setup.exe

The Integration Service is required to connect Transaction Manager to the DLL.


Method 1. Copy From Working Machine


The best option is to simply grab a DLL from a working machine and copy it over to your new client machine as this will ensure that you're in sync with the rest of your clients.

Stop the Integration Service


On your new client - in order for it to unload the existing DLL that's out of sync, you'll need to first stop the Transaction Manager Integration Service so that it can release it.

Open: Task Manager β†’ Services

Stop: TmoIntegrationService

Stopping the TmoIntegrationService

Note:

If you're using windows services the process will be labeled Transaction Manager Integration Service

Copy the Working DLL over to the Client


Once the Integration Service is stopped - you'll want to go to your working client and grab the DLL from their machine

Note:

It's recommended that you backup your existing DLL first before replacing it with the new one to prevent accidently corrupting a working DLL

Navigate: C:\Program Files (x86)\True Commerce\TmoIntegrationService

Copy from Working Client: Tc.Int.Platform.BSPDynamicsGP.dll

On New Client: Past into same folder and overwrite existing DLL (backup first)

Tc.Int.Platform.BSPDynamicsGP.dll

Check to Ensure DLL is not Blocked


Often Windows will block a DLL after being transferred over the Network or the Internet manually for security reasons. You'll want to make sure that your newly placed DLL did not get blocked during this process.

Right Click: Tc.Int.Platform.BSPDynamicsGP.dll β†’ Properties

Uncheck: Blocked under the General Tab

Note:

If you do not see the Unblock checkbox - this implies your DLL is not blocked and you're safe to proceed

Restart the Integration Service


Once a new DLL has been placed onto your new client machine - you'll need to now restart the Integration Service in order for it to load the new DLL.

Navigate: Task Manager β†’ Services

Start/Restart: TmoIntegrationService

Starting TmoIntegrationService

rev 12/14/22

Did this answer your question?