Integration Manager – Cannot Create ActiveX Component

Microsoft Dynamics GPI’ve probably said this before, but Integration Manager can be both very useful and also most infuriating, because when you get an error the error message usually isn’t useful.

However, my most recent problem with Integration Manager did actually produce a useful error message:

Integration Manager - Integration 'Invoices' is not ready to run due to the following problems: The destination could not be initialized due to the following problem: Cannot create ActiveX component.

Integration Manager

Integration 'Invoices' is not ready to run due to the following problems:
- The destination could not be initialized due to the following problem:

Cannot create ActiveX component.

I did a search and found a most useful KB article from Microsoft which detailed the problem (Microsoft Dynamics GP hadn’t been written to the registry correctly) and also the solution.

I read the whole article and decided to try a shortcut of starting with step 3 of re-registering the Dynamics.exe. To do this open a Run or Command Prompt and type the following (this particular problem was encountered with Microsoft Dynamics GP 20103 R2):

"C:\Program Files (x86)\Microsoft Dynamics\GP2013\Dynamics.exe" /regsrver

When I retried the integration, it ran through without further problems.

What should we write about next?

If there is a topic which fits the typical ones of this site, which you would like to see me write about, please use the form, below, to submit your idea.

Your Name

Your Email

Suggested Topic

Suggestion Details

Looking for support or consultancy with Microsoft Dynamics GP?

I no longer work with Microsoft Dynamics GP, but the last company I worked for was ISC Software in the UK; if you’re looking for support or consultancy services with Microsoft Dynamics GP you can contact them here.

5 thoughts on “Integration Manager – Cannot Create ActiveX Component

  1. Hi Ian,

    Something interesting I just found. I was getting this ActiveX error on a client terminal server. Launching GP and IM as administrator got rid of the error without any other changes.

    -Victoria

    1. Ian Grieve says:

      Hi Victoria,

      I guess launching them as an admin gives the permissions they need to make the relevant update to the registry. If/when I get this again I’ll try your approach.

      Thanks.

Leave a Reply

Your email address will not be published. Required fields are marked *