*This post is locked for comments
*This post is locked for comments
I just went through an identical upgrade to this last month - version 10 GP to version 2013. You need to make sure you are on build 1779 of GP 10 prior to moving forward with your 2013 upgrade - see this post:
Here is a link to my post - 2013 Upgrade Check List
redbeardblogging.blogspot.com/.../the-value-of-checklists-dynamics-gp.html
Product 0, 949 and 3830 are giving you problems, based on your error message. I would recommend making sure you have a current version of SmartList Builder installed, prior to rerunning your utilities, as this product has now been returned to eOne, and is no longer technically a Microsoft Product.
We are facing issue while upgrading from GP2010 (11.00.2320) (SP4) GP2013 SP1. The error we are getting while running the upgrade utilities
Error: Product 3830 does not support upgrading from version 10.0.79.
Error: Product 0 does not support upgrading from version 11.0.2320.
Error: Product 949 does not support upgrading from version 11.0.2279.
Error: Product 3830 does not support upgrading from version 10.0.79.
Error: Product 0 does not support upgrading from version 11.0.2320.
Error: Product 949 does not support upgrading from version 11.0.2279.
My environment information:
OS: Win 2008 R2
SQL: MS SQL 2008 R2
We started the upgrade process from GP10, upgrade from GP10 to GP2010 was successful but when we started upgrade from GP2010 to GP2013 SP1 we started encountering the above error message.
As recommended in some blogs we installed the latest SP available of GP2010 before trying to upgrade.
Please help us to resolve this issue.
That is odd that GP SQL Maintenance did not work as it does the same thing. As long as you are back now that is all that matters.
Thanks Richard. I had tried this earlier and it didnt work. I however found a solution through Janakiram's Blog.
He suggests that we drop and create the tables manually in SQL server instead of using the GP Maintenance->SQL
You can find it here ...
Assuming you are doing a test upgrade, I would try it again and then see what the messages are under Errors/Warnings. If they are about column mismatch I would copy the databases again and this time before you do the upgrade, I would drop the GL10110,GL10111,GL70500 and GL70501 tables. If the messages are tables do not exists I would launch GP first and then go into Maintenance->SQL and drop and recreate these tables. You could even try this on the production server, again assuming you have a backup. These tables are easily repopulated by runing GL reconcile and resetting the GL options. It appears something is wrong with these tables. Either they do not exist of they are the wrong structure.
André Arnaud de Cal...
292,516
Super User 2025 Season 1
Martin Dráb
231,430
Most Valuable Professional
nmaenpaa
101,156