Integration Manager Error: ‘Input string was not in a correct format’

Microsoft Dynamics GPI was working on a new integration template for a client recently and after accidentally closed Integration Manager instead of just the Destination Mappings window I started getting the below error message when I reopened and tried running the integration:

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

It took me a few minutes of fiddling around to work out the problem, but when I did it was a bit of a face/palm moment.

The project I was working on had some customisations in Microsoft Dynamics GP as well as a new integration template. When I logged in first thing I had started GP using Run as Administrator and then launched Integration Manager from the Tools menu (Microsoft Dynamics GP menu >> Tools >> Integrate >> Integration Manager); but, when reopening it, I had launched it from the Windows Start screen.

This meant that GP itself was running under the administrator account, but Integration Manager was running under my user account. I closed Integration Manager again and then launched it from the GP menu, so that it was running under the same user account as GP itself, and was able to run the integration without further problems.

Integration Manager – Input String Was Not In A Correct Format

After 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.

Integration Manager 11 Installation Errors

Well, the old ones are often the best. I needed to install Integration Manager onto a system earlier and got an access denied error message the first time I tried to start it;

Integration Manager - Could not create all default application data due to the following error: - Access to the path 'C:\ProgramData\Microsoft\Microsoft Dynamics GP\11.0.0.0' is deniedCould not create all default application data due to the following error: – Access to the path ‘C:\ProgramData\Microsoft\Microsoft Dynamics GP\11.0.0.0′ is denied

Continue reading

Installing Microsoft Dynamics GP 2010 – Insufficient Privileges To Modify The VBA Project Error

Microsoft Dynamics GPI upgraded a clients test system from Microsoft Dynamics GP 10 SP3 to 2010 R2 successfully on the main system such as installing the main client and upgrading the system and company databases.

The client has a few modified reports on the system which needed to be brought across to Microsoft Dynamics GP 2010. These reports were exported from Customisation Maintenance (Microsoft Dynamics GP menu >> Tools >> Customise >> Customisation Maintenance);

Customisation Maintenance

Continue reading