A Bug in SalesLogix ERP Sync when not running it on the SalesLogix Server

In an earlier post, I reviewed the ERP Sync component of the Sage ERP Link product.  We had a client who was unable to get ERP Sync to run.  They had everything set up correctly but when the job was executed using the command line switches, the SalesLogix client would open then close without running ERP Sync.

This was caused by a bug in the ERP Sync engine that causes it to incorrectly extract the required .NET assemblies to the wrong path.

When you use .NET extension in SalesLogix (which is what ERP Link is comprised of) the client is supposed to extract the necessary assembly files from the database to a specified client folder.  This works successfully except with ERP Sync.  When you run ERP Sync on a machine other than the SalesLogix server it incorrectly places the .NET assemblies under a folder with the name of the SalesLogix server computer.

Normally the folder location that .NET assemblies are extracted to is located under:

C:Documents and SettingsApplication DataSalesLogixNETPlugins{Local Computer Name} {SalesLogix Alias on local computer}

Where {Local Computer Name} would be the computer name of the local client and {SalesLogix Alias on local computer} is the SalesLogix alias for the current user’s SalesLogix session (like SalesLogix or SalesLogix_Eval, etc.)

The ERP Sync bug places the required assemblies in the following folder path:

C:Documents and SettingsApplication DataSalesLogixNETPlugins{SalesLogix Server Computer Name} {SalesLogix Alias on local computer}

Notice that it creates a folder with the name of the SalesLogix Server computer rather than the local computer.

You have two ways of fixing this:

1 Simply rename the SalesLogix Server folder to the correct local computer name.

2 If this local computer name folder already exists (from some other .NET assembly usage), renaming the folder will not work.  Instead simply copy the contents found under the SalesLogix Server name folder into the local computer name folder.

This is a small thing that is very hard to find unless you know about it. Sage knows about this problem and hopefully they will have a fix in the future.  In the mean time you will need to do the steps above in order to get ERP Sync to work.