FIX: Upgrade to SQL Server Fails When MSDE Installed from MOD

View products that this article applies to.

This article was previously published under Q234915

IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 (http://support.microsoft.com/kb/256986/EN-US/ ) Description of the Microsoft Windows Registry

BUG #: 55572(SQLBUG_70)

SYMPTOMS

If you install the Microsoft Data Engine (MSDE) from the Office 2000 Developer (MOD) and then try to upgrade to Standard or Desktop SQL Server, the setup fails with the following error:

You cannot install a version which is older (7.00.623) than the version on your machine (7.00.677). Uninstall the older version.

Back to the top

CAUSE

Office 2000 Developer shipped an MSDE build where "Select @@version" will report 7.00.623 but the following registry key will show 7.00.677:

HKEY_LOCAL_MACHINE/Software/Microsoft/MSSQLServer/MSSQLServer/CurrentVersion/CurrentVersion

Back to the top

WORKAROUND

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

Start the Registry Editor (Regedt32.exe).

Locate the CurrentVersion value under the following key in the registry:

  HKEY_LOCAL_MACHINE/Software/Microsoft/MSSQLServer/MSSQLServer/CurrentVersion

From the Edit menu, click Modify, enter 7.00.623, and then click OK.
Quit Registry Editor.

- OR -

If you have a Microsoft Visual Studio 6.0 product, uninstall this version of MSDE and install MSDE for Visual Studio. MSDE for Visual Studio is available from the following:

http://msdn.microsoft.com/vstudio/msde (http://msdn.microsoft.com/vstudio/msde)

Back to the top

STATUS

Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 1 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

232570 (http://support.microsoft.com/kb/232570/ ) INF: How to Obtain Service Pack 1 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0

For more information, contact your primary support provider.

Back to the top

MORE INFORMATION

Applying Service Pack 1 to SQL Server updates the CurrentVersion registry key back to 7.00.623 if the MSDE version was detected as 7.00.677. After installing SP1, this registry key will contain 7.00.623:

HKEY_LOCAL_MACHINE/Software/Microsoft/MSSQLServer/MSSQLServer/CurrentVersion/CurrentVersion

In addition, this registry key will contain 7.00.699, which is the version number returned by the query "select @@version":

HKEY_LOCAL_MACHINE/Software/Microsoft/MSSQLServer/MSSQLServer/CurrentVersion/CSDVersion

For MSDE shipping with Access 2000 (with GUI setup) and Visual Studio 6.0 MSDE, the SQL Server version is 7.00.623 and the CurrentVersion registry key is correctly set to 7.00.623.

Back to the top

REFERENCES

For additional information about how to move databases that are running SQL Server 7.0, click the following article number to view the article in the Microsoft Knowledge Base:

224071 (http://support.microsoft.com/kb/224071/EN-US/ ) INF: Moving SQL Server Databases to a New Location

Back to the top