PRB: SQL Executive Service Fails to Start (158585)


The information in this article applies to:

  • Microsoft SQL Server 6.5
This article was previously published under Q158585

SYMPTOMS

The 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: 
   Event: 109
   Source: SQLExecutive
   Description: This version of SQLExecutive requires SQL Server version
   6.5 or later.

STATUS

This 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: 
   HKEY_LOCAL_MACHINE\Software\Microsoft\MSSQLServer\MSSQLServer
   \CurrentVersion

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.
Modification Type:MinorLast Reviewed:2/14/2005
Keywords:kbenv kbprb kbsetup KB158585
©2004 Microsoft Corporation. All rights reserved.