This issue is probably remote and may not be faced by many of you out there. But I thought I would share this information with you all, just in case.
Issue: I was upgrading my GP 2013 to GP 2015. By the time, GP Utilities (almost) finished, it got stuck with an error while updating the table SY_Company_MSTR (Company Master) as shown below. I have tried to capture the entire error details on one screen:
Error Explanation on Table Error Details had more information that I could not capture above. Below is that additional information. I’d rather say, that’s the exact error message:
While that greyed portion denotes a company DB name.
Reason: I copied one company database (out of 8) backup from my production environment, restored it on my test machine and ran the utilities to upgrade to GP 2015. When Utilities tried to update Company Master table (SY01500, SY_Company_MSTR), it found records pertaining to companies other than one that’s existing on my test machine while it could not find the respective databases physically.
Resolution: If you are going to have less companies on your upgrade scheme than what’s there on your original GP environment, then you must run Clear Companies script. This script will clear all records pertaining to companies that are not physically available on your SQL instance.
Once I cleaned up the company records, my upgrade process went on successfully.
I have never even imagined more than 15-20 companies, and this advise IS needed for all of us.
And this post also answers a major question: Is Dynamics GP really capable of handling loads and transactions? Now a customer having 150+ companies in Dynamics GP 9.0. And we have already got Dynamics GP 2010 with SQL Server 2008 R2.