PRB: Incorrect Registry Permissions Causes Problems with Setup (180499)

SYMPTOMS

Improper registry permissions may cause problems with your SQL Server installation. For example, you may encounter the following problems:

During the last portion of the setup process, Setup reports that the registry could not be updated.
You are unable to start SQL server in Integrated or Mixed Security mode.
You start SQL Server Setup, and at the Options screen select Change Network Support. When you click Continue, you receive the following error message:
The network could not be successfully installed. An error occurred while reading the Windows NT registry.

CAUSE

These problems can be caused by improper registry permissions. For example, in the case of the first symptom listed above, SQL Server Setup attempts to update the registry and create the program icons during the end of setup. If the registry is configured so that the Windows NT account that is running the upgrade does not have adequate permission to change the SQL registry keys at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer and its subkeys, Setup will display the error and quit. In the case of the second and third symptoms above, the inability to read the RPCNetLib registry key is the root cause of the problem.

The following are several reasons why the registry may have additional security:

C2 security was applied to the server.
Administrators are attempting to "lock down" the server.
Integrated security is in use (that is, the Windows NT account used to perform the upgrade is NOT a member of the admin group(s)).

WORKAROUND

To work around this problem, do the following:

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it.

Run RegEdt32 to open the registry, and navigate to:
```
      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer

						
```
You may find that the inner MSSQLServer key is unavailable.
On the Security menu, click Permissions.
Confirm that the Administrators and whoever else is appropriate are listed with Full Control permission.
Click to place a check in the Replace Permission On Existing Subkeys check box, and then click OK.

The inner MSSQLServer key should now be available. You can also access the keys under MSSQLServer\MSSQLServer, such as Parameters, CurrentVersion, and RPCNetLib.
Start SQL Server Setup.
Confirm that you can now enter the Change Network Support area, and confirm the desired network libraries are selected (either Named Pipes or Multi-Protocol for Integrated or Mixed security).
Check Set Security Options and confirm that Mixed or Integrated is now selected.
Stop and restart the server.
Confirm that the server is running in the desired mode. Use ISQL\W to make a trusted connection.

Alternatively, if your problem lies in running SQL Server Setup to perform an upgrade, you can also use a Windows NT account that already has the proper permissions to compete the upgrade. To do this, perform the following steps: