WMI Provider Error: Access is denied. [0x80070005] from SQL Server Computer Manager

Published Jan 15 2019 11:15 AM 9,397 Views
Microsoft
First published on MSDN on Jan 04, 2009

When you attempt to change the Login Account for the SQL services [SQL Server, SQL Agent, Full Text, Analysis Services] from the SQL Server Computer Manager tool, you may encounter the following error message:


"WMI Provider Error"


"Access is denied. [0x80070005]"



This post is applicable for SQL Services installed as failover instances on Windows Clusters.


If this is the only operation [changing service startup account] that gives you this error and you can perform all other operations from Computer Manager, then verify the following:

-          When you setup SQL Server, you provided a domain group for cluster services

-          You need to make sure one of the following is true:

o   The Windows user account under which you are running the SQL Server Computer Manager has appropriate permission in the Active Directory to add the new service startup account to the domain group for cluster

o   The new service startup account is already added to the appropriate domain group for cluster. You can specify different domain groups for SQL Server, SQL Agent, Full Text, and Analysis Services. Make sure to add the appropriate service startup account to the correct domain group.

Basically this message is telling you that the SQL Computer Management WMI provider [sqlmgmprovider.dll] attempted to add the new service startup account to the domain group for cluster and it failed with this error.

You will notice the recommended steps for changing service startup accounts in a failover cluster are documented in the Knowledge Base article:

915846 Best practices that you can use to set up domain groups and solutions to problems that may occu...

How to change the service account for a clustered service

To change the service account for a clustered service of SQL Server 2005, follow these steps:



1.


Add the new service account to the domain group of the clustered service.


2.


On one of the cluster nodes, use SQL Server Configuration Manager to change the service account to the new account.

You can actually see what is happening if you turn on the verbose WMI logs:

START >> ADMINISTRATIVE TOOLS >> COMPUTER MANAGEMENT >> SERVICES AND APPLICATIONS >> WMI CONTROL >> PROPERTIES >> LOGGING >> VERBOSE

Change the Log max size to 1 MB

Note down the location of the log files

Save the changes and restart winmgmt service

The framework logs will show the following entries of interest:

GetNamespaceConnection: rootMicrosoftSqlServerComputerManagement  12/26/2008 11:33:53.883       thread:2684

CreateInstanceEnumAsync: SqlService - Succeeded 12/26/2008 11:33:53.883    thread:2684

CWbemProviderGlue::Release, count is (approx) 6 12/26/2008 11:33:53.883    thread:2684

CWbemProviderGlue::AddRef, count is (approx) 7  12/26/2008 11:33:56.352    thread:2684

GetObjectAsync: SqlService.ServiceName="SQLAgent$SQLINST03",SQLServiceType=2      12/26/2008 11:33:56.352       thread:2684

Impersonation running as: SURESHKADCsureshka   12/26/2008 11:33:56.352    thread:2684

GetObjectAsync: SqlService.ServiceName="SQLAgent$SQLINST03",SQLServiceType=2 - Succeeded 12/26/2008 11:33:57.180  thread:2684

CWbemProviderGlue::Release, count is (approx) 6 12/26/2008 11:33:57.180    thread:2684

CWbemProviderGlue::AddRef, count is (approx) 7  12/26/2008 11:34:16.461    thread:2684

GetObjectAsync: SqlService.ServiceName="SQLAgent$SQLINST03",SQLServiceType=2      12/26/2008 11:34:16.461       thread:2684

Impersonation running as: SURESHKADCsureshka   12/26/2008 11:34:16.461    thread:2684

Recognized __GET_EXT_KEYS_ONLY    12/26/2008 11:34:16.461    thread:2684

GetObjectAsync: SqlService.ServiceName="SQLAgent$SQLINST03",SQLServiceType=2 - Succeeded 12/26/2008 11:34:17.305  thread:2684

CWbemProviderGlue::Release, count is (approx) 6 12/26/2008 11:34:17.305    thread:2684

CWbemProviderGlue::AddRef, count is (approx) 7  12/26/2008 11:34:17.305    thread:2684

ExecMethodAsync: SqlService.ServiceName="SQLAgent$SQLINST03",SQLServiceType=2.SetServiceAccount 12/26/2008 11:34:17.305  thread:2684

Impersonation running as: SURESHKADCsureshka   12/26/2008 11:34:17.305    thread:2684

ExecMethodAsync: SqlService.ServiceName="SQLAgent$SQLINST03",SQLServiceType=2.SetServiceAccount - FAILED (80070005)    12/26/2008 11:34:18.352    thread:2684

CWbemProviderGlue::Release, count is (approx) 6 12/26/2008 11:34:18.352    thread:2684

Here you will be able to notice

-          What is the Windows user credentials under which the operation is being performed

-          What specific WMI call failed

-          What was the return code

After this you can debug the SetServiceAccount method in the provider and find out the exact step where it fails. This requires the use of Windows Debugger and symbols for the provider.

This whole concept applies to the setup process also and is well documented in the Books Online topic: Domain Groups for Clustered Services .

The domain groups should have the appropriate service accounts added to them. If the service accounts are not members of the appropriate domain groups at the time Setup is run, Setup will attempt to add them. In this case, the account under which Setup is running must have adequate privileges to add accounts to the domain groups. If SQL Server Setup is run under an account that does not have permission to add users to the domain groups, the users must already be members of the appropriate group.

You can refer to the following article for more information about how the SQL Computer Manager interacts with WMI.

941823 Some or all SQL Server 2005 services are not listed in SQL Server Configuration Manager, or you...

Thanks

Suresh B. Kandoth

SQL Server Escalation Services


%3CLINGO-SUB%20id%3D%22lingo-sub-315620%22%20slang%3D%22en-US%22%3EWMI%20Provider%20Error%3A%20Access%20is%20denied.%20%5B0x80070005%5D%20from%20SQL%20Server%20Computer%20Manager%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-315620%22%20slang%3D%22en-US%22%3E%0A%20%26lt%3Bmeta%20http-equiv%3D%22Content-Type%22%20content%3D%22text%2Fhtml%3B%20charset%3DUTF-8%22%20%2F%26gt%3B%3CSTRONG%3E%20First%20published%20on%20MSDN%20on%20Jan%2004%2C%202009%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3EWhen%20you%20attempt%20to%20change%20the%20Login%20Account%20for%20the%20SQL%20services%20%5BSQL%20Server%2C%20SQL%20Agent%2C%20Full%20Text%2C%20Analysis%20Services%5D%20from%20the%20SQL%20Server%20Computer%20Manager%20tool%2C%20you%20may%20encounter%20the%20following%20error%20message%3A%3C%2FP%3E%0A%20%20%3CP%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%20%20%3CP%3E%22WMI%20Provider%20Error%22%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%22Access%20is%20denied.%20%5B0x80070005%5D%22%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%20%20%3CP%3EThis%20post%20is%20applicable%20for%20SQL%20Services%20installed%20as%20failover%20instances%20on%20Windows%20Clusters.%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3EIf%20this%20is%20the%20only%20operation%20%5Bchanging%20service%20startup%20account%5D%20that%20gives%20you%20this%20error%20and%20you%20can%20perform%20all%20other%20operations%20from%20Computer%20Manager%2C%20then%20verify%20the%20following%3A%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E-%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20When%20you%20setup%20SQL%20Server%2C%20you%20provided%20a%20domain%20group%20for%20cluster%20services%3C%2FP%3E%0A%20%20%3CP%3E-%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20You%20need%20to%20make%20sure%20one%20of%20the%20following%20is%20true%3A%3C%2FP%3E%0A%20%20%3CP%3Eo%26nbsp%3B%26nbsp%3B%20The%20Windows%20user%20account%20under%20which%20you%20are%20running%20the%20SQL%20Server%20Computer%20Manager%20has%20appropriate%20permission%20in%20the%20Active%20Directory%20to%20add%20the%20new%20service%20startup%20account%20to%20the%20domain%20group%20for%20cluster%3C%2FP%3E%0A%20%20%3CP%3Eo%26nbsp%3B%26nbsp%3B%20The%20new%20service%20startup%20account%20is%20already%20added%20to%20the%20appropriate%20domain%20group%20for%20cluster.%20You%20can%20specify%20different%20domain%20groups%20for%20SQL%20Server%2C%20SQL%20Agent%2C%20Full%20Text%2C%20and%20Analysis%20Services.%20Make%20sure%20to%20add%20the%20appropriate%20service%20startup%20account%20to%20the%20correct%20domain%20group.%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3EBasically%20this%20message%20is%20telling%20you%20that%20the%20SQL%20Computer%20Management%20WMI%20provider%20%5Bsqlmgmprovider.dll%5D%20attempted%20to%20add%20the%20new%20service%20startup%20account%20to%20the%20domain%20group%20for%20cluster%20and%20it%20failed%20with%20this%20error.%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3EYou%20will%20notice%20the%20recommended%20steps%20for%20changing%20service%20startup%20accounts%20in%20a%20failover%20cluster%20are%20documented%20in%20the%20Knowledge%20Base%20article%3A%3C%2FP%3E%0A%20%20%3CP%3E915846%20%3CA%20href%3D%22http%3A%2F%2Fsupport.microsoft.com%2Fdefault.aspx%3Fscid%3Dkb%3BEN-US%3B915846%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%20Best%20practices%20that%20you%20can%20use%20to%20set%20up%20domain%20groups%20and%20solutions%20to%20problems%20that%20may%20occur%20when%20you%20set%20up%20a%20domain%20group%20when%20you%20install%20a%20SQL%20Server%202005%20failover%20cluster%20%3C%2FA%3E%3C%2FP%3E%0A%20%20%3CP%3E%3CB%3E%20How%20to%20change%20the%20service%20account%20for%20a%20clustered%20service%20%3C%2FB%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3ETo%20change%20the%20service%20account%20for%20a%20clustered%20service%20of%20SQL%20Server%202005%2C%20follow%20these%20steps%3A%3C%2FP%3E%0A%20%20%3CP%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%20%20%3CTABLE%3E%0A%20%20%20%3CTBODY%3E%3CTR%3E%0A%20%20%20%20%3CTD%3E%3CBR%20%2F%3E%3CP%3E1.%3C%2FP%3E%0A%20%20%20%20%3C%2FTD%3E%0A%20%20%20%20%3CTD%3E%3CBR%20%2F%3E%3CP%3EAdd%20the%20new%20service%20account%20to%20the%20domain%20group%20of%20the%20clustered%20service.%3C%2FP%3E%0A%20%20%20%20%3C%2FTD%3E%0A%20%20%20%3C%2FTR%3E%0A%20%20%20%3CTR%3E%0A%20%20%20%20%3CTD%3E%3CBR%20%2F%3E%3CP%3E2.%3C%2FP%3E%0A%20%20%20%20%3C%2FTD%3E%0A%20%20%20%20%3CTD%3E%3CBR%20%2F%3E%3CP%3EOn%20one%20of%20the%20cluster%20nodes%2C%20use%20SQL%20Server%20Configuration%20Manager%20to%20change%20the%20service%20account%20to%20the%20new%20account.%3C%2FP%3E%0A%20%20%20%20%3C%2FTD%3E%0A%20%20%20%3C%2FTR%3E%0A%20%20%3C%2FTBODY%3E%3C%2FTABLE%3E%0A%20%20%3CP%3EYou%20can%20actually%20see%20what%20is%20happening%20if%20you%20turn%20on%20the%20verbose%20WMI%20logs%3A%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3ESTART%20%26gt%3B%26gt%3B%20ADMINISTRATIVE%20TOOLS%20%26gt%3B%26gt%3B%20COMPUTER%20MANAGEMENT%20%26gt%3B%26gt%3B%20SERVICES%20AND%20APPLICATIONS%20%26gt%3B%26gt%3B%20WMI%20CONTROL%20%26gt%3B%26gt%3B%20PROPERTIES%20%26gt%3B%26gt%3B%20LOGGING%20%26gt%3B%26gt%3B%20VERBOSE%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3EChange%20the%20Log%20max%20size%20to%201%20MB%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3ENote%20down%20the%20location%20of%20the%20log%20files%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3ESave%20the%20changes%20and%20restart%20winmgmt%20service%3C%2FP%3E%0A%20%20%3CP%3EThe%20framework%20logs%20will%20show%20the%20following%20entries%20of%20interest%3A%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3EGetNamespaceConnection%3A%20rootMicrosoftSqlServerComputerManagement%26nbsp%3B%2012%2F26%2F2008%2011%3A33%3A53.883%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20thread%3A2684%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3ECreateInstanceEnumAsync%3A%20SqlService%20-%20Succeeded%2012%2F26%2F2008%2011%3A33%3A53.883%26nbsp%3B%26nbsp%3B%26nbsp%3B%20thread%3A2684%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3ECWbemProviderGlue%3A%3ARelease%2C%20count%20is%20(approx)%206%2012%2F26%2F2008%2011%3A33%3A53.883%26nbsp%3B%26nbsp%3B%26nbsp%3B%20thread%3A2684%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3ECWbemProviderGlue%3A%3AAddRef%2C%20count%20is%20(approx)%207%26nbsp%3B%2012%2F26%2F2008%2011%3A33%3A56.352%26nbsp%3B%26nbsp%3B%26nbsp%3B%20thread%3A2684%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3EGetObjectAsync%3A%20SqlService.ServiceName%3D%22SQLAgent%24SQLINST03%22%2CSQLServiceType%3D2%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%2012%2F26%2F2008%2011%3A33%3A56.352%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20thread%3A2684%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3EImpersonation%20running%20as%3A%20SURESHKADCsureshka%26nbsp%3B%26nbsp%3B%2012%2F26%2F2008%2011%3A33%3A56.352%26nbsp%3B%26nbsp%3B%26nbsp%3B%20thread%3A2684%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3EGetObjectAsync%3A%20SqlService.ServiceName%3D%22SQLAgent%24SQLINST03%22%2CSQLServiceType%3D2%20-%20Succeeded%2012%2F26%2F2008%2011%3A33%3A57.180%26nbsp%3B%20thread%3A2684%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3ECWbemProviderGlue%3A%3ARelease%2C%20count%20is%20(approx)%206%2012%2F26%2F2008%2011%3A33%3A57.180%26nbsp%3B%26nbsp%3B%26nbsp%3B%20thread%3A2684%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3ECWbemProviderGlue%3A%3AAddRef%2C%20count%20is%20(approx)%207%26nbsp%3B%2012%2F26%2F2008%2011%3A34%3A16.461%26nbsp%3B%26nbsp%3B%26nbsp%3B%20thread%3A2684%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3EGetObjectAsync%3A%20SqlService.ServiceName%3D%22SQLAgent%24SQLINST03%22%2CSQLServiceType%3D2%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%2012%2F26%2F2008%2011%3A34%3A16.461%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20thread%3A2684%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3EImpersonation%20running%20as%3A%20SURESHKADCsureshka%26nbsp%3B%26nbsp%3B%2012%2F26%2F2008%2011%3A34%3A16.461%26nbsp%3B%26nbsp%3B%26nbsp%3B%20thread%3A2684%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3ERecognized%20__GET_EXT_KEYS_ONLY%26nbsp%3B%26nbsp%3B%26nbsp%3B%2012%2F26%2F2008%2011%3A34%3A16.461%26nbsp%3B%26nbsp%3B%26nbsp%3B%20thread%3A2684%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3EGetObjectAsync%3A%20SqlService.ServiceName%3D%22SQLAgent%24SQLINST03%22%2CSQLServiceType%3D2%20-%20Succeeded%2012%2F26%2F2008%2011%3A34%3A17.305%26nbsp%3B%20thread%3A2684%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3ECWbemProviderGlue%3A%3ARelease%2C%20count%20is%20(approx)%206%2012%2F26%2F2008%2011%3A34%3A17.305%26nbsp%3B%26nbsp%3B%26nbsp%3B%20thread%3A2684%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3ECWbemProviderGlue%3A%3AAddRef%2C%20count%20is%20(approx)%207%26nbsp%3B%2012%2F26%2F2008%2011%3A34%3A17.305%26nbsp%3B%26nbsp%3B%26nbsp%3B%20thread%3A2684%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3EExecMethodAsync%3A%20SqlService.ServiceName%3D%22SQLAgent%24SQLINST03%22%2CSQLServiceType%3D2.SetServiceAccount%2012%2F26%2F2008%2011%3A34%3A17.305%26nbsp%3B%20thread%3A2684%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3EImpersonation%20running%20as%3A%20SURESHKADCsureshka%26nbsp%3B%26nbsp%3B%2012%2F26%2F2008%2011%3A34%3A17.305%26nbsp%3B%26nbsp%3B%26nbsp%3B%20thread%3A2684%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3EExecMethodAsync%3A%20SqlService.ServiceName%3D%22SQLAgent%24SQLINST03%22%2CSQLServiceType%3D2.SetServiceAccount%20-%20FAILED%20(80070005)%26nbsp%3B%26nbsp%3B%26nbsp%3B%2012%2F26%2F2008%2011%3A34%3A18.352%26nbsp%3B%26nbsp%3B%26nbsp%3B%20thread%3A2684%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3ECWbemProviderGlue%3A%3ARelease%2C%20count%20is%20(approx)%206%2012%2F26%2F2008%2011%3A34%3A18.352%26nbsp%3B%26nbsp%3B%26nbsp%3B%20thread%3A2684%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3EHere%20you%20will%20be%20able%20to%20notice%3C%2FP%3E%0A%20%20%3CP%3E-%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20What%20is%20the%20Windows%20user%20credentials%20under%20which%20the%20operation%20is%20being%20performed%3C%2FP%3E%0A%20%20%3CP%3E-%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20What%20specific%20WMI%20call%20failed%3C%2FP%3E%0A%20%20%3CP%3E-%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20What%20was%20the%20return%20code%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3EAfter%20this%20you%20can%20debug%20the%20SetServiceAccount%20method%20in%20the%20provider%20and%20find%20out%20the%20exact%20step%20where%20it%20fails.%20This%20requires%20the%20use%20of%20Windows%20Debugger%20and%20symbols%20for%20the%20provider.%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3EThis%20whole%20concept%20applies%20to%20the%20setup%20process%20also%20and%20is%20well%20documented%20in%20the%20Books%20Online%20topic%3A%20%3CA%20href%3D%22http%3A%2F%2Fmsdn.microsoft.com%2Fen-us%2Flibrary%2Fms345196(SQL.90).aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%20Domain%20Groups%20for%20Clustered%20Services%20%3C%2FA%3E%20.%3C%2FP%3E%0A%20%20%3CP%3EThe%20domain%20groups%20should%20have%20the%20appropriate%20service%20accounts%20added%20to%20them.%20If%20the%20service%20accounts%20are%20not%20members%20of%20the%20appropriate%20domain%20groups%20at%20the%20time%20Setup%20is%20run%2C%20Setup%20will%20attempt%20to%20add%20them.%20In%20this%20case%2C%20the%20account%20under%20which%20Setup%20is%20running%20must%20have%20adequate%20privileges%20to%20add%20accounts%20to%20the%20domain%20groups.%20If%20SQL%20Server%20Setup%20is%20run%20under%20an%20account%20that%20does%20not%20have%20permission%20to%20add%20users%20to%20the%20domain%20groups%2C%20the%20users%20must%20already%20be%20members%20of%20the%20appropriate%20group.%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3EYou%20can%20refer%20to%20the%20following%20article%20for%20more%20information%20about%20how%20the%20SQL%20Computer%20Manager%20interacts%20with%20WMI.%3C%2FP%3E%0A%20%20%3CP%3E941823%20%3CA%20href%3D%22http%3A%2F%2Fsupport.microsoft.com%2Fdefault.aspx%3Fscid%3Dkb%3BEN-US%3B941823%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%20Some%20or%20all%20SQL%20Server%202005%20services%20are%20not%20listed%20in%20SQL%20Server%20Configuration%20Manager%2C%20or%20you%20receive%20a%20%22No%20SQL%20Server%202005%20components%20were%20found%22%20error%20message%20when%20you%20perform%20operations%20in%20SQL%20Server%202005%20Surface%20Area%20Configuration%20%3C%2FA%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3EThanks%3C%2FP%3E%0A%20%20%3CP%3ESuresh%20B.%20Kandoth%3C%2FP%3E%0A%20%20%3CP%3ESQL%20Server%20Escalation%20Services%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-315620%22%20slang%3D%22en-US%22%3EFirst%20published%20on%20MSDN%20on%20Jan%2004%2C%202009%20%26nbsp%3BWhen%20you%20attempt%20to%20change%20the%20Login%20Account%20for%20the%20SQL%20services%20%5BSQL%20Server%2C%20SQL%20Agent%2C%20Full%20Text%2C%20Analysis%20Services%5D%20from%20the%20SQL%20Server%20Computer%20Manager%20tool%2C%20you%20may%20encounter%20the%20following%20error%20message%3A%22WMI%20Provider%20Error%22%22Access%20is%20denied.%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-315620%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESCM%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Version history
Last update:
‎Jan 15 2019 11:15 AM
Updated by: