First article of a series about DR & BC planning. Experience from the trenches.
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
Ever wondered where GP Utilities pulls the default values for the file location of a new company in GP ?
See how you can quickly fix a pop-up error that might come in GP and is related to the table SY00100.
What the heck is the DMU you might ask ? DMU stands for Dynamics Maintenance Utility and is provided out-of-the-box by Microsoft when you install the GP client (or at least it was until it was gone missing in the 2018 R2 image.. see more here) In essence, this is what the GP administration guide... Continue Reading →