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.
Microsoft Dynamics GP 2015 R2 added lots of new features and enhancements and fixed a number of bugs too. However, it also introduced a change that is now causing errors in some ISV’s (Independent Software Vendor) products.
I first came across this issue when preparing to release GP Power Tools build 22 and was testing the Database Validation feature on my Microsoft Dynamics GP 2016 install.
I have finally taken the plunge and updated my primary machine, a Surface Pro 3, to Windows 10.
I delayed the installation of Windows 10 for a little while primarily because I wanted to get GP Power Tools released and did not want anything to mess up my development environments.
While working on testing GP Power Tools, I had to investigate an issue with GP Power Tools running on the Microsoft Dynamics GP 2015 Web Client, and discovered a bug which can crash the web client.
The problem I was seeing was just by having GP Power Tools installed, the web client would crash after login or when opening the first window. Note that this issue is resolved now.
It has been a while since I last posted on the blog. I have been working flat out to finalize the GP Power Tools code and documentation. All I can say is that the Microsoft Dynamics GP community will be amazed with some of the new features and will love the improvements above and beyond the Support Debugging Tool. I will be starting a “What’s New” in GP Power Tools series of posts soon.
Anyhow, the subject of today’s post is an issue in Microsoft Dynamics GP 2015 that I discovered while testing the GP Power Tools code.