Most Microsoft Dynamics GP upgrades run through quickly ad without issue but every so often one will encounter a problem. I had one of the upgrades which encountered a problem recently with a client we’d taken over the support from a previous partner.
We always recommend that a test upgrade be done on a standalone server before live to identify exactly this sort of issue. We restored all of the databases onto the new server, installed the client and started the upgrade through GP Utilities; it ran through without issue for a few minutes upgrading several companies before popping up an error window showing there was an issue with the Item Master table:
I selected the line and clicked the Details button to view details of the table:
The returned to the Company Detail window and clicked the Errors/Warnings button:
Unfortunately, all this showed was that there was an error, but no details. Following the recommended action, I enabled logging in the Dex.ini file and ran the upgrade again. When the error popped up again I checked the dex log and found the following error:
It showed that the Item Master (IV00101) could not be dropped as it was being referenced by a SQL object; I did some exploring in SQL and found this was a table function. I created scripts to drop and recreate the functions. Once the functions had been dropped, the upgrade ran successfully and I was able to then recreate the functions.
What should we write about next?
If there is a topic which fits the typical ones of this site, which you would like to see me write about, please use the form, below, to submit your idea.
Hi Ian,
Do you remember what function was causing the problem ? I’m running into the exact same upgrade issue when going from 18.0.628 to 18.4.1384 on IV00101.. GPU doesn’t let me go further.
I dropped some 3rd-party triggers from Nodus that I thought could be the problem and disable some other triggers which I felt were non-standard, but it keeps failing. Did a DEXSQL Trace log and the last records were about counting how many records are in IV00101 and this zDP_DU000010SS_1 which returns a strange conversion error : convertIV00101forGP18R3
This tries obviously to convert a table version from 18.0.728 to 18.3, but that’s not the case here.
Any hint would be greatly appreciate.
Beat
Hi Beat,
In this case it was a custom function specific to only that client.
I have helped someone with a very similar error recently and it was a standard trigger causing the problem. We disabled the trigger, ran the upgrade and switched it back on again.
Ian