Spent quite a while trying to familiarize myself with the GP2013 update today. During my test migration I will backup the live databases, restore them to SQL on the test - making sure to following kb878449. My question is, the only way I could possibly screw up anything in the live environment would be creating an ODBC to the live GP server right? By creating a new ODBC connection the test server and using restored data, there shouldn't be any connections to the live environment, right?
Are you using a test company or a test instance of SQL? Or do you have a completely separate test server?
When you run an upgrade, GP Utilities will upgrade all company db's and the Dynamics Db found on the one instance of SQL. If you are using a separate instance of SQL or a completely separate installation on a different server, you are correct.
For you sanity, back up EVERYTHING
BTW, when it comes to training users on 2013, get a copy of our book GP Version 2013 Unleashed. Visit our web site.
Richard L. Whaley Author, Publisher, Consultant
Enhancing your Dynamics Knowledge!
Sorry, was a bit hasty with my original post. I currently have one virtual machine running the live GP. That live server has GP and SQL both installed on it. I've created a new virtual machine (test server) which also has it's own instance of SQL for its own install of GP.
Received the following error after running GP Utilities:
"There was a problem ascertaining product version information. Microsoft Dynamics GP Utilities will now exit. Please check the duinstall.log file for more information.
Here are the contents of the log file:
"Failure encountered ON 6/24/2013 at 10:36:06 AM. Error: Product 414 does not support upgrading from version 10.0.1304. Failure encountered ON 6/24/2013 at 10:36:06 AM. Error: Product 414 does not support upgrading from version 10.0.1071. Failure encountered ON 6/24/2013 at 10:36:06 AM. Error: Product 414 does not support upgrading from version 10.0.1304."
After doing some research, Product 414 refers to the HR module. books.google.com/books
Here is the thing, the HR module was installed quite a long time ago, and nothing was done with it. Going forward we'd like to try to use it, but start fresh with it so the old data does not need to be carried over. What are my options? Try to uninstall just that module on the original GP server, or can I somehow just drop those tables associated with the HR module?
You can run these scripts to reinstalling HR for each company:
Delete DYNAMICS..DB_Upgrade where PRODID = 414 and db_name = 'xxxx'
Delete DYNAMICS..DU000020 where PRODID = 414 and companyID = xx
Delete DYNAMICS..DU000030 where PRODID = 414 and companyID = xx
If you are reinstalling this module for the Dynamics database run the following scripts against Dynamics:
Drop Table SUSPREF
Drop Table HR2APP06
Drop Table AAX10130
You can find the Companyid by running the following script:
select CMPANYID,CMPNYNAM,INTERID from Dynamics..SY01500
Last you need to run the following drop scripts against each company you need to reinstall the module for:
Drop Table HR2NJ01
Drop Table EX010130
Thanks for your post Jonathan. I was actually looking at something similar here: http://dynamicsuser.net/forums/t/46358.aspx
To make sure I have the sequence right, here's how I understand this should be run (please correct me if I'm wrong):
1. Backup and restore DBs to new SQL instance on test server.
2. Run the commands above.
3. Install GP 2013.
4. Run GP Utilities
Edit: I completed the four steps I listed above in my post, but I'm still getting the same error in the duinstall log unfortunately.
The steps appear to be correct. As for your error you should not be receiving anything in regards to the prodid 414 if you ran the scripts against dynamics and then the last couple of scripts against each company database you changed the first set of scripts for.
If you have further issues please open a support case so we can get additional information and stream in.
I completed your steps and these ( http://dynamicsuser.net/forums/t/46358.aspx ). In the duinstall.log now I only have one line instead of three so it looks like most of that HR module has been cleaned out but not all.
Failure encountered ON 6/24/2013 at 2:19:35 PM. Error: Product 414 does not support upgrading from version 10.0.1304.
Failure encountered ON 6/24/2013 at 2:19:35 PM. Error: Product 414 does not support upgrading from version 10.0.1071.
Failure encountered ON 6/24/2013 at 2:19:35 PM. Error: Product 414 does not support upgrading from version 10.0.1304
Failure encountered ON 6/25/2013 at 9:40:57 AM. Error: Product 414 does not support upgrading from version 10.0.1304.
By running the following query on the DYNAMICS db, I still see one line of output: select * from dynamics..db_upgrade where prodid = '414'
db_name PRODID db_verMajor db_verMinor db_verBuild db_verOldMajor db_verOldMinor db_verOldBuild db_status start_time stop_time DEX_ROW_ID DYNAMICS 414 10 0 1304 10 0 1304 0 2009-08-10 16:36:46.077 2009-08-10 16:37:13.610 81
Looking in our CustomerSource Portal now to determine how often/when I can contact support issues such as this. If you can think of anything else, please feel free to post. Thanks for your help.
Edit: If I were to open a case through support, would that be done through CustomerSource or a different site? Looks like that won't be possible without paying due to our "Business Ready Enhancement Plan" contract. Darn!
If our GP2010 is on the latest service pack, any idea how the HR modules (414) wouldn't have been updated?
Edit: May have gotten it. While digging through the DB Upgrade table I found one row of 414 left pointing at the DYNAMICS db. So I had ran the following command for my GP companies, but forgot to include the DYNAMICS db as well.
Getting a different error about the SQL compatibility level now in GP Utilities, but I'll make a different topic if I can't address the issue myself. Hopefully this will be my last post in the topic! Ha
You are NOT upgrading from 2010 to 2013 but from Version 10 to 2013 (version numbers 10. = 10, 11.=2010, 12.=2013)
Restore from backup, install SP5 from Version 10, and try the upgrade again.
I am aware of that Mr. Whaley. Almost everything was at 11 when digging through the tables. The items at 10 were product id 414 which begs my original question, how could that module not have been updated when everything else was already at 11 in my current/live GP 2010 system?
After I got past the SQL compatibility issue (just changed the compatibility (right click on db - properties - options - compatibility level sql 2012), the upgrade in GP Utilities seemed to go fine. Once I get my license, post back on how everything is working in the test environment.
When you did the upgrade,was the HR code included in the installation for GP 2013? If not, then the upgrade would not have known HR was loaded and the HR data would have been left behind at the older version.
Richard E. Wheeler 2013 and 2014 MVP
Member Microsoft Academic Alliance
www.rbsolutions.com Revered Business Solutions Ballston Lake, NY 518-877-0763 x10
I think you're misunderstanding me Richard. My test migration worked after doing some of the sql commands above which effectively removed the outdated HR modules.
What I was wondering though is how was that module not at the same version as the rest of GP 2010 in our current live environment? Our live environment used to be GP 10 back in the day, it was then upgraded to 2010. 2010 has been kept up to date with the latest service packs and hot fixes. How has that HR module not been getting updated while the rest of GP 2010 was?
OK, I see what you are saying but the answer would be the same. When GP 10 was upgraded to GP 2010 on your production server if the HR module was not installed prior to launching GP Utilities it would would not be upgraded. If you look at the DYNAMICS.SET on the production server do you see HR in the list?
Looking in the DYNAMICS.SET file in our GP2010 directory, I do not see HR or anything relating to it.
Was GP ever copied from one server to another? It is sounding like somewhere along the way, GP HR was installed and then a discoinnet occurred between the HR code and the HR data. So you may very well have had the HR code installed on workstations but not on the server and then you came along and upgraded the server but the HR code was not there so the HR data got left behind. Do you still have a backup of your data in GP 2010?