This is an issue that I found back in April 2019 and reported to Microsoft. I added it to my list of articles to write up where it sat until today. Now that I have seen it happen “in the wild” and not just on my test system, I thought I better spend some time to get it documented.
The error occurs when launching Microsoft Dynamics GP and can happen on any version since about v8.0. When you launch GP it displays the Dexterity Login Dialog and if you don’t log in, it will generate a couple of error dialogs.
A while back I had a customer site reporting an issue where a small window would open every time a user opens the Sales Transaction Entry (SOP_Entry) window.
This issue only occurs when the GP Power Tools – Administrator Tools module feature to prevent windows opening outside of the visible display is enabled.
Every now and then a support request comes in where a customer has received an error message referencing the ‘MBS_ScreenShot_Forms’ table. These support requests are usually redirected from Microsoft’s support team. The error is caused by environmental issues and are generated from GP Power Tools (or its predecessor, the Support Debugging Tool).
This article explains what can cause the error and provides suggestions on how to modify your environment to avoid the issue re-ocurring.
Recently my Microsoft Dynamics GP 2010 installation started generating errors while navigating around the Homepage and Area Pages. I thought it was due to the recent Windows 10 1809 update, but have since learned that this was not the cause.
I temporarily fixed the issue by removing all objects from the Homepage and only using the application menus for navigation and not using the Area Pages at all.
Today, we have an article from guest author Craig Verster, Senior Microsoft Dynamics GP Consultant at Microchannel Services, who identified an issue that can affect Australian (and potentially other non-US) SQL Server installations.
When installing SQL Server Database Engine the default collation is dependent on the Locale of the operating system.
i.e. If Australia, then Latin1_General_CI_AS is the default collation method.
If USA (which is the default locale), then SQL_Latin1_General_CP1_CI_AS is the default collation method.
Although both these collation methods use code page 1252 they actually work very differently.
Today, I had a report that the latest build 25.1 release of GP Power Tools was causing an Unhandled Script Exception error when opening certain windows within Microsoft Dynamics GP.
I was able to replicate the issue and have released a 25.2 hotfix which resolves the problem.
This article is an informational post to help anyone who might have come across this issue with Integration Manager and is searching online for a solution.
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.