Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

powershell WMI error: "Could not obtain SQL Server Service information. An attempt to connect to WMI ... failed with the following error: access is denied." Expand / Collapse
Author
Message
Posted Monday, June 20, 2011 3:11 PM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Saturday, August 16, 2014 5:48 AM
Points: 1,862, Visits: 3,602
I get the following error when I launch powershell from SSMS, after right-clicking on a remote SQL instance and choosing "Start powershell":

Warning: Could not obtain SQL Server Service information. An attempt to connect to WMI on server1 failed with the following error: access is denied.


How can I fix this?


__________________________________________________________________________________

Turbocharge Your Database Maintenance With Service Broker: Part 2
Turbocharge Your Database Maintenance With Service Broker: Part 1
Real-Time Tracking of Tempdb Utilization Through Reporting Services
Monitoring Database Blocking Through SCOM 2007 Custom Rules and Alerts
Preparing for the Unthinkable - a Disaster/Recovery Implementation
Post #1128582
Posted Monday, June 20, 2011 4:42 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 7:34 AM
Points: 7,098, Visits: 12,606
What version is the OS is running on the remote server? What version is the database instance?

__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
Post #1128628
Posted Tuesday, June 21, 2011 9:09 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Saturday, August 16, 2014 5:48 AM
Points: 1,862, Visits: 3,602
opc.three (6/20/2011)
What version is the OS is running on the remote server? What version is the database instance?


Thank you for responding.

OS is on Windows 2003 R2, SP2
sql is on SQL 2008 SP2.


__________________________________________________________________________________

Turbocharge Your Database Maintenance With Service Broker: Part 2
Turbocharge Your Database Maintenance With Service Broker: Part 1
Real-Time Tracking of Tempdb Utilization Through Reporting Services
Monitoring Database Blocking Through SCOM 2007 Custom Rules and Alerts
Preparing for the Unthinkable - a Disaster/Recovery Implementation
Post #1129074
Posted Tuesday, June 21, 2011 9:26 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 7:34 AM
Points: 7,098, Visits: 12,606
Please have a look at this MSDN forum post. It references an MSDN article related to SSIS but see the section "Eliminating the "Access Is Denied" Error. The original poster resolved his own issue referencing that article so DCOM settings may be a common root cause to both your issue and the SSIS issue referenced in the article:

http://social.msdn.microsoft.com/Forums/en-NZ/sqltools/thread/7431a5a3-ef26-4e61-8a53-64cd616dcf84


__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
Post #1129082
Posted Tuesday, June 21, 2011 9:27 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Saturday, August 16, 2014 5:48 AM
Points: 1,862, Visits: 3,602
opc.three (6/21/2011)
Please have a look at this MSDN forum post. It references an MSDN article related to SSIS but see the section "Eliminating the "Access Is Denied" Error. The original poster resolved his own issue referencing that article so DCOM settings may be a common root cause to both your issue and the SSIS issue referenced in the article:

http://social.msdn.microsoft.com/Forums/en-NZ/sqltools/thread/7431a5a3-ef26-4e61-8a53-64cd616dcf84


Thank you, I'll check it.


__________________________________________________________________________________

Turbocharge Your Database Maintenance With Service Broker: Part 2
Turbocharge Your Database Maintenance With Service Broker: Part 1
Real-Time Tracking of Tempdb Utilization Through Reporting Services
Monitoring Database Blocking Through SCOM 2007 Custom Rules and Alerts
Preparing for the Unthinkable - a Disaster/Recovery Implementation
Post #1129084
Posted Tuesday, June 21, 2011 9:30 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 7:34 AM
Points: 7,098, Visits: 12,606
You're welcome. If you happen to resolve it and have a moment to post the solution for others that would be great.

__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
Post #1129085
Posted Tuesday, June 21, 2011 9:31 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Saturday, August 16, 2014 5:48 AM
Points: 1,862, Visits: 3,602
For sure.

__________________________________________________________________________________

Turbocharge Your Database Maintenance With Service Broker: Part 2
Turbocharge Your Database Maintenance With Service Broker: Part 1
Real-Time Tracking of Tempdb Utilization Through Reporting Services
Monitoring Database Blocking Through SCOM 2007 Custom Rules and Alerts
Preparing for the Unthinkable - a Disaster/Recovery Implementation
Post #1129087
Posted Friday, July 22, 2011 3:27 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, June 26, 2014 5:18 PM
Points: 7, Visits: 20
Has anyone found a solid fix for this issue? The fix referenced in my MSDN post did not fully resolve the issue for me.
Post #1146946
Posted Thursday, September 8, 2011 12:22 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, May 9, 2014 5:59 PM
Points: 22, Visits: 83
Firewall, RPC/DCOM setting/WMI securtiy might be involved.
The following article might provide some info:
[url=http://sqlbeyond.blogspot.com/2010/05/sql-wmi-permission-issue.html
]http://sqlbeyond.blogspot.com/2010/05/sql-wmi-permission-issue.html[/url]
Post #1172064
Posted Wednesday, November 7, 2012 3:26 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, August 25, 2014 1:38 AM
Points: 12, Visits: 353
I had the same issue and fixed it.

My problem was when launching Configuration Manager I got an error message in relation to WMI which actually caused the problem you saw in powershell. After I ran:
mofcomp "C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof"

Both issues were fixed. I am running sql2008 r2 on win 2008 r2. You might need to change the path above.

By the way, why I found out this was because I tried to connect to a different instance on a different server, I didn't get the error. And that reminded me checking Configuration Manager because I had this issue before.

Let me know if this is also the case for you.
Post #1382197
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse