Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry


After you install Integration Manager for Microsoft Dynamics GP or Integration Manager for Microsoft Business Solutions - Great Plains, Automation errors are returned as follows.

  • When you run an integration in Integration Manager, you receive one of the following error messages.

    Error message 1

    The destination could not be initialized due to the following problem: ActiveX component can't create object

    Error message 2

    Automation Error Library not registered.

  • When you open Integration Manager, you receive the following error message:

    Automation Error: The object invoked has been disconnected from its clients.


This problem occurs because the installation of Microsoft Dynamics GP or of Microsoft Great Plains was not written to the registry correctly.


Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To resolve this problem, follow these steps:

  1. Make sure that you have the following registry subkey:

    HKEY_CLASSES_ROOT\CLSID\{6D016639-BA35-11CF-827E-00001B27AB13}\LocalServer32To do this, follow these steps:

    1. Click Start, click Run, type regedit, and then click OK.

    2. On the Edit menu, click Find.

    3. In the Find What box, type 6D016639-BA35-11CF-827E-00001B27AB13.

    4. In the Look at section, make sure that only the Keys check box is selected, and then click Find Next. If you have the registry subkey, you will see the full path of the Dynamics.exe file in the LocalServer32 folder.

  2. If you do not have this registry subkey, the subkey will be created when you reregister the Dynamics.exe file in step 4.

    Note After you reregister the Dynamics.exe file, repeat step 1a through step 1d to verify that the subkey was created by using the correct path.

  3. Log on as the user who is receiving the error message.

  4. Reregister the Dynamics.exe file.

    To reregister any .exe file, click Start, click Run, type "<path>\NameOfFile.exe" /REGSERVER, and then click OK.

    Note The placeholder <path> represents the full path of the folder that contains the file, and the placeholder NameOfFile.exe represents the name of the file. For example, type the following string:

    "C:\Program Files\MyAppLocation\MyApp.exe" /REGSERVER

    Most executables do not display any message boxes when they are registered. This behavior depends on how the application is created. When some applications are registered, they may open on your computer.

  5. Verify the path of the registry subkey again to make sure that the path points to the Dynamics.exe file. To do this, repeat steps 1a through 1d.

  6. Try to open Integration Manager or to run the integration. If the Automation errors are not resolved, you must reregister the following files:

    • IM.exe

    • IMRun.exe

    To reregister these files, follow these steps:

    1. Log on to the computer as the user who will run the integration.

      Note You must reregister the IM.exe and IMRun.exe files by using this user ID.

    2. Reregister each file by following the procedure that is described in step 4.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!