One of our customers is upgrading from version 9 to 10. This also involves a move to a new server and some eConnect developments. Means that we set everything up on the new server, get the eConnect integrations tested and when all is ready, do the live upgrade and detach and re-attach the databases So, to allow users test the new enviornment, GP 10 was installed on som workstations alongside the current Live GP9. Not an issue, both will co-exist perfectly happily, each with their own ODBC to connect to their relevant server.
However, a day or so after installing GP10 (and having tested that both versions launched and worked OK), a user reports getting the following error message when logging into GP9:
You are using an earlier version of the Dynamics.dic than the one that is currently installed on the network.
Logging into GP10 was fine, so worked our way through all the usual suspects on the 9 install, and went back over the sequence of events since installing GP10 and the error appearing to see what could be the cause. Different Dynamics.dic version? OK – so lets look in the DB_Upgrade table in the Dynamics database – nothing wrong there, all product versions as they should be. Then we looked in the Versions table – DU000020. Aha!! in here the Dynamics Product major Version is set to 10. (The Product ID for Dynamics is ‘0’). This clearly isn’t correct. We manually edited the table to reset the major and minor version numbers to what they should be, and viola, all back to normal. Users logging into 9 without issue.
But what was the cause? We tested in our own test enviornment and failed to re-create the issue…until…we changed the ODBC name when logging into Version 10 and hey presto, the error message re-appears.
It seems that the simple act of launching GP10 and selecting the ODBC that connects to the 9 database…actually causes an update to the DU000020 table. Now, when you do this, of course GP recognises that the data is in version 9 format and tells you to run utilities to update it. This is as you would expect…but even if you close out of GP, the DU000020 table is updated.
Simple fix, but could have been one of those all nighter issues!!
When looking at the DU000020 table, and you have no idea what the major and minor version numbers should be, look for one of the other products that are in synch with the Dynamics.dic version numbers. We used Field Service – product ID ‘949’ – setting the Product ‘0’ version numbers to equal the ‘949’ version numbers.