Kerberos security error
Client-side authentication error: KerbUnknownSecurityError
Error <computer name> : Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: WinRM cannot process the request. The following error with errorcode
0x80090322 occurred while using Kerberos authentication: An unknown security error occurred. Possible causes are: -The user name or password specified are invalid. -Kerberos is used when no authentication method and no user name are specified. -Kerberos accepts
domain user names, but not local user names. -The Service Principal Name (SPN) for the remote computer name and port does not exist. -The client and remote computers are in different domains and there is no trust between the two domains. After checking for
the above issues, try the following: -Check Event Viewer for events related to authentication. -Change the authentication method; add the destination computer to the WinRM TrustedHosts configuration setting or use HTTPS transport. Note that computers in the
TrustedHosts list might not be authenticated. -For more information about WinRM configuration, run the following command: winrm help config.
Client and target server are in the same domain; the target server is added to Server Manager, but later, the target server’s domain is changed to a trusted but different domain. Try removing the target server from the Server
Manager server pool, and then adding the server again by using the Active Directory tab in the
Add Servers dialog box. If you do not want to remove the server from Server Manager, try following instructions in
Add Servers to Server Manager to add the target server to the client’s trusted hosts list.
Error
Kerberos target resolution error
Client-side authentication error: KerbResolutionError
Error <computer name>: Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: WinRM cannot process the request. The following error occurred while
using Kerberos authentication: Cannot find the computer <computer name>. Verify that the computer exists on the network and that the name provided is spelled correctly.
Client is in a domain, and the target server is in a workgroup (using the NetBIOS name of the server): A Kerberos error occurs if explicit credentials are not specified for managing the target server, because the Kerberos ticket
granting service (TGS) cannot find the workgroup server, and the Default authentication mechanism does not attempt to use
Negotiate authentication unless explicit credentials are specified for the target server. For information about how to add servers in workgroups to Server Manager, see
Add Servers to Server Manager.
Error
Error <computer name>: Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: WinRM cannot process the request. The following error occurred while
using Kerberos authentication: Cannot find the computer <computer name>. Verify that the computer exists on the network and that the name provided is spelled correctly.
Error <computer name>: Refresh failed with the following error: Call was canceled by the message filter.
Client is in Domain1 and the target server is in an untrusted Domain2. A Kerberos error occurs because the Kerberos TGS cannot find the target server. Explicit credentials must be used to manage the target server. Right-click
the target server in the Servers tile of the All Servers page, and then click
Manage As to provide explicit credentials.
Error
Error <computer name>: Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: WinRM cannot process the request. The following error occurred while
using Kerberos authentication: Cannot find the computer <computer name>. Verify that the computer exists on the network and that the name provided is spelled correctly.
Error <computer name>: Refresh failed with the following error: Call was canceled by the message filter.
Client is in a domain and the target server is in the same domain, but the domain name provided for the target server is incorrect or misspelled.
Error
Kerberos authentication error
Client-side authentication error: Kerb0x80090311Error
Error <computer name>: Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: WinRM cannot process the request. The following error with errorcode
0x80090311 occurred while using Kerberos authentication: There are currently no logon servers available to service the logon request. Possible causes are: -The user name or password specified are invalid. -Kerberos is used when no authentication method and
no user name are specified. -Kerberos accepts domain user names, but not local user names. -The Service Principal Name (SPN) for the remote computer name and port does not exist. -The client and remote computers are in different domains and there is no trust
between the two domains. After checking for the above issues, try the following: -Check the Event Viewer for events related to authentication. -Change the authentication method; add the destination computer to the WinRM TrustedHosts configuration setting or
use HTTPS transport. Note that computers in the TrustedHosts list might not be authenticated. -For more information about WinRM configuration, run the following command: winrm help config.
Client is in a domain, but the domain controller for the client computer is not accessible. Try adding the target server to the client computer’s trusted host list. For information about how to add a managed server to the trusted
host list, see
Add Servers to Server Manager.
Error
Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: WinRM cannot process the request. The following error with errorcode 0x80090311 occurred
while using Kerberos authentication: There are currently no logon servers available to service the logon request. Possible causes are: -The user name or password specified are invalid. -Kerberos is used when no authentication method and no user name are specified.
-Kerberos accepts domain user names, but not local user names. -The Service Principal Name (SPN) for the remote computer name and port does not exist. -The client and remote computers are in different domains and there is no trust between the two domains.After
checking for the above issues, try the following: -Check the Event Viewer for events related to authentication. -Change the authentication method; add the destination computer to the WinRM TrustedHosts configuration setting or use HTTPS transport.Note that
computers in the TrustedHosts list might not be authenticated. -For more information about WinRM configuration, run the following command: winrm help config.
Client is in a domain, and the target server is in the same domain (using the NetBIOS name or FQDN, and explicit but local-only administrator credentials for the target, or other non-domain credentials): A Kerberos error occurs
because the credentials are unknown on the domain. The user must add the target server to the trusted host list on the client computer to allow the Default authentication mechanism to use Negotiate authentication instead of Kerberos. For information about
how to add a managed server to the trusted host list, see
Add Servers to Server Manager.
Error
Error <computer name>: Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: WinRM cannot process the request. The following error with errorcode
0x80090311 occurred while using Kerberos authentication: There are currently no logon servers available to service the logon request. Possible causes are: -The user name or password specified are invalid. -Kerberos is used when no authentication method and
no user name are specified. -Kerberos accepts domain user names, but not local user names. -The Service Principal Name (SPN) for the remote computer name and port does not exist. -The client and remote computers are in different domains and there is no trust
between the two domains. After checking for the above issues, try the following: -Check the Event Viewer for events related to authentication. -Change the authentication method; add the destination computer to the WinRM TrustedHosts configuration setting or
use HTTPS transport. Note that computers in the TrustedHosts list might not be authenticated. -For more information about WinRM configuration, run the following command: winrm help config.
Client is in a domain and the target server is in a workgroup (using the NetBIOS name of the server): User has specified explicit credentials. An error occurs if the user has not added the server to the trusted host list of the
client, because the Default authentication mechanism will not attempt Negotiate authentication unless explicit credentials are specified. For information about how to add a workgroup server to Server Manager, see
Add Servers to Server Manager.
Error
Client-side authentication error: Kerb0x8009030eError
Error : Refresh failed with the following error (WSMAN): The metadata failed to be retrieved from the server, due to the following error: WinRM cannot process the request. The following error with errorcode 0x8009030e occurred
while using Kerberos authentication: A specified logon session does not exist. It may already have been terminated. Possible causes are: -The user name or password specified are invalid. -Kerberos is used when no authentication method and no user name are
specified. -Kerberos accepts domain user names, but not local user names. -The Service Principal Name (SPN) for the remote computer name and port does not exist. -The client and remote computers are in different domains and there is no trust between the two
domains.After checking for the above issues, try the following: -Check the Event Viewer for events related to authentication. -Change the authentication method; add the destination computer to the WinRM TrustedHosts configuration setting or use HTTPS transport.Note
that computers in the TrustedHosts list might not be authenticated. -For more information about WinRM configuration, run the following command: winrm help config.
Client is in a domain: Attempting to connect to a remote server by using implicit credentials that are the local administrator’s credentials on the client. Instead, use domain credentials that are recognized by the domain of
the target server, or right-click the server entry in the Servers tile, click
Manage As, and then specify credentials of an administrator on the target server.
Error
WinRM Default authentication error
Client-side authentication error: DefaultAuthReqsError
Error <computer IP address>: Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: The WinRM client cannot process the request. Default authentication
may be used with an IP address under the following conditions: the transport is HTTPS or the destination is in the TrustedHosts list, and explicit credentials are provided. Use winrm.cmd to configure TrustedHosts. Note that computers in the TrustedHosts list
might not be authenticated. For more information on how to set TrustedHosts run the following command: winrm help config.
Client and target server are both in the same domain. The target server was added to Server Manager by using the IP address of the server, such as by using the
Import tab of the Add Servers dialog box. An authentication error occurs because if a client is in a domain, and attempting to connect to a target server by referencing an IP address, the user must provide explicit server to
the client computer’s trusted host list. This is required for the Default authentication mechanism to use Negotiate instead of Kerberos authentication. To avoid this problem, if target servers that you want to manage are in the same domain as the client computer,
add them by using the Active Directory tab of the Add Servers dialog box.
Error
Client is in a domain and the target server is in a workgroup. The target server was added to Server Manager by using its IP address. An authentication error occurs because if a client is in a domain, and attempting to connect
to a target server by referencing an IP address, the user must provide explicit credentials and add the target server to the client computer’s trusted host list. This is required for the Default authentication mechanism to use Negotiate instead of Kerberos
authentication. For information about how to add a workgroup server to Server Manager, see
Add Servers to Server Manager.
Error
WinRM Negotiate authentication error
Client-side authentication error: NegoAuthReqsError
Error <computer name>: Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: The WinRM client cannot process the request. If the authentication
scheme is different from Kerberos, or if the client computer is not joined to a domain, then HTTPS transport must be used or the destination machine must be added to the TrustedHosts configuration setting. Use winrm.cmd to configure TrustedHosts. Note that
computers in the TrustedHosts list might not be authenticated. You can get more information about that by running the following command: winrm help config.
Client is in a workgroup, and the target server is in a workgroup (using the NetBIOS name of the server): The network can resolve the name of the server. An authentication error occurs because the target server has not been added
to the trusted host list of the client computer, which permits Negotiate authentication. For information about how to add a workgroup server to Server Manager, see
Add Servers to Server Manager.
Error
Error <computer name>: Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: The WinRM client cannot process the request. If the authentication
scheme is different from Kerberos, or if the client computer is not joined to a domain, then HTTPS transport must be used or the destination machine must be added to the TrustedHosts configuration setting. Use winrm.cmd to configure TrustedHosts. Note that
computers in the TrustedHosts list might not be authenticated. You can get more information about that by running the following command: winrm help config.
Client computer is in a workgroup, and the target server is also in a workgroup (using the IP address of the server): An authentication error occurs because the target server has not been added to the trusted host list of the
client, which permits Negotiate authentication. For information about how to add a workgroup server to Server Manager, see
Add Servers to Server Manager.
Error
Error <computer name>: Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: The WinRM client cannot process the request. If the authentication
scheme is different from Kerberos, or if the client computer is not joined to a domain, then HTTPS transport must be used or the destination machine must be added to the TrustedHosts configuration setting. Use winrm.cmd to configure TrustedHosts. Note that
computers in the TrustedHosts list might not be authenticated. You can get more information about that by running the following command: winrm help config.
Client computer is in a workgroup, and the target server is in a domain (using the NetBIOS name of the server): User’s network can resolve the name of the server. An authentication error occurs because the target server has not
been added to the trusted host list of the client computer to allow Negotiate authentication. For information about how to add a domain server to Server Manager when the client is in a workgroup, see
Add Servers to Server Manager.
Error
Error <computer name>: Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: The WinRM client cannot process the request. If the authentication
scheme is different from Kerberos, or if the client computer is not joined to a domain, then HTTPS transport must be used or the destination machine must be added to the TrustedHosts configuration setting. Use winrm.cmd to configure TrustedHosts. Note that
computers in the TrustedHosts list might not be authenticated. You can get more information about that by running the following command: winrm help config.
Client is in a workgroup and the target server is in a domain (using the IP address of the server): An authentication error occurs because the target server has not been added to the trusted host list of the client computer to
allow Negotiate authentication. For information about how to add a domain server to Server Manager when the client is in a workgroup, see
Add Servers to Server Manager.
Error
Target name resolution error
Name resolution error
Error <computer name>: Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: The WinRM client cannot process the request because the server name
cannot be resolved.
Error <computer name>: Refresh failed with the following error: The RPC server is unavailable.
Client is in a workgroup, and the target server is in a workgroup (using the NetBIOS name of the server): A name resolution error occurs if the DNS server that is used by the client cannot resolve the target server name. This
can occur when the client and target server are in two different workgroups, and each has a different DNS server. Add the target server to the client computer’s trusted host list. For information about how to add a workgroup server to Server Manager, see
Add Servers to Server Manager.
Error
Error <computer name>: Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: The WinRM client cannot process the request because the server name
cannot be resolved.
Error <computer name>: Refresh failed with the following error: The RPC server is unavailable.
Client is in a workgroup and the target server is in a domain (using the NetBIOS name of the server): A name resolution error occurs if the DNS server that is used by the client cannot resolve the target server name. Add the
target server to the client computer’s trusted host list. For information about how to add remote servers to a workgroup client that is running Server Manager, see
Add Servers to Server Manager.
Error
Name resolution error: SpecialCasedError
Error <computer name>: Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: WS-Management could not connect to the specified destination: (<computer
name>:5985).
The target server name includes an unsupported character or string, such as
. This error can occur when a cluster logical node is offline. For more information about characters that cannot be used in server names, see
Naming conventions in Active Directory for computers, domains, sites, and OUs.
Error
Error — Cannot manage the operating system of the target computer
Non-Windows target computer error
Error <computer name>: Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: The client cannot connect to the destination specified in the request.
Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following
command on the destination to analyze and configure the WinRM service: «winrm quickconfig».
Error <computer name>: Refresh failed with the following error: The RPC server is unavailable.
The target computer is not running a Windows-based operating system. You cannot use Server Manager to manage this computer.
Error
Target computer not accessible
Network connection-related errors
Configuration Refresh failed with the following error: Windows Remote Management (WinRM) cannot complete the operation. Verify that the specified computer name is valid, that the computer is accessible over the network, and that
a firewall exception for the Windows Remote Management service is enabled and allows access from this computer. By default, the WinRM firewall exception for public profiles limits access to remote computers within the same local subnet. [#1]Refresh failed
with the following error: Windows Remote Management (WinRM) cannot complete the operation. Verify that the specified computer name is valid, that the computer is accessible over the network, and that a firewall exception for the Windows Remote Management service
is enabled and allows access from this computer. By default, the WinRM firewall exception for public profiles limits access to remote computers within the same local subnet. [#1]
The network connecting the client and server is offline, or there is a problem with the target server’s connection to the network. Try verifying that Windows Firewall exceptions have been enabled on the target server for Windows
Remote Management (WinRM) inbound rules.
The
netsh trace command-line utility can help troubleshoot network connectivity problems, if you do not immediately find the cause of network connectivity failures.
Error
Error <computer name>: Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: Windows Remote Management (WinRM) cannot complete the operation. Verify
that the specified computer name is valid, that the computer is accessible over the network, and that a firewall exception for the Windows Remote Management service is enabled and allows access from this computer. By default, the WinRM firewall exception for
public profiles limits access to remote computers within the same local subnet.
Error <computer name>: Refresh failed with the following error: Call was canceled by the message filter.
The target computer is offline; either it is turned off, or not responding because of other hardware or software failures.
Error
Error <computer name>: Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: Windows Remote Management (WinRM) cannot complete the operation. Verify
that the specified computer name is valid, that the computer is accessible over the network, and that a firewall exception for the Windows Remote Management service is enabled and allows access from this computer. By default, the WinRM firewall exception for
public profiles limits access to remote computers within the same local subnet.
Error <computer name>: Refresh failed with the following error: The RPC server is unavailable.
Client computer is in a domain and the target server is in a workgroup (using the NetBIOS name of the server): User has specified explicit credentials for the target server, and added the target server to the trusted host list
of the client. However, a subnet timeout error occurs if the user has not changed the default subnet restrictions for computers in workgroups. See step 2 of “To add remote workgroup servers to Server Manager” in
Add Servers to Server Manager.
Error
Error <computer IP address>: Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: Windows Remote Management (WinRM) cannot complete the operation.
Verify that the specified computer name is valid, that the computer is accessible over the network, and that a firewall exception for the Windows Remote Management service is enabled and allows access from this computer. By default, the WinRM firewall exception
for public profiles limits access to remote computers within the same local subnet.
Error <computer IP address>: Refresh failed with the following error: The RPC server is unavailable.
Client is in a domain, and the target server is in a workgroup (using the IP address of the server): User has specified explicit credentials for the target server, and added the target server to the trusted host list of the client.
However, a subnet timeout error occurs if the user has not changed the default subnet restrictions for computers in workgroups. See step 2 of “To add remote workgroup servers to Server Manager” in
Add Servers to Server Manager.
Error
Error <computer name>: Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: Windows Remote Management (WinRM) cannot complete the operation. Verify
that the specified computer name is valid, that the computer is accessible over the network, and that a firewall exception for the Windows Remote Management service is enabled and allows access from this computer. By default, the WinRM firewall exception for
public profiles limits access to remote computers within the same local subnet.
Error <computer name>: Refresh failed with the following error: The RPC server is unavailable.
The client is in a workgroup, and the target server is in a workgroup (using the NetBIOS name of the server): The user’s network can resolve the name of the server, and the user has added the target server to the trusted host
list of the client. However, a subnet timeout error occurs if the user has not changed the default subnet restrictions for computers in workgroups. See step 2 of “To add remote workgroup servers to Server Manager” in
Add Servers to Server Manager.
Error
Error <computer IP address>: Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: Windows Remote Management (WinRM) cannot complete the operation.
Verify that the specified computer name is valid, that the computer is accessible over the network, and that a firewall exception for the Windows Remote Management service is enabled and allows access from this computer. By default, the WinRM firewall exception
for public profiles limits access to remote computers within the same local subnet.
Error <computer IP address>: Refresh failed with the following error: The RPC server is unavailable.
The client is in a workgroup, and the target server is in a workgroup (using the IP address of the target server): The user has added the server to the trusted host list of the client. However, a subnet timeout error occurs if
the user has not changed the default subnet restrictions for computers in workgroups. See step 2 of “To add remote workgroup servers to Server Manager” in
Add Servers to Server Manager.
Error
Error <computer name>: Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: Windows Remote Management (WinRM) cannot complete the operation. Verify
that the specified computer name is valid, that the computer is accessible over the network, and that a firewall exception for the Windows Remote Management service is enabled and allows access from this computer. By default, the WinRM firewall exception for
public profiles limits access to remote computers within the same local subnet.
Error <computer name>: Refresh failed with the following error: Call was canceled by the message filter.
WinRM 3.0, WinRM 2.0, and DCOM are unavailable or not enabled on the target. On a server that is running Windows Server 2012, the user might have disabled both WinRM 3.0 or DCOM. On a server that is running an older Windows Server
operating system, WinRM 2.0 and DCOM are not enabled by default, while WinRM 3.0 is not available. Follow instructions in
Managing Downlevel Windows-based Servers from Server Manager in Windows Server 2012 to resolve this error.
Error
The metadata failed to be retrieved from the server, due to the following error: WS-Management cannot process the request. The operation failed because of an HTTP error. The HTTP error (50) is: The request is not supported.
User is attempting to connect to the target server by using an IPv4 address, but on the client computer, only IPv6, not IPv4, is enabled. Either connect to the target server by using its IPv6 address, or change settings on the
client computer network adapters to support IPv4 addresses. These settings are found in
Control PanelNetwork and Sharing CenterChange Adapter Settings. Right-click the network connection, click
Properties, select Internet Protocol Version 4, and save your changes.
Error
Online — Verify WinRM 3.0 service is installed, running, and required firewall ports are open
Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: Windows Remote Management (WinRM) cannot complete the operation. Verify that the specified
computer name is valid, that the computer is accessible over the network, and that a firewall exception for the Windows Remote Management service is enabled and allows access from this computer. By default, the WinRM firewall exception for public profiles
limits access to remote computers within the same local subnet.
WinRM 2.0 and 3.0 are either not available or not enabled, but DCOM is enabled on the target server.
Note:
DCOM is enabled by default for domain-joined servers that are running Windows Server 2012 and Windows Server 2008 R2, but not for Windows Server 2008.
This error can occur on a server that is running an older Windows Server operating system (Windows Server 2008 R2 or Windows Server 2008) where the
Windows Management Framework 3.0 download package has not been installed (so WinRM 3.0 is not available) and WinRM 2.0 is not enabled but DCOM is enabled. It can also occur on servers
that are running Windows Server 2012 and older Windows Server operating systems where Windows Management Framework 3.0 is installed and DCOM is still enabled, but the user has disabled WinRM 3.0 (either stopped the service or closed required firewall ports).
Follow instructions in
Managing Downlevel Windows-based Servers from Server Manager in Windows Server 2012 to resolve this error.
Error
Network connection related errors: WinRM 2.0 and DCOM
Error <computer name>: Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: The WS-Management service cannot process the request. The resource
URI (<URI>) was not found in the WS-Management catalog. The catalog contains the metadata that describes resources, or logical endpoints.
WinRM 3.0 is not available or enabled, but WinRM 2.0 and DCOM are both enabled on the target server. This can occur on servers that are running older Windows Server operating systems (Windows Server 2008 R2 or Windows Server
2008 where the
Windows Management Framework 3.0 download package has not been installed (so WinRM 3.0 is not available), but WinRM 2.0 and DCOM are both enabled. Follow instructions in
Managing Downlevel Windows-based Servers from Server Manager in Windows Server 2012 to resolve this error.
Error
Network connection related errors: WinRM 2.0
Error <computer name>: Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: The WS-Management service cannot process the request. The resource
URI (http://schemas.dmtf.org/wbem/cim-xml/2/cim-schema/2/*) was not found in the WS-Management catalog. The catalog contains the metadata that describes resources, or logical endpoints.
Error <computer name>: Refresh failed with the following error: Call was canceled by the message filter.
WinRM 3.0 and DCOM are either not available or not enabled, but WinRM 2.0 is enabled on the target server.
Note:
DCOM is enabled by default for domain-joined servers that are running Windows Server 2012 and Windows Server 2008 R2, but not for Windows Server 2008.
A user might have enabled WinRM 2.0, but not DCOM, on a target server that is running an older Windows Server operating system, and not yet installed the
Windows Management Framework 3.0 download package to get WinRM 3.0. Follow instructions in
Managing Downlevel Windows-based Servers from Server Manager in Windows Server 2012 to resolve this error.
Error
Online — Access denied
Access denied error
Error <computer IP address>: Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: Access is denied.
Client is in a domain and the target server is in a workgroup (using the IP address of the server): The user has provided explicit credentials and added the server to the trusted host list of the client. However, an “access denied”
error occurs if the user specifies credentials for the target server other than the built-in Administrator account, and if the account token filter policy is not configured. See “To add remote workgroup servers to Server Manager” in
Add Servers to Server Manager.
Error
Error <computer name>: Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: Access is denied.
Client is in a workgroup and the target server is in a workgroup (using the NetBIOS name of the server): The user’s network can resolve the name of the server, the user has added the target server to the trusted hosts list on
the client, and the user has already removed subnet restrictions on the server. However, an “access denied” error can occur if the user is managing the target server by using the same credentials that were provided to log on to the client computer, but that
are not valid or recognized on the target server.
Error
Error <computer name>: Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: Access is denied.
Client is in a workgroup and the target server is in a workgroup (using the IP address of the server): The user has added the server to the trusted hosts list of the client, and removed subnet restrictions on the server. However,
an “access denied” error can occur if the user is managing the target server by using the same credentials that were provided to log on to the client computer, but that are not valid or recognized on the target server.
Error
Error <computer name>: Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: Access is denied.
Client is in a workgroup and the target server is in a domain (using the NetBIOS name of the server): The user’s network can resolve the name of the server, and the user has added the server to the trusted hosts list of the client.
However, an “access denied” error can occur if the user is managing the target server by using the same credentials that were provided to log on to the client computer, but that are not valid or recognized on the target server.
Error
Error <computer name>: Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: Access is denied.
The client is in a workgroup, and the target server is in a domain (using the IP address of the server): The user has added the server to the trusted hosts list on the client. However, an “access denied” error can occur if the
user is managing the target server by using the same credentials that were provided to log on to the client computer, but that are not valid or recognized on the target server.
Error
Error <computer name>: Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: Access is denied.
The user is attempting to manage the remote server with a credential that has only standard user (not a member of the Administrators group) access rights on the target server, and the user has not enabled standard user remote
management of the target server. By default, an account with standard user access rights is not a part of the WinRM remote WMI user’s group, and can perform limited management tasks on a remote server in Server Manager. To allow standard users more management
access rights on a target server, run the Enable-ServerManagerStandardUserRemoting cmdlet on the target server, in a Windows PowerShell session that has been opened with elevated user rights (Run as Administrator). For more information about how
to use this cmdlet (and disable standard user management access when it is no longer needed), see the cmdlet Help topic for
Enable-ServerManagerStandardUserRemoting.
Error
Error <computer name>: Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: Access is denied.
An incorrect or misspelled user name was provided to log on to the target server.
Error
Error <computer name>: Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: Access is denied.
The correct user name for the account used to manage the target server was provided, but the password was incorrect.
Error
MessageID: 1326. Message: The metadata failed to be retrieved from the server, due to the following error: The user name or password is incorrect.
The correct user name for the account used to manage the target server was provided, but the password was incorrect.
Error
Error <computer name>: Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: Access is denied.
Client is in a domain, and the server is in a workgroup (using the NetBIOS name of the server): The user has specified explicit credentials, added the target server to the trusted hosts list of the client, and removed the subnet
restrictions on the target server. However, an access denied error occurs if the user specified an account to manage the target server other than the built-in Administrator account, and the local account token filter policy is not configured correctly. See
“To add remote workgroup servers to Server Manager” in
Add Servers to Server Manager to resolve this issue.
Error
Error <computer name>: Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: Access is denied.
Both the client and the target server are in workgroups (using the NetBIOS name of the server): The user’s network can resolve the name of the server, the user has added the server to the trusted hosts list of the client, the
user has removed the subnet restrictions on the server, and specified explicit credentials that are valid on the target server, but is not using the built-in Administrator account for the target server. An access denied error occurs because the specified account
is not the built-in Administrator account, and the local account token filter policy is not set. See “To add remote workgroup servers to Server Manager” in
Add Servers to Server Manager to resolve this issue.
Error
Error <computer name>: Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: Access is denied.
Both the client and target server are in workgroups (using the IP address of the server): User has added the server to the trusted host list of the client, and removed the subnet restrictions on the server. The user attempts
to manage the target server by using the credentials with which they logged on to the client computer. An access denied error occurs because the specified account is not the built-in Administrator account on the target server, and the local account token filter
policy is not set. See “To add remote workgroup servers to Server Manager” in
Add Servers to Server Manager to resolve this issue.
Error
Online – Cannot manage a client-based operating system
Server Manager WMI providers are not available on the target computer
Message: The metadata failed to be retrieved from the server, due to the following error: The WS-Management service cannot process the request. The CIM namespace root/microsoft/windows/servermanager is not valid.
This is typical of Windows 8, on which Server Manager providers are not available and DCOM is not enabled by default. You cannot manage this computer by using Server Manager.
Error
Inventory discovery-based errors
None
Server Manager inventory collection finds that the target computer is running a Windows client-based operating system. You cannot manage this computer by using Server Manager, so you must contact them. h
Error
Online — Server Manager WMI providers not loading on the target server
Server Manager WMI provider cannot load error
Error <computer name>: Configuration refresh failed with the following error: HRESULT = 0x80041013
The Server Manager provider is available, but cannot load. This error can occur when WMI namespace access rights do not grant access to the user, and is most commonly seen when standard users (those who are not members of the
Administrators group on the target server) are managing a server by using Server Manager. To grant WMI namespace access rights to standard users, administrators should run the
Enable-ServerManagerStandardUserRemoting cmdlet on the target server. For more information about how to use this cmdlet (and disable standard user management access when it is no longer needed), see the cmdlet Help topic for
Enable-ServerManagerStandardUserRemoting.
Error
Online – Cannot manage operating systems older than Windows Server 2003
Inventory discovery-based errors
None
Server Manager inventory collection finds that the target computer is running a release of Windows Server that is older than Windows Server 2003. You cannot manage this computer by using Server Manager.
Error
Online – Limited data – Windows Server 2003
Inventory discovery-based errors
None
Server Manager inventory collection finds that the target computer is running Windows Server 2003.
Informational
Online – Restart pending
Inventory discovery-based errors
None
Server Manager inventory collection finds that the target server requires a restart. Restart the target server.
Informational
Online – Windows PowerShell not installed
Inventory discovery-based errors
None
Server Manager inventory collection finds that Windows PowerShell is not installed on the target server. On a target server that is running Windows Server 2012, run the following cmdlet on the computer that is running Server
Manager to install Windows PowerShell: Install-WindowsFeature -Name PowerShell –ComputerName <target server name>. On Windows Server 2008 R2 and Windows Server 2008, install the
Windows Management Framework 3.0 download package to get Windows PowerShell 3.0. Install prerequisites for Windows Management Framework 3.0 by following instructions in
Managing Downlevel Windows-based Servers from Server Manager in Windows Server 2012 to resolve this error.
Informational
Online – Performance counters not started
Inventory discovery-based errors
None
Server Manager inventory collection finds that performance counter data collection is turned off on the target server.
Informational
Online — Cannot get event data
Data retrieval errors
Any errors from the Server Manager provider that are related to event data retrieval.
This error can also occur if specific roles and features have been installed, but not yet configured. The following underlying error messages are examples of known cases where a role, role service, or feature requires post-installation
configuration to clear the error.
- Events from ‘Virtualization.Events.xml’ could not be enumerated. (This error is cleared after required post-installation configuration for Hyper-V is completed.)
- Events from ‘PrintServices.Events.xml’ could not be enumerated. (This error is cleared after required post-installation configuration for Print and Document Services is completed.)
- Events from ‘ADAM.Events.xml’ could not be enumerated. (This error might be cleared after required post-installation configuration for Active Directory Lightweight Directory Services is completed.)
The following underlying error message can occur for Active Directory Federation Services when the only role services that are installed are web agents. Configuring the installed role services does not resolve the error.
- Events from ‘IdentityServer.Events.xml’ could not be enumerated.
Server Manager cannot get event data from the target server. The user might not have access rights to the target server event log, or event log files might not contain valid data.
For some roles and features (Hyper-V, Print and Document Services, AD LDS), this error can occur after installation, but before required post-installation configuration has been completed. The error is resolved after post-installation
configuration is complete. For AD FS, this error can occur if web agents are the only role services installed, but there is currently no known resolution for this case of the error.
Error
Online — Cannot get service data
Any errors from the Server Manager provider that are related to service data retrieval
Server Manager cannot get services data from the target server. The user might not have access rights to service data on the target server, or service data files might not contain valid data. To grant service data access rights
to standard (non-Administrator) users, administrators should run the Enable-ServerManagerStandardUserRemoting cmdlet on the target server. For more information about how to use this cmdlet (and disable standard user management access when it is
no longer needed), see the cmdlet Help topic for
Enable-ServerManagerStandardUserRemoting.
Error
Online — Cannot get BPA results
Any errors from the Server Manager provider related to BPA result retrieval (excluding Windows PowerShell not enabled errors which are covered by other manageability status messages)
Server Manager cannot get Best Practices Analyzer result data from the target server. The user might not have access rights to BPA data on the target server, or BPA result data might not be readable. Standard users cannot get
access to BPA data, even after an administrator runs the Enable-ServerManagerStandardUserRemoting cmdlet.
Error
Online — Cannot get performance counter data
Any errors from the Server Manager provider related to performance data retrieval (excluding performance counters off errors, which are covered by other manageability status messages)
Server Manager cannot get performance counter data from the target server. The user might not have access rights to performance data on the target server, or the data might not be readable. To grant performance data access rights
to standard (non-Administrator) users, administrators should run the Enable-ServerManagerStandardUserRemoting cmdlet on the target server. For more information about how to use this cmdlet (and disable standard user management access when it is
no longer needed), see the cmdlet Help topic for
Enable-ServerManagerStandardUserRemoting.
Error
Online — Cannot get role and feature data
Any errors from the Server Manager provider related to role and feature data retrieval
Server Manager cannot get role and feature inventory data from the target server. The user might not have access rights to role and feature data on the target server, or the data might not be readable. To grant role and feature
inventory data access rights to standard (non-Administrator) users, administrators should run the
Enable-ServerManagerStandardUserRemoting cmdlet on the target server. For more information about how to use this cmdlet (and disable standard user management access when it is no longer needed), see the cmdlet Help topic for
Enable-ServerManagerStandardUserRemoting.
Error
Online — Data retrieval failures occurred
(If two or more types of data cannot be retrieved)
- The WS-Management service cannot process the request. WS-Management cannot identify the enumeration context ID in the SOAP packet. The packet may not be valid, or the operation may have timed out.
- The WinRM client cannot process the request because the metadata failed to be retrieved from the server.
- Non terminating error during inventory method; for example, an access error to cluster resource data
This error can also occur if specific roles and features have been installed, but not yet configured. The following underlying error messages are examples of known cases where a role, role service, or feature requires post-installation
configuration to clear the error.
- Events from ‘Virtualization.Events.xml’ could not be enumerated. (This error is cleared after required post-installation configuration for Hyper-V is completed.)
- Events from ‘PrintServices.Events.xml’ could not be enumerated. (This error is cleared after required post-installation configuration for Print and Document Services is completed.)
- Events from ‘ADAM.Events.xml’ could not be enumerated. (This error might be cleared after required post-installation configuration for Active Directory Lightweight Directory Services is completed.)
The following underlying error message can occur for Active Directory Federation Services when the only role services that are installed are web agents. Configuring the installed role services does not resolve the error.
- Events from ‘IdentityServer.Events.xml’ could not be enumerated.
Server Manager cannot get a combination of data types: events, BPA results, performance counters, or services. This can be caused by insufficient user access rights, data that is not valid, or WinRM time-outs.
To grant event, performance, role and feature inventory, and service data access rights to standard (non-Administrator) users, administrators should run the
Enable-ServerManagerStandardUserRemoting cmdlet on the target server. For more information about how to use this cmdlet (and disable standard user management access when it is no longer needed), see the cmdlet Help topic for
Enable-ServerManagerStandardUserRemoting. The
Enable-ServerManagerStandardUserRemoting cmdlet does not provide standard users access to BPA result data.
For some roles and features (Hyper-V™, Print and Document Services, AD LDS), this error can occur after installation, but before required post-installation configuration has been completed. The error is resolved after post-installation
configuration is complete. For AD FS, this error can occur if web agents are the only role services installed, but there is currently no known resolution for this case of the error.
Error
An unknown error occurred
Unknown errors
None
If the error persists,
contact Customer Support Services.
Error
Иногда нужно добавить IIS, сайт и пул приложений в failover кластер Майкрософт — например, если на одном кластере у нас и сервер БД в AlwaysOn, и службы сервера приложений (в отдельной группе/роли), и веб-сайт. Это не самая лучшая практика (и вообще это всё дела давно минувших дней), но вполне допустимая, и есть готовый скрипт Clusweb7.vbs для кластеризации: https://docs.microsoft.com/ru-ru/troubleshoot/iis/configure-w3svc-wsfc Этот скрипт будет проверять и поддерживать запущенным IIS и указанные в теле сайт и пул приложений, а также останавливать сайт при остановке узла и смене активного узла кластера. Однако иногда нужно останавливать не только сайт, но и пул приложений, особенно если исходно приложение и пул были написаны без учёта возможности кластеризации. Немного подправил скрипт clusweb7.vbs, чтобы он останавливал пул приложений, там несложно было. Изменения относительно исходного выделены. Для поиска: clusweb7.vbs stop iis application pool.
‘<begin script sample>
‘This script provides high availability for IIS websites
‘By default, it monitors the «Default Web Site» and «DefaultAppPool»
‘To monitor another website, change the SITE_NAME below
‘To monitor another application pool, change the APP_POOL_NAME below
‘More thorough and application-specific health monitoring logic can be added to the script if needed
Option Explicit
DIM SITE_NAME
DIM APP_POOL_NAME
Dim START_WEB_SITE
Dim START_APP_POOL
Dim SITES_SECTION_NAME
Dim APPLICATION_POOLS_SECTION_NAME
Dim CONFIG_APPHOST_ROOT
Dim STOP_WEB_SITE
Dim STOP_APP_POOL
‘Note:
‘Replace this with the site and application pool you want to configure high availability for
‘Make sure that the same website and application pool in the script exist on all cluster nodes. Note that the names are case-sensitive.
SITE_NAME = «Default Web Site»
APP_POOL_NAME = «DefaultAppPool»
START_WEB_SITE = 0
START_APP_POOL = 0
STOP_WEB_SITE = 1
STOP_APP_POOL = 1
SITES_SECTION_NAME = «system.applicationHost/sites»
APPLICATION_POOLS_SECTION_NAME = «system.applicationHost/applicationP
CONFIG_APPHOST_ROOT = «MACHINE/WEBROOT/APPHOST»
‘Helper script functions
‘Find the index of the website on this node
Function FindSiteIndex(collection, siteName)
Dim i
FindSiteIndex = -1
For i = 0 To (CInt(collection.Count) — 1)
If collection.Item(i).GetPropertyByName(«na
FindSiteIndex = i
Exit For
End If
Next
End Function
‘Find the index of the application pool on this node
Function FindAppPoolIndex(collection, appPoolName)
Dim i
FindAppPoolIndex = -1
For i = 0 To (CInt(collection.Count) — 1)
If collection.Item(i).GetPropertyByName(«na
FindAppPoolIndex = i
Exit For
End If
Next
End Function
‘Get the state of the website
Function GetWebSiteState(adminManager, siteName)
Dim sitesSection, sitesSectionCollection, siteSection, index, siteMethods, startMethod, executeMethod
Set sitesSection = adminManager.GetAdminSection(SITES_SECTI
Set sitesSectionCollection = sitesSection.Collection
index = FindSiteIndex(sitesSectionCollection, siteName)
If index = -1 Then
GetWebSiteState = -1
End If
Set siteSection = sitesSectionCollection(index)
GetWebSiteState = siteSection.GetPropertyByName(«state»).V
End Function
‘Get the state of the ApplicationPool
Function GetAppPoolState(adminManager, appPool)
Dim configSection, index, appPoolState
set configSection = adminManager.GetAdminSection(APPLICATION
index = FindAppPoolIndex(configSection.Collectio
If index = -1 Then
GetAppPoolState = -1
End If
GetAppPoolState = configSection.Collection.Item(index).Get
End Function
‘Start the w3svc service on this node
Function StartW3SVC()
Dim objWmiProvider
Dim objService
Dim strServiceState
Dim response
‘Check to see if the service is running
set objWmiProvider = GetObject(«winmgmts:/root/cimv2»)
set objService = objWmiProvider.get(«win32_service=’w3svc’
strServiceState = objService.state
If ucase(strServiceState) = «RUNNING» Then
StartW3SVC = True
Else
‘If the service is not running, try to start it
response = objService.StartService()
‘response = 0 or 10 indicates that the request to start was accepted
If ( response <> 0 ) and ( response <> 10 ) Then
StartW3SVC = False
Else
StartW3SVC = True
End If
End If
End Function
‘Start the application pool for the website
Function StartAppPool()
Dim ahwriter, appPoolsSection, appPoolsCollection, index, appPool, appPoolMethods, startMethod, callStartMethod
Set ahwriter = CreateObject(«Microsoft.ApplicationHost.W
Set appPoolsSection = ahwriter.GetAdminSection(APPLICATION_POO
Set appPoolsCollection = appPoolsSection.Collection
index = FindAppPoolIndex(appPoolsCollection, APP_POOL_NAME)
Set appPool = appPoolsCollection.Item(index)
‘See if it is already started
If appPool.GetPropertyByName(«state»).Value = 1 Then
StartAppPool = True
Exit Function
End If
‘Try to start the application pool
Set appPoolMethods = appPool.Methods
Set startMethod = appPoolMethods.Item(START_APP_POOL)
Set callStartMethod = startMethod.CreateInstance()
callStartMethod.Execute()
‘If started return true, otherwise return false
If appPool.GetPropertyByName(«state»).Value = 1 Then
StartAppPool = True
Else
StartAppPool = False
End If
End Function
‘Start the website
Function StartWebSite()
Dim ahwriter, sitesSection, sitesSectionCollection, siteSection, index, siteMethods, startMethod, executeMethod
Set ahwriter = CreateObject(«Microsoft.ApplicationHost.W
Set sitesSection = ahwriter.GetAdminSection(SITES_SECTION_N
Set sitesSectionCollection = sitesSection.Collection
index = FindSiteIndex(sitesSectionCollection, SITE_NAME)
Set siteSection = sitesSectionCollection(index)
if siteSection.GetPropertyByName(«state»).V
‘Site is already started
StartWebSite = True
Exit Function
End If
‘Try to start site
Set siteMethods = siteSection.Methods
Set startMethod = siteMethods.Item(START_WEB_SITE)
Set executeMethod = startMethod.CreateInstance()
executeMethod.Execute()
‘Check to see if the site started, if not return false
If siteSection.GetPropertyByName(«state»).V
StartWebSite = True
Else
StartWebSite = False
End If
End Function
‘Stop the application pool for the website
Function StopAppPool()
Dim ahwriter, appPoolsSection, appPoolsCollection, index, appPool, appPoolMethods, startMethod, callStartMethod
Set ahwriter = CreateObject(«Microsoft.ApplicationHost.W
Set appPoolsSection = ahwriter.GetAdminSection(APPLICATION_POO
Set appPoolsCollection = appPoolsSection.Collection
index = FindAppPoolIndex(appPoolsCollection, APP_POOL_NAME)
Set appPool = appPoolsCollection.Item(index)
‘Stop the application pool
Set appPoolMethods = appPool.Methods
Set startMethod = appPoolMethods.Item(STOP_APP_POOL)
Set callStartMethod = startMethod.CreateInstance()
callStartMethod.Execute()
End Function
‘Stop the website
Function StopWebSite()
Dim ahwriter, sitesSection, sitesSectionCollection, siteSection, index, siteMethods, startMethod, executeMethod, autoStartProperty
Set ahwriter = CreateObject(«Microsoft.ApplicationHost.W
Set sitesSection = ahwriter.GetAdminSection(SITES_SECTION_N
Set sitesSectionCollection = sitesSection.Collection
index = FindSiteIndex(sitesSectionCollection, SITE_NAME)
Set siteSection = sitesSectionCollection(index)
‘Stop the site
Set siteMethods = siteSection.Methods
Set startMethod = siteMethods.Item(STOP_WEB_SITE)
Set executeMethod = startMethod.CreateInstance()
executeMethod.Execute()
End Function
‘Cluster resource entry points. More details here:
‘Cluster resource Online entry point
‘Make sure the website and the application pool are started
Function Online( )
Dim bOnline
‘Make sure w3svc is started
bOnline = StartW3SVC()
If bOnline <> True Then
Resource.LogInformation «The resource failed to come online because w3svc could not be started.»
Online = False
Exit Function
End If
‘Make sure the application pool is started
bOnline = StartAppPool()
If bOnline <> True Then
Resource.LogInformation «The resource failed to come online because the application pool could not be started.»
Online = False
Exit Function
End If
‘Make sure the website is started
bOnline = StartWebSite()
If bOnline <> True Then
Resource.LogInformation «The resource failed to come online because the web site could not be started.»
Online = False
Exit Function
End If
Online = true
End Function
‘Cluster resource offline entry point
‘Stop the website
Function Offline( )
StopWebSite()
StopAppPool()
Offline = true
End Function
‘Cluster resource LooksAlive entry point
‘Check for the health of the website and the application pool
Function LooksAlive( )
Dim adminManager, appPoolState, configSection, i, appPoolName, appPool, index
i = 0
Set adminManager = CreateObject(«Microsoft.ApplicationHost.A
appPoolState = -1
‘Get the state of the website
if GetWebSiteState(adminManager, SITE_NAME) <> 1 Then
Resource.LogInformation «The resource failed because the » & SITE_NAME & » web site is not started.»
LooksAlive = false
Exit Function
End If
‘Get the state of the Application Pool
if GetAppPoolState(adminManager, APP_POOL_NAME) <> 1 Then
Resource.LogInformation «The resource failed because Application Pool » & APP_POOL_NAME & » is not started.»
LooksAlive = false
Exit Function
end if
‘ Web site and Application Pool state are valid return true
LooksAlive = true
End Function
‘Cluster resource IsAlive entry point
‘Do the same health checks as LooksAlive
‘If a more thorough than what we do in LooksAlive is required, this should be performed here
Function IsAlive()
IsAlive = LooksAlive
End Function
‘Cluster resource Open entry point
Function Open()
Open = true
End Function
‘Cluster resource Close entry point
Function Close()
Close = true
End Function
‘Cluster resource Terminate entry point
Function Terminate()
Terminate = true
End Function
‘<end script sample>
- WMI
- ROOT\Microsoft\Windows\ServerManager
- CIM_Error
Class
| Childs (2)
| Methods | Properties (15)
| Qualifiers (6)
| Instances | Namespaces (142)
Samples: VB Script
| C#
| VB.Net
| Search on:Microsoft
Description
CIM_Error is a specialized class that contains information about the severity, cause, recommended actions and other data related to the failure of a CIM Operation. Instances of this type MAY be included as part of the response to a CIM Operation.
CIM_Error — child subclasses in ROOT\Microsoft\Windows\ServerManager
Number of classes:2
CIM_Error properties
CIM_Error has 15 properties (15 Local)
| Name | Origin | CIMType |
|---|---|---|
| CIMStatusCode | CIM_Error | 19 [uint32] |
| CIMStatusCodeDescription | CIM_Error | 8 [string] |
| ErrorSource | CIM_Error | 8 [string] |
| ErrorSourceFormat | CIM_Error | 18 [uint16] |
| ErrorType | CIM_Error | 18 [uint16] |
| Message | CIM_Error | 8 [string] |
| MessageArguments | CIM_Error | 8 [string] |
| MessageID | CIM_Error | 8 [string] |
| OtherErrorSourceFormat | CIM_Error | 8 [string] |
| OtherErrorType | CIM_Error | 8 [string] |
| OwningEntity | CIM_Error | 8 [string] |
| PerceivedSeverity | CIM_Error | 18 [uint16] |
| ProbableCause | CIM_Error | 18 [uint16] |
| ProbableCauseDescription | CIM_Error | 8 [string] |
| RecommendedActions | CIM_Error | 8 [string] |
Detailed description of CIM_Error properties
Local properties (15) of CIM_Error class
| ▲ CIMStatusCode property | |
|---|---|
| CIMTYPE | ‘uint32’ |
| Description | ‘The CIM status code that characterizes this instance. This property defines the status codes that MAY be return by a conforming CIM Server or Listener. Note that not all status codes are valid for each operation. The specification for each operation SHOULD define the status codes that may be returned by that operation. The following values for CIM status code are defined: 1 — CIM_ERR_FAILED. A general error occurred that is not covered by a more specific error code. 2 — CIM_ERR_ACCESS_DENIED. Access to a CIM resource was not available to the client. 3 — CIM_ERR_INVALID_NAMESPACE. The target namespace does not exist. 4 — CIM_ERR_INVALID_PARAMETER. One or more parameter values passed to the method were invalid. 5 — CIM_ERR_INVALID_CLASS. The specified Class does not exist. 6 — CIM_ERR_NOT_FOUND. The requested object could not be found. 7 — CIM_ERR_NOT_SUPPORTED. The requested operation is not supported. 8 — CIM_ERR_CLASS_HAS_CHILDREN. Operation cannot be carried out on this class since it has instances. 9 — CIM_ERR_CLASS_HAS_INSTANCES. Operation cannot be carried out on this class since it has instances. 10 — CIM_ERR_INVALID_SUPERCLASS. Operation cannot be carried out since the specified superclass does not exist. 11 — CIM_ERR_ALREADY_EXISTS. Operation cannot be carried out because an object already exists. 12 — CIM_ERR_NO_SUCH_PROPERTY. The specified Property does not exist. 13 — CIM_ERR_TYPE_MISMATCH. The value supplied is incompatible with the type. 14 — CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTED. The query language is not recognized or supported. 15 — CIM_ERR_INVALID_QUERY. The query is not valid for the specified query language. 16 — CIM_ERR_METHOD_NOT_AVAILABLE. The extrinsic Method could not be executed. 17 — CIM_ERR_METHOD_NOT_FOUND. The specified extrinsic Method does not exist. 18 — CIM_ERR_UNEXPECTED_RESPONSE. The returned response to the asynchronous operation was not expected. 19 — CIM_ERR_INVALID_RESPONSE_DESTINATION. The specified destination for the asynchronous response is not valid. 20 — CIM_ERR_NAMESPACE_NOT_EMPTY. The specified Namespace is not empty. 21 — CIM_ERR_INVALID_ENUMERATION_CONTEXT. The enumeration context supplied is not valid. 22 — CIM_ERR_INVALID_OPERATION_TIMEOUT. The specified Namespace is not empty. 23 — CIM_ERR_PULL_HAS_BEEN_ABANDONED. The specified Namespace is not empty. 24 — CIM_ERR_PULL_CANNOT_BE_ABANDONED. The attempt to abandon a pull operation has failed. 25 — CIM_ERR_FILTERED_ENUMERATION_NOT_SUPPORTED. Filtered Enumeratrions are not supported. 26 — CIM_ERR_CONTINUATION_ON_ERROR_NOT_SUPPORTED. Continue on error is not supported. 27 — CIM_ERR_SERVER_LIMITS_EXCEEDED. The WBEM Server limits have been exceeded (e.g. memory, connections, …). 28 — CIM_ERR_SERVER_IS_SHUTTING_DOWN. The WBEM Server is shutting down. 29 — CIM_ERR_QUERY_FEATURE_NOT_SUPPORTED. The specified Query Feature is not supported.’ |
| ModelCorrespondence | [‘CIM_Error.CIMStatusCodeDescription’] |
| ValueMap | [‘1’, ‘2’, ‘3’, ‘4’, ‘5’, ‘6’, ‘7’, ‘8’, ‘9’, ’10’, ’11’, ’12’, ’13’, ’14’, ’15’, ’16’, ’17’, ’18’, ’19’, ’20’, ’21’, ’22’, ’23’, ’24’, ’25’, ’26’, ’27’, ’28’, ’29’, ‘..’] |
| Values | [‘CIM_ERR_FAILED’, ‘CIM_ERR_ACCESS_DENIED’, ‘CIM_ERR_INVALID_NAMESPACE’, ‘CIM_ERR_INVALID_PARAMETER’, ‘CIM_ERR_INVALID_CLASS’, ‘CIM_ERR_NOT_FOUND’, ‘CIM_ERR_NOT_SUPPORTED’, ‘CIM_ERR_CLASS_HAS_CHILDREN’, ‘CIM_ERR_CLASS_HAS_INSTANCES’, ‘CIM_ERR_INVALID_SUPERCLASS’, ‘CIM_ERR_ALREADY_EXISTS’, ‘CIM_ERR_NO_SUCH_PROPERTY’, ‘CIM_ERR_TYPE_MISMATCH’, ‘CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTED’, ‘CIM_ERR_INVALID_QUERY’, ‘CIM_ERR_METHOD_NOT_AVAILABLE’, ‘CIM_ERR_METHOD_NOT_FOUND’, ‘CIM_ERR_UNEXPECTED_RESPONSE’, ‘CIM_ERR_INVALID_RESPONSE_DESTINATION’, ‘CIM_ERR_NAMESPACE_NOT_EMPTY’, ‘CIM_ERR_INVALID_ENUMERATION_CONTEXT’, ‘CIM_ERR_INVALID_OPERATION_TIMEOUT’, ‘CIM_ERR_PULL_HAS_BEEN_ABANDONED’, ‘CIM_ERR_PULL_CANNOT_BE_ABANDONED’, ‘CIM_ERR_FILTERED_ENUMERATION_NOT_SUPPORTED’, ‘CIM_ERR_CONTINUATION_ON_ERROR_NOT_SUPPORTED’, ‘CIM_ERR_SERVER_LIMITS_EXCEEDED’, ‘CIM_ERR_SERVER_IS_SHUTTING_DOWN’, ‘CIM_ERR_QUERY_FEATURE_NOT_SUPPORTED’, ‘DMTF Reserved’] |
| CIMStatusCode property is in 4 classes of ROOT\Microsoft\Windows\ServerManager and in 142 namespaces |
| ▲ CIMStatusCodeDescription property | |
|---|---|
| CIMTYPE | ‘string’ |
| Description | ‘A free-form string containing a human-readable description of CIMStatusCode. This description MAY extend, but MUST be consistent with, the definition of CIMStatusCode.’ |
| ModelCorrespondence | [‘CIM_Error.CIMStatusCode’] |
| CIMStatusCodeDescription property is in 4 classes of ROOT\Microsoft\Windows\ServerManager and in 142 namespaces |
| ▲ ErrorSource property | |
|---|---|
| CIMTYPE | ‘string’ |
| Description | ‘The identifying information of the entity (i.e., the instance) generating the error. If this entity is modeled in the CIM Schema, this property contains the path of the instance encoded as a string parameter. If not modeled, the property contains some identifying string that names the entity that generated the error. The path or identifying string is formatted per the ErrorSourceFormat property.’ |
| ModelCorrespondence | [‘CIM_Error.ErrorSourceFormat’] |
| ErrorSource property is in 4 classes of ROOT\Microsoft\Windows\ServerManager and in 142 namespaces |
| ▲ ErrorSourceFormat property | |
|---|---|
| CIMTYPE | ‘uint16’ |
| Description | ‘The format of the ErrorSource property is interpretable based on the value of this property. Values are defined as: 0 — Unknown. The format is unknown or not meaningfully interpretable by a CIM client application. 1 — Other. The format is defined by the value of the OtherErrorSourceFormat property.2 — CIMObjectPath. A CIM Object Path as defined in the CIM Infrastructure specification. Note: CIM 2.5 and earlier used the term object names.’ |
| ModelCorrespondence | [‘CIM_Error.ErrorSource’, ‘CIM_Error.OtherErrorSourceFormat’] |
| ValueMap | [‘0’, ‘1’, ‘2’, ‘..’] |
| Values | [‘Unknown’, ‘Other’, ‘CIMObjectPath’, ‘DMTF Reserved’] |
| ErrorSourceFormat property is in 4 classes of ROOT\Microsoft\Windows\ServerManager and in 142 namespaces |
| ▲ ErrorType property | |
|---|---|
| CIMTYPE | ‘uint16’ |
| Description | ‘Primary classification of the error. The following values are defined: 2 — Communications Error. Errors of this type are principally associated with the procedures and/or processes required to convey information from one point to another. 3 — Quality of Service Error. Errors of this type are principally associated with failures that result in reduced functionality or performance. 4 — Software Error. Error of this type are principally associated with a software or processing fault. 5 — Hardware Error. Errors of this type are principally associated with an equipment or hardware failure. 6 — Environmental Error. Errors of this type are principally associated with a failure condition relating the to facility, or other environmental considerations. 7 — Security Error. Errors of this type are associated with security violations, detection of viruses, and similar issues. 8 — Oversubscription Error. Errors of this type are principally associated with the failure to allocate sufficient resources to complete the operation. 9 — Unavailable Resource Error. Errors of this type are principally associated with the failure to access a required resource. 10 -Unsupported Operation Error. Errors of this type are principally associated with requests that are not supported.’ |
| ModelCorrespondence | [‘CIM_Error.OtherErrorType’] |
| ValueMap | [‘0’, ‘1’, ‘2’, ‘3’, ‘4’, ‘5’, ‘6’, ‘7’, ‘8’, ‘9’, ’10’, ‘..’] |
| Values | [‘Unknown’, ‘Other’, ‘Communications Error’, ‘Quality of Service Error’, ‘Software Error’, ‘Hardware Error’, ‘Environmental Error’, ‘Security Error’, ‘Oversubscription Error’, ‘Unavailable Resource Error’, ‘Unsupported Operation Error’, ‘DMTF Reserved’] |
| ErrorType property is in 4 classes of ROOT\Microsoft\Windows\ServerManager and in 142 namespaces |
| ▲ Message property | |
|---|---|
| CIMTYPE | ‘string’ |
| Description | ‘The formatted message. This message is constructed by combining some or all of the dynamic elements specified in the MessageArguments property with the static elements uniquely identified by the MessageID in a message registry or other catalog associated with the OwningEntity.’ |
| ModelCorrespondence | [‘CIM_Error.MessageID’, ‘CIM_Error.MessageArguments’] |
| Message property is in 4 classes of ROOT\Microsoft\Windows\ServerManager and in 142 namespaces |
| ▲ OtherErrorSourceFormat property | |
|---|---|
| CIMTYPE | ‘string’ |
| Description | ‘A string defining «Other» values for ErrorSourceFormat. This value MUST be set to a non NULL value when ErrorSourceFormat is set to a value of 1 («Other»). For all other values of ErrorSourceFormat, the value of this string must be set to NULL.’ |
| ModelCorrespondence | [‘CIM_Error.ErrorSourceFormat’] |
| OtherErrorSourceFormat property is in 4 classes of ROOT\Microsoft\Windows\ServerManager and in 142 namespaces |
| ▲ OwningEntity property | |
|---|---|
| CIMTYPE | ‘string’ |
| Description | ‘A string that uniquely identifies the entity that owns the definition of the format of the Message described in this instance. OwningEntity MUST include a copyrighted, trademarked or otherwise unique name that is owned by the business entity or standards body defining the format.’ |
| OwningEntity property is in 4 classes of ROOT\Microsoft\Windows\ServerManager and in 142 namespaces |
| ▲ PerceivedSeverity property | |
|---|---|
| CIMTYPE | ‘uint16’ |
| Description | ‘An enumerated value that describes the severity of the Indication from the notifier\’s point of view: 0 — the Perceived Severity of the indication is unknown or indeterminate. 1 — Other, by CIM convention, is used to indicate that the Severity\’s value can be found in the OtherSeverity property. 2 — Information should be used when providing an informative response. 3 — Degraded/Warning should be used when its appropriate to let the user decide if action is needed. 4 — Minor should be used to indicate action is needed, but the situation is not serious at this time. 5 — Major should be used to indicate action is needed NOW. 6 — Critical should be used to indicate action is needed NOW and the scope is broad (perhaps an imminent outage to a critical resource will result). 7 — Fatal/NonRecoverable should be used to indicate an error occurred, but it\’s too late to take remedial action. 2 and 0 — Information and Unknown (respectively) follow common usage. Literally, the Error is purely informational or its severity is simply unknown.’ |
| ValueMap | [‘0’, ‘1’, ‘2’, ‘3’, ‘4’, ‘5’, ‘6’, ‘7’, ‘..’] |
| Values | [‘Unknown’, ‘Other’, ‘Information’, ‘Degraded/Warning’, ‘Minor’, ‘Major’, ‘Critical’, ‘Fatal/NonRecoverable’, ‘DMTF Reserved’] |
| PerceivedSeverity property is in 13 classes of ROOT\Microsoft\Windows\ServerManager and in 142 namespaces |
| ▲ ProbableCause property | |
|---|---|
| CIMTYPE | ‘uint16’ |
| Description | ‘An enumerated value that describes the probable cause of the error.’ |
| ModelCorrespondence | [‘CIM_Error.ProbableCauseDescription’] |
| ValueMap | [‘0’, ‘1’, ‘2’, ‘3’, ‘4’, ‘5’, ‘6’, ‘7’, ‘8’, ‘9’, ’10’, ’11’, ’12’, ’13’, ’14’, ’15’, ’16’, ’17’, ’18’, ’19’, ’20’, ’21’, ’22’, ’23’, ’24’, ’25’, ’26’, ’27’, ’28’, ’29’, ’30’, ’31’, ’32’, ’33’, ’34’, ’35’, ’36’, ’37’, ’38’, ’39’, ’40’, ’41’, ’42’, ’43’, ’44’, ’45’, ’46’, ’47’, ’48’, ’49’, ’50’, ’51’, ’52’, ’53’, ’54’, ’55’, ’56’, ’57’, ’58’, ’59’, ’60’, ’61’, ’62’, ’63’, ’64’, ’65’, ’66’, ’67’, ’68’, ’69’, ’70’, ’71’, ’72’, ’73’, ’74’, ’75’, ’76’, ’77’, ’78’, ’79’, ’80’, ’81’, ’82’, ’83’, ’84’, ’85’, ’86’, ’87’, ’88’, ’89’, ’90’, ’91’, ’92’, ’93’, ’94’, ’95’, ’96’, ’97’, ’98’, ’99’, ‘100’, ‘101’, ‘102’, ‘103’, ‘104’, ‘105’, ‘106’, ‘107’, ‘108’, ‘109’, ‘110’, ‘111’, ‘112’, ‘113’, ‘114’, ‘115’, ‘116’, ‘117’, ‘118’, ‘119’, ‘120’, ‘121’, ‘122’, ‘123’, ‘124’, ‘125’, ‘126’, ‘127’, ‘128’, ‘129’, ‘130’, ‘..’] |
| Values | [‘Unknown’, ‘Other’, ‘Adapter/Card Error’, ‘Application Subsystem Failure’, ‘Bandwidth Reduced’, ‘Connection Establishment Error’, ‘Communications Protocol Error’, ‘Communications Subsystem Failure’, ‘Configuration/Customization Error’, ‘Congestion’, ‘Corrupt Data’, ‘CPU Cycles Limit Exceeded’, ‘Dataset/Modem Error’, ‘Degraded Signal’, ‘DTE-DCE Interface Error’, ‘Enclosure Door Open’, ‘Equipment Malfunction’, ‘Excessive Vibration’, ‘File Format Error’, ‘Fire Detected’, ‘Flood Detected’, ‘Framing Error’, ‘HVAC Problem’, ‘Humidity Unacceptable’, ‘I/O Device Error’, ‘Input Device Error’, ‘LAN Error’, ‘Non-Toxic Leak Detected’, ‘Local Node Transmission Error’, ‘Loss of Frame’, ‘Loss of Signal’, ‘Material Supply Exhausted’, ‘Multiplexer Problem’, ‘Out of Memory’, ‘Output Device Error’, ‘Performance Degraded’, ‘Power Problem’, ‘Pressure Unacceptable’, ‘Processor Problem (Internal Machine Error)’, ‘Pump Failure’, ‘Queue Size Exceeded’, ‘Receive Failure’, ‘Receiver Failure’, ‘Remote Node Transmission Error’, ‘Resource at or Nearing Capacity’, ‘Response Time Excessive’, ‘Retransmission Rate Excessive’, ‘Software Error’, ‘Software Program Abnormally Terminated’, ‘Software Program Error (Incorrect Results)’, ‘Storage Capacity Problem’, ‘Temperature Unacceptable’, ‘Threshold Crossed’, ‘Timing Problem’, ‘Toxic Leak Detected’, ‘Transmit Failure’, ‘Transmitter Failure’, ‘Underlying Resource Unavailable’, ‘Version Mismatch’, ‘Previous Alert Cleared’, ‘Login Attempts Failed’, ‘Software Virus Detected’, ‘Hardware Security Breached’, ‘Denial of Service Detected’, ‘Security Credential Mismatch’, ‘Unauthorized Access’, ‘Alarm Received’, ‘Loss of Pointer’, ‘Payload Mismatch’, ‘Transmission Error’, ‘Excessive Error Rate’, ‘Trace Problem’, ‘Element Unavailable’, ‘Element Missing’, ‘Loss of Multi Frame’, ‘Broadcast Channel Failure’, ‘Invalid Message Received’, ‘Routing Failure’, ‘Backplane Failure’, ‘Identifier Duplication’, ‘Protection Path Failure’, ‘Sync Loss or Mismatch’, ‘Terminal Problem’, ‘Real Time Clock Failure’, ‘Antenna Failure’, ‘Battery Charging Failure’, ‘Disk Failure’, ‘Frequency Hopping Failure’, ‘Loss of Redundancy’, ‘Power Supply Failure’, ‘Signal Quality Problem’, ‘Battery Discharging’, ‘Battery Failure’, ‘Commercial Power Problem’, ‘Fan Failure’, ‘Engine Failure’, ‘Sensor Failure’, ‘Fuse Failure’, ‘Generator Failure’, ‘Low Battery’, ‘Low Fuel’, ‘Low Water’, ‘Explosive Gas’, ‘High Winds’, ‘Ice Buildup’, ‘Smoke’, ‘Memory Mismatch’, ‘Out of CPU Cycles’, ‘Software Environment Problem’, ‘Software Download Failure’, ‘Element Reinitialized’, ‘Timeout’, ‘Logging Problems’, ‘Leak Detected’, ‘Protection Mechanism Failure’, ‘Protecting Resource Failure’, ‘Database Inconsistency’, ‘Authentication Failure’, ‘Breach of Confidentiality’, ‘Cable Tamper’, ‘Delayed Information’, ‘Duplicate Information’, ‘Information Missing’, ‘Information Modification’, ‘Information Out of Sequence’, ‘Key Expired’, ‘Non-Repudiation Failure’, ‘Out of Hours Activity’, ‘Out of Service’, ‘Procedural Error’, ‘Unexpected Information’, ‘DMTF Reserved’] |
| ProbableCause property is in 4 classes of ROOT\Microsoft\Windows\ServerManager and in 142 namespaces |
CIM_Error Qualifiers
| Name | Value | ToInstance | ToSubclass | Overridable | Amended | Local |
|---|---|---|---|---|---|---|
| Description | ‘CIM_Error is a specialized class that contains information about the severity, cause, recommended actions and other data related to the failure of a CIM Operation. Instances of this type MAY be included as part of the response to a CIM Operation.’ | ✗ | ✓ | ✓ | ✓ | ✓ |
| Exception | True | ✗ | ✓ | ✗ | ✗ | ✓ |
| Indication | True | ✗ | ✓ | ✗ | ✗ | ✓ |
| locale | ‘MS_409’ | ✗ | ✗ | ✓ | ✓ | ✓ |
| UMLPackagePath | ‘CIM::Interop’ | ✗ | ✓ | ✓ | ✗ | ✓ |
| Version | ‘2.22.1’ | ✗ | ✗ | ✓ | ✓ | ✓ |
CIM_Error System properties
| Name | Value | Origin | CIMType | Local | Array |
|---|---|---|---|---|---|
| __PATH | ‘\\.\ROOT\Microsoft\Windows\ServerManager:CIM_Error’ | ___SYSTEM | 8 | ✗ | ✗ |
| __NAMESPACE | ‘ROOT\Microsoft\Windows\ServerManager’ | ___SYSTEM | 8 | ✗ | ✗ |
| __SERVER | ‘.’ | ___SYSTEM | 8 | ✗ | ✗ |
| __DERIVATION | [] | ___SYSTEM | 8 | ✗ | ✓ |
| __PROPERTY_COUNT | 15 | ___SYSTEM | 3 | ✗ | ✗ |
| __RELPATH | ‘CIM_Error’ | ___SYSTEM | 8 | ✗ | ✗ |
| __DYNASTY | ‘CIM_Error’ | ___SYSTEM | 8 | ✗ | ✗ |
| __SUPERCLASS | null | ___SYSTEM | 8 | ✗ | ✗ |
| __CLASS | ‘CIM_Error’ | ___SYSTEM | 8 | ✗ | ✗ |
| __GENUS | 1 | ___SYSTEM | 3 | ✗ | ✗ |
Similar Classes to CIM_Error
Number of classes:4
comments powered by
Normally even WinRM quickconfig will also say “WinRM service is already running on this machine.” and winmgmt /verifyrepository says “WMI repository is consistent“.
To find whether WMI is properly setup or not use below setups to verify
- Open wmimgmt.msc in Run.
- WMI Control will be opened.
- Right click on and select properties.
- In ideal scenario every thing should be good with proper wmi version etc.
Or
if you run get-cimclass it should return all class and name if it return CIM namespace root/Microsoft/Windows/DesiredStateConfiguration is invalid.
Follow below steps to fix issue
- Disable and stop the winmgmt service
- Remove or rename C:\Windows\System32\wbem\repository
- Enable and start the winmgmt service
- Open a CMD prompt as Administrator
- In the CMD prompt Navigate to C:\Windows\System32\wbem\
- Run the following command: in c:\
‘for /f “delims=”%s in (‘dir /b *.mof’) do mofcomp “%s”’
Note: This will take a minute or so to complete.
- Now run the command:
‘for /f “delims=” %s in (‘dir /b en-us\*.mfl’) do mofcomp en-us\%s’
I was working on a VBScript code that uses the Windows Management Instrumentation (WMI) to query the running processes on the local machine, something like this:
strComputer = "." strProcess2Kill = "something.exe" Set objWMIService = GetObject("winmgmts:" & "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2") Set colProcess = objWMIService.ExecQuery("Select * from Win32_Process Where Name = " & strProcess2Kill) For Each objProcess In colProcess 'Now we will each one of the running processes "something.exe" objProcess.Terminate() Next
This code works in, at least, Win2k, WinXP, WinVista and Win7 (not sure if works on WinNt 4). The problem I had (as you can see here) was that the box where it should have been deployed (Win2k) showed an 0x8004100E error (Namespace specified cannot be found) on the 4th line of the code.
When I ran the following script to query all the namespaces on root:
strComputer = "." Set objSWbemServices = GetObject("winmgmts:\\" & strComputer & "\root") Set colNameSpaces = objSwbemServices.InstancesOf("__NAMESPACE") For Each objNameSpace In colNameSpaces Wscript.Echo objNameSpace.Name Next
I got this:
DEFAULT SECURITY WMI directory aspnet
As you can see, the CIMV2 namespace was not present and it should have been. So, something was wrong with the WMI installation on that box.
Then, I ran a very nice tool called wmidiag.vbs (pointed by user Uros Calakovic on my StackOverflow question) to diagnose several problems with WMI. Unfortunately, the tool gave me the same error and no proposed solution. He also mention a couple of interesting screencasts that more than one may find useful.
At the end, Google gave me the final answer once again. Reinstalling the WMI into the Windows Registry and rebuilding the WMI Repository did the trick (I did both, but maybe only the Repository rebuilding helped me this time).
In any case, to rebuild the WMI Repository, these are the only required steps:
- Stop the WMI service (net stop winmgmt)
- Go to %windows%/system32/wbem (in my win2k, winnt, on XP would be windows)
- Rename or remove the repository directory
- Start the WMI service again (net start winmgmt)
And for reinstalling WMI, you should run these commands on a console:
winmgmt /clearadap winmgmt /kill winmgmt /unregserver winmgmt /regserver winmgmt /resyncperf