API DLL VersioningOmniRush uses the slgxapi.dll to communicate with the SalesLogix environment. During installation, OmniRush requests the version of SalesLogix you are running and installs the correct dll version. However, OmniRush only includes the major release dll versions (e.g. 3.0, 4.0, 5.0). If you run a minor release or service pack, you should read this entire article.
Additionally, since SalesLogix does not publish api version compatibility information for service pack and minor revisions, in some cases Z-Firm cannot automatically install the correct dll version to run with your SalesLogix system. By default, OmniRush installs the SalesLogix major version slgxapi.dll that you indicate during installation. If the SalesLogix system is a service release or minor release of SalesLogix (5.0 is a major release, 5.2 is a minor release)the correct dll version will need to be installed on the OmniRush server PC (see steps below).
Contact your SalesLogix reseller or SalesLogix technical support if there is any question on the correct version for your environment.
Steps:
Shut down the OmniRush SalesLogix Connector module
Search the entire OmniRush Server hard drive for slgxapi.dll
Any copies found in the search path should be moved out of the search path.
Copy the 'known correct' slgxapi.dll from your SalesLogix installation files to the OmniRush server directory (default: c:\program files\Z-Firm LLC\OmniRush\Server\v5\ )
Or, open the SalesLogix Connector in the OmniRush Administrator, and set the path and file to the Slgxapi.dll (this must be a local path)
Known DLL Versions:
|
Version |
Comment |
|
4.0.0.0 |
Original SalesLogix v4.0 release. |
|
4.0.2.1 |
SalesLogix first Service Release |
|
4.1.1.0 |
SalesLogix v4.1 |
|
5.0.0.1545 |
SalesLogix 5.0 initial release |
The following has been reported by other SalesLogix developers. Z-Firm has not observed this problem with OmniRush and SalesLogix.NET (v5). This is purely FYI:
The initial release of the SalesLogix.net (v5) API DLL (used by all applications that work with the SalesLogix database) has a bug that requires attention from all SalesLogix sites that sync. The problem is that it does not put the SalesLogix sync files in the correct directory. Instead of using the shared logging directory, the DLL creates a directory relative to where it executes from (e.g. under c:\program files\Z-Firm LLC\OmniRush\Server\v5\ ) and puts the sync files there.
The resolution is that these files need to be copied to the central sync directory. This can be automated with a batch file and a scheduler (like techscheduler at www.winutils.com). Note that the batch file should run frequently (say once every 15 or 30 minutes). The Windows AT scheduler cannot schedule activities more than once a day.