The information in this article applies to:
SYMPTOMSThe SQL Executive service may fail to start if the account that it is running under does not have appropriate permissions to certain registry keys. In such a case, the Windows NT Event Viewer displays the following:
STATUSThis behavior is by design. MORE INFORMATION
Upon startup, the SQL Executive service attempts to read the following
registry key to determine what version of SQL Server is installed, and to
verify that it is version 6.5:
If the account under which SQL Executive is started does not have appropriate permissions (usually full control but read permissions at the minimum) to access the preceding registry key, the service fails to start. To resolve this problem, verify that the SQL Executive service is running under an account that has the proper registry privileges to the preceding key. To view or change registry permissions, use the Windows NT Registry Editor utility (Regedt32.exe). WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk. Additional query words: sql65 user
Keywords : kbenv kbsetup SSrvGen |
Last Reviewed: October 7, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |