The issue is Integration Manager only imports a few transactions before failing when using the Standard Adapters for some integrations.
One possible cause for this issue was fixed many months ago in GP Power Tools code, but as not all sites keep up to date with their software, it might still be occurring. A recent support case for this issue is the reason for publishing this article.
The introduction of the Window Position Memory feature in GP Power Tools Build 22 (Released 23-Feb-2017) added the ability for any window in any product dictionary in Microsoft Dynamics GP to remember its position, size and state on a per user basis. There are a number of common maintenance and transaction windows added by default, and additional windows can be added via the user interface for the feature.
In June 2017, it was reported that the Window Position Memory feature was causing issues when Integration Manager was running, causing the integrations to fail prematurely. Removing the appropriate windows from the Window Position Memory feature created a temporary fix, but then you lost the functionality entirely for those windows, even when Integration Manager was not running.
Note: Removing all windows would not work as when the list is entirely empty, the default windows will be added back.
The Build 22 hotfix released 19-Jun-2017, fixed the issue by disabling both the Window Position Memory and Automatic Window Positioning features in GP Power Tools when Integration Manager is running. GP Power Tools no longer attempts to move or resize windows during integrations.
At the time of writing this article, Build 23 has already been released which includes this fix, plus many other fixes and enhancements.
If you have any issues with Integration Manager integrations using the standard adapters failing and have GP Power Tools installed, please make sure you are running the latest build.
For more information and download links, please see the GP Power Tools Portal page:
Thanks for your support.
This article was originally posted on http://www.winthropdc.com/blog.