Where does the issue originate, Mekorma, GP, or other third party?

June 19, 2019 149 2164

If you are encountering an issue of incorrect data, unknown error,  processing checks, EFT's,SQL or GP related error messages, the first troubleshooting step will be to determine the product that is responsible for the issue at-hand. To isolate the cause of the problem, it is important to run the same process that presented the issue by removing Mekorma from the Dynamics.set file or disabling Mekorma Alternate Windows Security in order to test and verify the origin of the issue, especially in cases involving unexpected data on stub or check reports.  Keep in mind the primary function of Mekorma Payment Hub (MICR)  is to format data. It is our experience that when the data printed on the checks or stubs is incorrect, the problem lies with the base data (GP) rather than with the formatting or formatted data. To help isolate the cause of this type of problem it is important to print the same check as a Mekorma check and then as a standard GP check to make a comparison.

The most effective test recommendation is the removal of Mekorma from the Dynamics.set file and Mekorma related .dll's.

Recommended method to test by launching GP without Mekorma in the Dynamics.set file:

The recommended method to test by launching GP without Mekorma in the Dynamics.set file:

1. Log out of GP
2. Go to GP Root/Addins folder in Windows Explorer
3. Create a backup folder called “TEMP” and move the following (3) files into the TEMP folder:


MeepConnectorInterface.dll
Mekorma.MultiBatchManagement.dll
MEP_Support_Tool.dll

4. Go to the GP Root Folder and find the file [Mekorma.Dynamics-{somedate}_xxxx. set] rename to Dynamics-xxxxxxxx_xxxx.set

5. Change Windows sort view to By File Name, Drag and drop this set file (step #4) over the Dynamics.exe to launch GP without Mekorma
6. Once the test is completed, move those Mekorma DLL files back from the Temp folder to the Addins folder and Run GP as before from the launch icon.

NOTE: The .set file's appended name (step #4) will reflect the date the file was created by the Mekorma installer before writing to the regular Dynamics.set file with Mekorma products. At the time of Mekorma installation the process made a copy of the Dynamics.set file before installing Mekorma and made a copy by renaming the file to Dynamics-{somedate}_xxxx.set for the purposes of launching GP without Mekorma.