Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Some or all SQL Server 2005 services are not listed in SQL Server Configuration Manager, or you receive a "No SQL Server 2005 components were found" error message when you perform operations in SQL Server 2005 Surface Area Configuration

Some or all SQL Server 2005 services are not listed in SQL Server Configuration Manager, or you receive a "No SQL Server 2005 components were found" error message when you perform operations in SQL Server 2005 Surface Area Configuration

Symptoms

In Microsoft SQL Server 2005, you open SQL Server Configuration Manager. In the SQL Server Configuration Manager window, you encounter one of the following problems when you click SQL Server 2005 Services:
  • No service is listed.
  • Some services are not listed.
When you perform operations in the SQL Server 2005 Surface Area Configuration window, you receive the following error message:
No SQL Server 2005 components were found on the specified computer. Either no components are installed, or you are not an administrator on this computer. (SQLSAC)

↑ Back to the top

Cause

This problem occurs because the NETWORK SERVICE account has insufficient permissions to query the information about the SQL Server 2005 services.

This problem may occur after you apply some security policies to update the security settings for SQL Server 2005 services. In particular, this problem may occur after you apply a Group Policy to update the security settings.

↑ Back to the top

Resolution

To resolve this problem, make sure that the NETWORK SERVICE account has the READ permission to query the information about the SQL Server 2005 services. To do this, follow these steps:
  1. Open a session in the server that has SQL Server installed. Open the session by using a Windows account that is part of the Domain Administrators group.
  2. Download and then install the Group Policy Management Console if you do not already have the console installed.
  3. Open the Group Policy Managment Console. Then, select the organizational unit where SQL Server is located.
  4. Create a new Group Policy object or edit the existing Group Policy object that is associated with this organizational unit. To edit the existing Group Policy object, right-click Policy Object, and then select Edit. A new Group Policy Object Editor Microsoft Management Console (MMC) appears.
  5. In the Service Name column, double-click SQL Server (Instance_Name).
  6. In the SQL Server (Instance_Name) Properties dialog box, click to select the Define this policy setting check box, select the appropriate startup mode, and then click Edit Security.
  7. In the Security for SQL Server (Instance_Name) dialog box, click NETWORK SERVICE under Group or user names.

    Note If the NETWORK SERVICE account is not listed, add the account before you perform this step.
  8. Under Permissions for NETWORK SERVICE, click to select the Read check box in the Allow column, and then click OK.
  9. Repeat steps 5 through 9 to add the READ permission to the NETWORK SERVICE account for other SQL Server 2005 services.

↑ Back to the top

More Information

We have a good practice to avoid this problem. When you apply security policies, always make sure that the default discretionary access control list (DACL) for the SQL Server 2005 services is not changed. You can add accounts or groups to the security setting of the SQL Server 2005 services if you want the accounts or groups to have the permission to query the service information.

You can run the following command at a command prompt to extract the information about the default DACL for a SQL Server 2005 service:
sc \\[servername] sdshow  SQLService_Name

↑ Back to the top

When you run the SQL Server Configuration Manager tool or the SQL Server 2005 Surface Area Configuration tool, these tools internally create an instance of the ManagedComputer SQL Server Management Objects (SMO) class. These tools iterate through the services collection to obtain the information about the SQL Server 2005 services. When these tools iterate through the services collection, these tools generate the following Windows Management Instrumentation (WMI) queries:
  • SELECT * FROM RegServices
  • SELECT * FROM SqlService
When these tools generate the WMI queries, the SQL Server Web-Based Enterprise Management (WBEM) provider (Sqlmgmprovider.dll) is loaded into the Wmiprvse.exe process. Then, the SQL Server WBEM provider extracts and processes the information about the services of every instance of SQL Server 2005. The information is about the following SQL Server 2005 services:
  • The SQL Server Database Engine service
  • The SQL Server 2005 Reporting Services service
  • The SQL Server 2005 FullText Search service
  • The SQL Server 2005 Agent service
  • The SQL Server 2005 Integration Services service
  • The SQL Server 2005 Analysis Services service
Finally, the ManagedComputer SMO object returns the list of SQL Server 2005 services to these tools.

The Wmiprvse.exe process in which the Sqlmgmprovider.dll file is loaded runs under the security context of the NETWORK SERVICE account. In the Wmiprvse.exe process, a thread executes the code in the Sqlmgmprovider.dll file. When you run these tools, this thread in the Wmiprvse.exe process impersonates the security context of the user who is running these tools.



Additionally, information about some SQL Server 2005 services is still extracted under the security context of NETWORK SERVICE account. If the NETWORK SERVICE account has insufficient permissions to extract the service information, the information about the SQL Server 2005 services is not present in the result set for the WMI queries that are mentioned previously. Therefore, the ManagedComputer SMO object returns an empty list or a partial list of SQL Server 2005 services to these tools.

↑ Back to the top

References

For more information about the ManagedComputer class, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn2.microsoft.com/en-us/library/microsoft.sqlserver.management.smo.wmi.managedcomputer.aspx
For more information about QueryServiceConfig function, visit the following MSDN Web site:
http://msdn2.microsoft.com/en-us/library/ms684932.aspx
For more information about WMI, visit the following MSDN Web site:
http://msdn2.microsoft.com/en-us/library/aa394572.aspx

↑ Back to the top

Keywords: kbsql2005tool, kbexpertiseadvanced, kbtshoot, kbprb, kb

↑ Back to the top

Article Info
Article ID : 941823
Revision : 3
Created on : 4/20/2018
Published on : 4/20/2018
Exists online : False
Views : 106