Integration Manager – Input String Was Not In A Correct Format

Microsoft Dynamics GPAfter installing Microsoft Dynamics GP in a new test system, I then installed Integration Manager and tried to run an integration to test.

After clicking the Run button the following message popped up:

Integration Manager: The destination could not be initialized due to the following problem: -Input string was not in a correct formatIntegration Manager: The destination could not be initialized due to the following problem: -Input string was not in a correct format

This error is typically one seen when Microsoft Dynamics GP is not running (I’ve seen it at a few clients running Citrix when they have Integration Manager running on one server and Microsoft Dynamics GP on another), but I had Microsoft Dynamics GP open in the background.

I quickly realised the problem; I had imported some modified reports into GP which contained VBA and to avoid an error I had right clicked and used Run as Administrator when starting Microsoft Dynamics GP, but had started Integration Manager normally.

This meant the two applications were running in different states and Integration Manager could not see Microsoft Dynamics GP.

To resolve the issue I closed Integration Manager and reopened it using the menu in Microsoft Dynamics GP (Microsoft Dynamics GP menu ¯ Integrate ¯ Integration Manager); this is the way I typically recommend clients open it in order to avoid this problem on Citrix XenApp or other ways of publishing applications.

What should we write about next?

Your Name (required) -
Your Email (required) -

(Visited 1,451 times, 1 visits today)

3 thoughts on “Integration Manager – Input String Was Not In A Correct Format

  1. Bill Campbell says:

    Ian, good weekend to you

    Wondering if you might know of another reason for this error. I am the domain admin and I run both IM and GP as Administrator

    Still same error.

    Any suggestions?

    1. Ian Grieve Ian Grieve says:

      Hi Bill,
      I assume from here that you resolved your problem.

      For other readers, GP not running under the same process ID is the most common cause, but as Bill found, a rouge GP session in the background that can’t be seen can also cause this problem to occur.

      Ian

Leave a Reply

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