Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Error message when performing an upgrade of Microsoft Dynamics GP 2010: "Product 6499 does not support upgrading from version xx.xx.xxxx"


View products that this article applies to.

Symptoms

When performing an upgrade to Microsoft Dynamics GP 2010 or Microsoft Dynamics GP 2013, Utilities performs the version check and gives the following error:


Error: Product 6499 does not support upgrading from version xx.xx.xxxx.


↑ Back to the top


Cause

Usually this error is caused because the Dynamics Online Services module / Product 6499, was removed from the DynUtils.set and possibly the Dynamics.set files within the Microsoft Dynamics GP application directory, and because of this, the Dynamics Online Services module didn't get installed or upgraded to a correct version in order to upgrade to the new version.

Dynamics Online Services / Product 6499 was introduced in Service Pack 5 (10.0.1579) for Microsoft Dynamics GP 10.0 and Service Pack 1 (11.0.1524) for Microsoft Dynamics GP 2010 and is a core module, meaning it gets installed by default, without the installer needing to select this module to be included in the installation.

Because this module is a core module, we do not want to remove it from being included in these versions of Microsoft Dynamics GP because there are other default processes, such as Sales and other modules that will look for this module's tables and other objects and error out if it doesn't find them. Another error that you could potentially run into is an 'Microsoft.Dynamics.GP.OnlineServices.dll' error when users attempt to login to the Microsoft Dynamics GP application.


↑ Back to the top


Resolution

Instead of removing Dynamics Online Services / Product 6499 from the DynUtils.set or Dynamics.set file for Microsoft Dynamics GP, if you're failing on an upgrade and this module has never been used by any company databases, you can reset the module to be installed at the new version of Microsoft Dynamics GP that you're upgrading to.

To do this, make sure to have backups of the DYNAMICS or system database and all company databases for Microsoft Dynamics GP and then run the following scripts before launching Utilities to perform the upgrade:

A. Run the following scripts against the DYNAMICS or system database:
Delete DYNAMICS..DB_UPGRADE where PRODID = 6499
Delete DYNAMICS..DU000020 where PRODID = 6499
Delete DYNAMICS..DU000030 where PRODID = 6499
DROP TABLE DO40100



B. Run the following script against each company database:


DROP TABLE DO03100



C. Make sure your Dynamics GP install that you're launching Utilities from has the 6499/Dynamics Online Services module in both the Dynamics.set and DynUtils.set file and then launch GP Utilities, which will see this module as missing and re-install it anew at the new version and then upgrade all other modules as normal.


↑ Back to the top


Keywords: kbmbspartner, kbmbsmigrate, kbsurveynew, kb

↑ Back to the top

Article Info
Article ID : 2831912
Revision : 1
Created on : 1/7/2017
Published on : 11/6/2013
Exists online : False
Views : 262