You receive one of the following Automation error messages when you try to create a new integration by using Integration Manager together with Microsoft Dynamics GP or with Microsoft Business Solutions - Great Plains:
Error message 1
Item '-8' Not in Collection
Error message 2
Class does not support Automation
When you try to open Integration Manager, you may also receive the following error message:
Automation error: Operating system not available
When you install Integration Manager on a client workstation, you receive the following error message:
Internal Error in TTGErrors: Automation error. The operating system cannot run %1.
When you click Details, you receive the following error report:
Could not create object IMProvider.ODBCProvider.
When you click Help on the Integration Manager menu bar, and then you clickAbout Integration Manager, you receivethe following error message:
Class does not support Automation or does not support expected interface
This error occurs if you have Microsoft Office 2003 installed.
This error is caused by a conflict that occurs when Business Contact Manager 2003 and Integration Manager are on the same computer. Business Contact Manager shares the same files and some registry keys asIntegration Manager 9.0, 8.0, and 7.50. Integration Manager 7.0 components were used to build Business Contact Manager. However, a problem occurs when Business Contact Manager and Integration Manager 9.0, 8.0, or 7.50 are installed on the same computer. The problem is that the Windows COM engine at the operating system level searches the registry to find the location of a COM server.
NoteBusiness Contact Manager is available only in Microsoft Office Small Business Edition 2003and in Microsoft Office Professional Edition 2003.
To resolve this problem, use either resolution 1 or 2 depending on whether you use Business Contact Manager. If you do not use Business Contact Manager, you can remove the component by using resolution 1. If you do use Business Contact Manager, you must use resolution 2.
Resolution 1: Remove Business Contact Manager
If 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 files
If 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.
This article was TechKnowledge Document ID:34103
The issue that is described in the Symptoms section does not apply to Microsoft Dynamics GP 10.0.