大网数据广告活动
数据库与应用安全

WMI Provider Error and 0x80004005 code

· 52CE 我爱测

This article provides a resolution for the problem that occurs when you change the service account that was specified during SQL Server setup to a new domain account using SQL Server Configuration Manager.

This article helps you resolve the problem that occurs when you change the service account that was specified during SQL Server setup to a new domain account using SQL Server Configuration Manager.

Original product version:   SQL Server
Original KB number:   4041637

Symptom

Assume that you have clustered instances in Microsoft SQL Server 2008 or in SQL Server 2008 R2. When you change the service account in SQL Server Configuration Manager from the account that was specified during SQL Server setup to a new domain account, you receive an error message that resembles the following in SQL Server Configuration Manager:

WMI Provider Error
Unspecified error [0x80004005]

Additionally, you can't start the SQL Server Analysis Services clustered instance. When you check the system event log, you see the following error message:

The MSSQLServerOLAPService service was unable to log on as <Domain><New account> with the currently configured password due to the following error:

Logon failure: the user has not been granted the requested logon type at this computer.

Service: MSSQLServerOLAPService
Domain and account:<Domain><New account>

This service account does not have the required user right "Log on as a service."

User Action

Assign "Log on as a service" to the service account on this computer. You can use Local Security Settings (Secpol.msc) to do this. If this computer is a node in a cluster, check that this user right is assigned to the Cluster service account on all nodes in the cluster.

If you have already assigned this user right to the service account, and the user right appears to be removed, check with your domain administrator to find out if a Group Policy object associated with this node might be removing the right.

Note: The Service shown earlier is for the default instance. For a named instance, the service name is MSOLAP$<instance name>.

Cause

This issue occurs because when you set up the clustered instance of Analysis Services, the service SID isn't granted the Log on as a service local policy user right (SeServiceLogonRight).

Resolution

To fix this issue, grant the SQL Server Analysis Services service SID the local policy user Log on as a service right.

  • For a default instance of SQL Server Analysis Services, the name of the service SID is NT SERVICE\MSSQLServerOLAPService.
  • For a named instance, the name is NT SERVICE\MSOLAP$\<instance name>.

To grant the Log on as a service right to the service SID, follow these steps:

  1. Open Local Security Policy by running the Secpol.msc command.

  2. Expand Local Policies.

  3. Click User Rights Assignment.

  4. In the right pane, right-click Log on as a service, and then click Properties.

  5. Click Add User or Group.

  6. Click the Locations button, select the server name, and then click OK.

  7. In Enter the object names to select box, type NT SERVICE\MSSQLServerOLAPService, and then click OK.

    [!NOTE] For a named instance, instead use MSOLAP$\<instance name>.

  8. Click OK.

You must repeat these steps for all nodes in the cluster.

More information

This issue only affects clustered instances of Analysis Services for SQL Server 2008 and SQL Server 2008 R2. For SQL Server 2012 and later versions of the program, you can't reproduce this issue.

Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / IT Pro troubleshooting
适用范围
See source applicability · Source date 11/09/2020
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。