Shulou(Shulou.com)05/31 Report--

In this issue, the editor will bring you solutions to the requirements of CDKEY during SQLserver installation. The article is rich in content and analyzes and describes for you from a professional point of view. I hope you can get something after reading this article.

[available] if CD-KEY is required to install sql server 2000, use regedt32 to find the registry, create a DWORD key SafeDLLSearchMode in the following key [HKEY_LOCAL_MACHINE\ SYSTEM\ CurrentControlSet\ Control\ Session Manager] and set the value to 0 Yes, H6TWQ-TQQM8-HXJYG-D69F7-R84VM-2KSVR serial number JCYFH-BYJMR-C4PVV-VD9G3-VXDYG-2003SVR serial number windows 2003 server does not seem to have appeared on previous versions of the operating system to enter CDKEY, but in the windows 2003 server with SP1 and domain controller environment, there is an interface to enter CDKEY during installation, indicating that the product key cannot be verified and CDKEY is wrong? The solution is as follows: environment: windows 2003 server + SP1 Enterprise VOL Domain Control Environment installation

According to the library: SQL 2000 in the input CDKEY interface, enter the CDKEY of the windows server 2003 you have installed and you can continue the installation, instead of the CDKEY of SQL 2000. Hope to be able to give IT practitioners who encounter this problem a help, I wish you success.

If it doesn't work, you can refer to:

On Service Pack 4 (SP 4), you are trying to install Microsoft SQL Server 2000 through Volume license Agreement (VLA) media on a server running Microsoft Windows Server 2003, Microsoft Windows Storage Server 2003, or Microsoft Windows 2000. To do so, you receive the following error message on the SQLServer installation wizard page of CD KEY: the product key solution cannot be verified if the registry is modified correctly by using the Registry Editor or by using other methods to warn of possible Serious problems. These issues may require a reinstallation of the operating system. Microsoft cannot guarantee that it will solve these problems. Modifying the registry is at your own risk.

To resolve this issue, follow these steps:

1. In the SQLServer installation wizard, click cancel.

two。 Start the Registry Editor. To do this, click start, run, type regedt 32, and then OK.

3. Locate and double-click the SafeDllSearchMode registry key. When running a Windows Server 2003 server or storing Windows Server 2003, this registry key is located under the following registry subkey: HKEY_LOCAL_MACHINE\ SYSTEM\ CurrentControlSet\ Control\ Session Manager running with SP 4, Windows 2000 server this registry key is under the following registry subkey: HKEY_LOCAL_MACHINE\ System\ Control\ Session Manager as the DWORD value Note if the SafeDllSearchMode registry key does not exist, create the SafeDllSearchMode registry key.

4. In the numeric data box, change the value from 1 to 0, and then click OK.

5. Exit Registry Editor. 6. Reinstall SQL Server 2000 and install the latest SQL Server

2000 service pack.

7. Restart the server.

The above is the solution that the editor shares with you when you install SQLserver. If you happen to have similar doubts, you might as well refer to the above analysis to understand. If you want to know more about it, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.