Share
Report
445Our customer is moving from local servers to a multi-tenant environment in the cloud. We have done this many times for many customers. They are on GP2013R2 (specifically 12.00.1826). They only have Mekorma MICR for a 3rd party (which our other MT type customers also have). So we first recreate their environment by bringing over all their GP install files and databases. We installed the exact same version of GP and service pack and exact MICR files. Restored the databases (but DYNAMICS is not restored into DYN_XXX due to moving to multi-tenant). And we run through the documentation to have GP recognize DYN_XXX as the new system database, then the last step before being able to launch is to run the DB Maintenance Utility that is installed with GP2013 to update the stored procs, etc. Once we enter our credentials, we get the message "Unable to connect to the SQL Server - The version of Dynamics GP on the client does not match the version of Dynamics GP on the SQL server".
There aren't many articles on this except for when you are truly launching a different version of GP than the data is. Both their current and the new GP installs are at 12.00.1826 and both the DU000020 and DU_Upgrade tables show 12.00.1826. We did not run into this in any of our other MT conversions and are not sure what to do.
ANY guidance is GREATLY appreciated!!!!
*This post is locked for comments
All responses (
Answers (
