Here is a strange case that happened to a customer today which is using Management Reporter 2012 CU15 and GP 2015 (I know they are behind on an unsupported version, but that's not part of the problem). The financial controller of the company generated a report in GP that they've been using for years now... Continue Reading →
From time to time I get a call from customers that are using Dynamics IM (Integration Manager) in conjunction with their GP client. I recent call was about a new user that got setup on a brand new Windows 10 workstation and when trying to run the first time an integration about Sales Invoices in... Continue Reading →
Just in time for the Dynamics Community Summit North America 2020, the all new Dynamics GP 18.3 version has been released today for download from the Customer Source (Partner will have to get it from the same place, as Partner Source was officially retired and disabled by October 1st, 2020). This is a quick overview... Continue Reading →
Another round of MS Office updates screwed up your GP client by preventing the Word Template to open after they get generated.
After much waiting, the latest build 28 of GP Power Tools (GPPT) has been release today by David Musgrave.. I have been participating in the development of this new build by helping out BETA testing for this version since early spring 2020 and the more the testing went on, the more features got added, as... Continue Reading →
This is quite a common error message you may get in Dynamics GP when trying to post a GL Batch in Financial. The full message actually starts with "The Stored procedure glpPostBatch returned the following results: DBMS: 0, Microsoft Dynamics GP: 20052" And that is the problem. The message means nothing and doesn't give you... Continue Reading →
Most of you may be aware that during the initial GP setup with GP Utilities you define a 1-5 digit company ID / DB Name, but what most don't know is how this can have deep implication in the global setup of your GP instance. First and foremost the basics: the information about the company... Continue Reading →
Today I was upgrading a client’s UAT system from GP 2018R2 to the October release 2019 of GP and added manually a custom dictionary the client had since GP 10.. While there was no specific install routine for this custom code, I simply added it to the DYNAMICS.SET launch file in 2nd position.. Soon as I tried to run GP, I got prompted for a SQL login with the ‘sa’ user… read on David’s post why this happens and how to easily fix it.
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.
View original post 657 more words