SQL Server 2005 Surface Area Configuration connection error -
05-12-2008
, 06:15 PM
I have 3 windows xp (sp2) computers running SQL Server 2005 (Dev edition)
with the same SAC connection error as follows:
Computer localhost does not exist on the network, or the computer cannot be
configured remotely. Verify that the remote computer has the required Windows
Management Instrumentation components and then try again. (SQLSAC)
------------------------------
Program Location:
at Microsoft.SqlSac.MainPanel.FormServicesAndProtocol s..ctor(String
machineName)
===================================
An exception occurred in SMO while trying to manage a service.
(Microsoft.SqlServer.Smo)
------------------------------
For help, click:
http://go.microsoft.com/fwlink?ProdN...0&LinkId=20476
------------------------------
Program Location:
at Microsoft.SqlServer.Management.Smo.Wmi.ManagedComp uter.TryConnect()
at Microsoft.SqlServer.Management.Smo.Wmi.WmiSmoObjec t.get_Proxy()
at
Microsoft.SqlServer.Management.Smo.Wmi.WmiSmoObjec t.EnumChildren(String
childTypeName, WmiCollectionBase coll)
at
Microsoft.SqlServer.Management.Smo.Wmi.ServiceColl ection.InitializeChildCollection()
at Microsoft.SqlServer.Management.Smo.Wmi.ServiceColl ection.get_Count()
at Microsoft.SqlSac.MainPanel.SmoAsyncConnection.Conn ect()
===================================
Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
(mscorlib)
------------------------------
Program Location:
at
System.Runtime.InteropServices.Marshal.ThrowExcept ionForHRInternal(Int32
errorCode, IntPtr errorInfo)
at System.Management.ManagementScope.InitializeGuts(O bject o)
at System.Management.ManagementScope.Initialize()
at System.Management.ManagementScope.Connect()
at Microsoft.SqlServer.Management.Smo.Wmi.ManagedComp uter.TryConnect()
The SQL browser service is running as are all the necessary SQL Server
services.
There is no firewall running on either machines.
SQL Management Studio connects fine to all servers.
On a fresh install of SQL Server 2005, SAC can connect. It is not until the
machine is restarted that the error appears.
SAC connects fine on other Windows Server based servers on the network.
Any help greatly appreciated. TIA |