Upgraded GP 2010 to GP 2013 in the testing lab, everything is working. However, after I restored the latest production GP 2010 database from the backup to GP 2013, I got the error message on the second login "company" screen, saying "A get/change first operation on table 'MC_SETP' failed accessing SQL data", and clicked the more info button, it shows "number of results columns doesn't match definition."
How to fix this problem? Please help.
Thanks,
Kevin
*This post is locked for comments
Hello,
I can confirm what others have said in this post. If you get this error, it means the company database you are trying to login to is hosed. It's missing some objects that are expected during the login process. That usually happens when someone restores an older version of the company database to a newer build of GP.
Never, ever, ever restore a company database from a different server unless you know that it's on the exact build of GP as you have installed.
Rob Klaproth
Dynamics Credentialed Professional (Instal & Config)
GP Consultant
Armanino, LLP
Hi Kevin,
Would you mind sharing the scripts you ran against the company database to complete the upgrade and SQL server transfer? Thanks.
Regards,
Zen
I have the same problem after I restored a 2005 database company to a 2012 gp2013 box. I run GP Utilities but i'm not seeing a option to update the company
Hi Richard,
Thanks. Unfortunately the person who did this did not make the backup of GP 2013, he restored GP 2010 database after the GP 2013 upgrade was finished.
But the default GP TEST company has the same database as this restored company, the schema is the same. So I restored the TEST company database back to the affected company database, but I need to run a couple of scripts to against the company database, so it has the same company information registered in system database and Dynamic database, then it worked.
Regards,
Kevin
Well now it is getting complicated. Do you have a backup made immediately after the initial 2013 upgrade? If so, you can simply restore that table for the affected company.
If you need to go back to the 2010 tables, you need to restore Dynamics and if you do not restore all of the companies, THEY will then be out of date with the Dynamics version table and the system will try to upgrade them from 2013 to 2013 since it believes they are 2010. Yes, you would need to do all of them.
Hi Richard,
I have a couple of different company databases, do I need to restore all of them or just the affected company database? What about Dynamics database, do I also need to restore it with GP 2010?
Thanks a lot for your help.
Regards,
Kevin
Sorry, no. There are database changes and the error you are getting is saying your 2013 code is opening a 2010 table that is not structured as expected. Yes, the upgrade can run in place but it changes the db structure.
You need to restore the 2010 database and run GP utilities to allow it to by updated to 2013.
Hi Sanjay,
Thanks.
Yes, I saw that article. But my case is different from the one described in that article. the SQL database are the same on GP2103 and GP2010 because the upgrade of GP 2013 is directly on the same server GP 2010 was running. The issue is I restored a company database from GP 2010 to GP 2013, because the table schema are difference between GP 2010 and GP 2013, I got the failed accessing sql data error. I am looking for the solution how to resolve this issue.
Thanks,
Kevin
There is version mismatch between database and GP install. check this article.
Thanks
Sanjay
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,269
Super User 2024 Season 2
#2
Martin Dráb
230,198
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (