Microsoft KB Archive/180499

= PRB: Incorrect Registry Permissions Causes Problems with Setup =

Article ID: 180499

Article Last Modified on 10/26/2007

-

APPLIES TO


 * Microsoft SQL Server 6.0 Standard Edition
 * Microsoft SQL Server 6.5 Standard Edition

-



This article was previously published under Q180499



IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.



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. </li> On the Security menu, click Permissions.</li> Confirm that the Administrators and whoever else is appropriate are listed with Full Control permission.</li> 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.</li> Start SQL Server Setup.</li> 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).</li> Check Set Security Options and confirm that Mixed or Integrated is now selected.</li> Stop and restart the server.</li> Confirm that the server is running in the desired mode. Use ISQL\W to make a trusted connection.</li></ol>

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:

<ol> From a command prompt at the <SQL_root>\Binn directory, run the following command:

setup /t RegistryRebuild = On

NOTE: The RegistryRebuild command above must be typed exactly as shown, including capitalization. A space on either side of the equal sign (=) is required.

You should be prompted for all information regarding the SQL Server installation, starting with the Enter Name And Organization dialog box. Running this command also creates the registry entries and the Program Manager icons.</li> Ensure that SQL Server and SQL Executive start properly. If SQL Server was starting under a Windows NT account (as opposed to the local system) you need to run Control Panel Services and modify the Startup options for MSSQLServer to Log On As the specified Windows NT account.</li></ol>

<div class="moreinformation_section">

MORE INFORMATION
For more information, see the following articles in the Microsoft Knowledge Base:

157805 : BUG: RegistryRebuild Option of Setup Is Not Documented

164167 : INF: Troubleshooting SQL Security Manager Messages

Additional query words: reg gray grey grayed greyed out dim dimmed right rights setting settings admins

Keywords: kbproductlink kbprb KB180499

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.