Select the product you need help with
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 ConfigurationArticle ID: 941823 - View products that this article applies to. SYMPTOMSIn 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 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) CAUSEThis 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. RESOLUTIONTo 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:
MORE INFORMATIONWe 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 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:
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. REFERENCESFor 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/microsoft.sqlserver.management.smo.wmi.managedcomputer.aspx)
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/ms684932.aspx)
http://msdn2.microsoft.com/en-us/library/aa394572.aspx
(http://msdn2.microsoft.com/en-us/library/aa394572.aspx)
PropertiesArticle ID: 941823 - Last Review: February 9, 2010 - Revision: 3.0 APPLIES TO
|
Back to the top
