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.
This post isn't dealing directly with Dynamics GP, but the process I went thru might actually apply equally well, so keep reading and feel free to add your comment. Last week a customer contacted me to proceed with some data structure changes in one of their database. It wasn't a big deal as they wanted... Continue Reading →
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.
