PRB: SQL Executive Service Fails to Start

 Last reviewed: April 9, 1997
Article ID: Q158585
The information in this article applies to:
  • Microsoft SQL Server, version 6.5

SUMMARY

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 will show the following information: 

   Event: 109
   Source: SQLExecutive
   Description: This version of SQLExecutive requires SQL Server version
   6.5 or later.

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 to access the above registry key, the service will fail to start. If the SQL Executive service is enabled to use a log file, the log file will indicate a SQL Server version of 0.00.000.

To resolve this problem, verify that the SQL Executive service is running under an account that has the proper registry privileges to the above 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
Version : 6.5
Platform : WINDOWS
Issue type : kbprb

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 9, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.