Resolution 1: Remove Business Contact ManagerIf you do not use Business Contact Manager, you can resolve this problem by removing the component. To do this, you must use Add or Remove Programs. After the componentis removed, you must repair Integration Manager. To delete BusinessContactManager and to repair Integration Manager, follow these steps:
- Click Start, point to Programs, click Control Panel, double-clickAdd or Remove Programs,click Business Contact Manager, and then click Remove.
- In Add orRemove Programs, selectIntegration Manager, clickChange/Remove, and then click Repair.
- If you continue to receive the error message, repeatthis procedure by clicking Modify in step 2 instead of Repair. Then select to install alladapters.
Resolution 2: Force the registry to use correct COM engine filesIf you use Business Contact Manager, you can resolve this problem by creating an IM.EXE.LOCAL file to force the registry to use the correct Windows COM engine files for Integration Manager. To do this, follow these steps:
- Start Notepad, and leave the pad blank.
- Click File, and then click Save As.
- Change the value of the Save as type field to All Files.
- In the File name field, type IM.EXE.LOCAL. Then save the file in the same folder in which Integration Manager (IM.exe) is installed.
Note If a file has the same name as the client application, and if the file name has the .LOCAL extension, the COM engine checks to determine whether the COM server is in the local directory instead of loading it from the folder in the registry.
- Copy the CBOMLib.dll and the CBOMLibX.dll files into the same folder as the IM.exe and the IM.EXE.LOCAL files. When the IM.exe file is opened from this folder, the IM.exe file uses the local copies of the CBOMLib.dll and CBOMLibX.dll files instead of the files that are identified in the registry.
Note Because Business Contact Manager was installed after Integration Manager, the registry points to the Business Contact Manager copies of those files. These copies are the same as those for Integration Manager 7.0.
The issue that is described in the Symptoms section does not apply to Microsoft Dynamics GP 10.0.
Article ID: 862158 - Last Review: 30 Dec 2014 - Revision: 1