Check the list here
https://mbs.microsoft.com/customersource/northamerica/GP/support/hot-topics/HOT_TOPIC_MDGP2013Upgrade
This error occurs if you are on the wrong service pack level to allow for upgrading to the next version.
Confirm your upgrade path by checking customersource.
This error can also happen if you are testing an upgrade on a server with a different name from the original server.
To confirm this, run the following SQL scripts
- This will show you the versions of each company.
- Ignore company -1, that's Fabrikam
- SELECT * FROM dynamics.dbo.du000020 where prodid = 0
- To find out the server name run this
- SELECT @@servername
- If it is showing your original production server name, and not your test server name, you will have to update it
- Run the following to set the name to the current test server
- exec sp_dropserver 'oldserver'
- exec sp_addserver 'newserver', 'local'
- Restart SQL server, and check the servername again to confirm it is correct
It is also possible you have "ghost" companies in your Dynamics that do not exist.
To clean these out, run the Clear Companies script on Partnersource
http://support.microsoft.com/kb/855361
If moving from GP 10, upgrade to version 10.00.1868
This link is for 10.00.1868
https://mbs.microsoft.com/partnersource/downloads/taxupdates/usgpye10.htm?printpage=false
Error: Number of results columns does not match table definition
This can also occur if not all of GP's modules were correctly updated from the last upgrade. For example, if a company used AA in GP 10, then stopped using it, but upgraded to GP2010 without installing the AA module for GP2010, the AA tables would never get upgraded, resulting in piece of the database to be at a lower version than the rest of the database.
Generally, this error means you have missed out an upgrade, or a service pack somewhere.
You need to restore your DYNAMICS and company back to a version that was properly upgraded.
(It is not possible to downgrade)
Ensure all of the correct modules are selected.
Run the most recent service pack for that version, then upgrade to the next level, keeping an eye out for errors and resolving them immediately before moving on to any other service packs.
No comments:
Post a Comment