When upgrading Microsoft Dynamics GP, it is quite common to get one client (often on the SQL Server) updated first and then update the system and company databases using Dynamics GP Utilities. The final step is then to go around the various workstations and upgrade the client application on those machines.
The process of upgrading often entails installing the application in a new folder or un-installing the application and then installing the new version. What this means is that it is very common to start with a new Dex.ini file for the new installation.
Ok, so you ask "What's the problem?".
Well, there are many settings stored for a workstation in the Dex.ini file and if you start with a new Dex.ini, these settings will be lost and will have to be replaced.
I am not going to go through all the Dex.ini settings, but I will highlight a few common ones that can cause issues if they are not copied across when upgrading.
There are many third party or addon products that also use Dex.ini settings. For example: The Support Debugging Tool stores a number of settings including where its setup file is stored, whether Advanced Mode is enabled and the positions and sizes of its windows.
Leslie Vail, The Dynamics Confessor, has a comprehensive list of Dex.ini settings that she has gathered over a number of years:
The Support Debugging Tool's Dex.ini Configuration window can be used to automatically update the Dex.ini file with settings which are the same for all users, for example: OLEPath, but cannot be used for settings that are specific to a workstation, such as ST_MachineID.
So please make sure that you check the Dex.ini settings in your pre upgrade system and make sure that the relevant settings are transferred into your post upgrade system.
Note: You could always copy the Dex.ini across, but you would need to change Initial=TRUE, Synchronize=TRUE and update the many of the paths (eg: DynHelpPath, DexHelpPath, Word Macro File, Letters Directory, ReportDictionaryPath, FormDictionaryPath, etc.).
Hope this is useful.
Thanks David, this helped me resolve running IM as a Remote App on TerminalServer. I was chasing down the wrong path and forgot it could be as simple as the ImPath & ImExecPath settings!
Posting from Jivtesh Singh at About Dynamics, Development and Life
Post from Mark Polino at DynamicAccounting.net
PLEASE READ BEFORE POSTING
Please only post comments relating to the topic of this page.
If you wish to ask a technical question, please use the links in the links section (scroll down, on right hand side) to ask on the Newsgroups or Forums. If you ask on the Newsgroups or Forums, others in the community can respond and the answers are available for everyone in the future.