Well, faster than I could write the previous article, the Microsoft Dynamics Community team and Microsoft Support have resolved the issue with the Connect gadget on the Microsoft Dynamics GP home page, causing Integration Manager to hang.
As mentioned in the previous article, Integration Manager integrations would hang for users not signed on to Connect on the home page. According to my sources, "After further investigation we have determined that during an operational update the url that [Microsoft Dynamics] GP references now requires /default [path] for the connection to be made. In the past the [Connect] system would automatically render the url as /default".
In layman terms, the operational update seem to have removed the default path that the Connect system used to set up automatically for GP to match and perform the signon. Once the URLs between the two systems were different, GP had no way of finding the sign on page.
Well, hope this all does not sound too confusing and frankly, I am just glad that it got fixed this fast. Once again, kudos to the Microsoft Dynamics GP Support and the Microsoft Dynamics Community teams for their quick call to action.
The forums are hot with users and partners reporting an issue with Integration
Manager for Microsoft Dynamics GP 2010 hanging when running an integration.
Everyone seems to agree the issue started sometimes over the past 2 weeks, with most users reporting a normal behavior and the ability to run trouble
free integrations prior to that date.
I should note that I have blogged about other hanging issues in the past here:
The first article above, details what was initially thought to be an issue after a change to the .NET Framework 3.5 was released by Microsoft.
The second article - the follow up - talks about an issue with the Connect gadget on the home page and one of the slides not cycling correctly, causing Integration Manager integrations to lock up.
This time around, Microsoft Support has indentified the problem (integrations hanging) to be, once more with the Connect gadget. The issue this time has been narrowed down to a user not signing in to Connect, which some how affects Integration Manager's ability to run an integration.
The workaround at this time appears to be removing the Connect gadget from the home page, prior to running the integration.
To disable the Connect gadget follow these steps:
1. Click on Customize this page below the toolbar.
2. Click on the Connect checkmark to disable the option.
Since this issue does not cause data loss and nor interferes with the normal operation of the application, and since there's an immediate workaround, chances are it will be put on the back burner long before you will see some fix being issued. So for now the workaround should do.