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 →
I'm still surprised by the number of companies that are using FRx 6.7 in the field as Financial Reporting tool.. Given that it is most often customers that are on an older GP version, like 10 or 2010, it's not much of a surprise that they haven't migrated to MR 2012... If it's not broken,... 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.
