Symptom 1: Prompt for a program to suspend during installation.
Solution 1: (Valid for validation)
Start \ Run \ input regedit carriage return
+hkey_local_machine
+system
+currentcontrolset
+control
+session Manager's Filerenameoperations deleted
Solution 2: (I haven't tried ...) )
+hkey_local_machine
+software
+microsoft
+windows
+currentversion
+setup
All the things under the +exceptioncomponents are deleted as follows:
{077acec7-979c-40ab-9835-435ba1511e0d}
{30C7234B-6482-4A55-A11D-ECD9030313F2}
{3FDF25EE-E592-4495-8391-6E9C504DAC2B}
{60204bb3-7078-4f70-8f69-68297621941c} ...
In short, there are several items, delete several items, delete after the restart, and then install SQL Server, will not be prompted to hang up.
Symptom 2:windowsxp SP2 or other non-server version of the operating system cannot install Enterprise Edition.
Solution 1: Go to the Enterprise installation directory, go to the MSDE directory, and run the setup installation. This is the server component Setup program. Reboot the system to find that there is already a server icon in the tray. After that, go to the Enterprise version of the installer, as prompted to normal installation, this still prompts the server components can not be installed, but it does not matter, we have manually installed the server program. In Run enter Regedit open Registry Editor, find [HKEY_LOCAL_MACHINE\Software\Microsoft\MSSqlserver\MSSqlServer], LoginMode the key value, change the default value of 1 to 2, Reboot the computer. Open Enterprise Manager, try to register the connection with SA, success is ok!
Solution 2: Download Tool NTSwitch.exe, convert the current system from workstation to server, OK, reboot. After the reboot may have some problems, you can try several times, restart and try again, some patience ... Oh. Directly run the SQLSERVER2000 Enterprise version of the installation program, successfully passed. There is no hint that the server program cannot be installed, and so on. Install complete, and then convert the system back to workstation, reboot, complete! Either way, remember to play the SQL patch package, and now out to SP4, otherwise such as JDBC connection, there will be problems.
Ok! This is the present I have encountered in the use of the problem, in fact, any search on the internet there are a lot of solutions, summed up here, their convenience, we can also be small for reference! If there are any such problems and solutions, please reply to the top posts!