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:
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.