Windows Server 2016 Event ID 5858 and WMI Errors

Question

Details are needed regarding Event ID 5858 in Windows Server 2016. The following operations are associated with the event:

1. Operation = Start IWbemServices::DeleteInstance - Root\Rsop\Computer : RSOP_ExtensionStatus.extensionGuid="{A3F3E39B-5D83-4940-B954-28315B82F0A8}";

• ResultCode = 0x80041002; PossibleCause = Unknown

1. Operation = Start IWbemServices::ExecMethod - ROOT\Microsoft\Windows\Smb : MSFT_SmbShare::FireShareChangeEvent;

• ResultCode = 0x80041007; PossibleCause = Unknown

  1.  Operation = Start IWbemServices::ExecQuery - root\CIMV2; resultclass = Win32_SCSIController;  
  
     -  ResultCode = 0x80041032; PossibleCause = Unknown
     
     1.  Operation = Start IWbemServices::ExecMethod - root\microsoft\windows\servermanager : MSFT_ServerManagerTasks::GetServerBpaResult;  
     
        -  ResultCode = 0x80041032; PossibleCause = Unknown
        

What do these result codes indicate, and what steps can be taken to resolve these issues?

Answer 1

Hello,

Event ID 5858 in Windows Server 2016 is related to WMI activity errors. Here are the details for the specific result codes you mentioned:

1. ResultCode = 0x80041002 (WBEM_E_NOT_FOUND):
   • Indicates: This error occurs when the specified WMI namespace or class is not found. It often points to a corrupted WMI repository.
   • Resolution: You can try rebuilding the WMI repository. Here are the steps:
   1. Open Command Prompt as an administrator.
   2. Run the following commands: net`` stop winmgmt winmgmt`` /resetrepository net`` start winmgmt
   3. Restart the server.
2. ResultCode = 0x80041007 (WBEM_E_INVALID_NAMESPACE):
   • Indicates: This error suggests that the specified namespace is invalid or does not exist.
   • Resolution: Verify that the namespace exists and is correctly spelled. You can use the wbemtest tool to connect to the namespace and check its validity.
3. ResultCode = 0x80041032 (WBEM_E_CALL_CANCELLED):
   • Indicates: This error occurs when a WMI query is canceled before it completes. It can happen if the WMI client application releases the IWbemContext object before retrieving the full result set.
   • Resolution: Ensure that the WMI client application is correctly handling the query results. The application should call IEnumWbemClassObject::Next with an appropriate timeout value and handle the WBEM_S_TIMEDOUT return code to retry the request if necessary.

Have a nice day.

Best Regards,

Hania Lian

============================================

If the Answer is helpful, please click "Accept Answer" and upvote it.