WinMgmtR.dll
Associated Error Codes
Below lists error codes and symbolic names found for this module.
| Code | Found in | Description |
|---|---|---|
| 0x4 | 1011 | Error %1 encountered when trying to load MOF %2 while recovering .MOF file marked with autorecover. |
| 0xa | 1011 | Event filter with query "%1" could not be reactivated in namespace "%2" because of error %3. Events cannot be delivered through this filter until the problem is corrected. |
| 0x15 | 1011 | Event provider %1 attempted to register a syntactically invalid query "%2". The query will be ignored. The query can be corrected by examining the WMI repository with CIM studio and updating the permanent subscriptions for the listed provider and query. If the permanent subscription is created with MOF file coming with an installed product, the application vendor must be contacted to correct the faulty registration. |
| 0x16 | 1011 | Event provider %1 attempted to register an intrinsic event query "%2" in %3 namespace for which the set of target object classes could not be determined. The query will be ignored. |
| 0x17 | 1011 | Event provider %1 attempted to register query "%2" in %3 namespace which is too broad. Event providers cannot provide events that are provided by the system. The query will be ignored. Contact the application vendor. |
| 0x18 | 1011 | Event provider %1 attempted to register query "%2" whose target class "%3" in %4 namespace does not exist. The query will be ignored. |
| 0x19 | 1011 | Event provider %1 attempted to register query "%2" whose target class "%3" is not an event class. The query will be ignored. Contact the application vendor. |
| 0x1c | 1011 | Failed to Initialize WMI Core or Provider SubSystem or Event SubSystem with error number %1. This could be due to a badly installed version of WMI, WMI repository upgrade failure, insufficient disk space or insufficient memory. WMI will try to re-create the WMI Repository by auto-recovery mechanism on its next restart. |
| 0x1d | 1011 | Error number %1 was returned in trying to initialize Windows Management Instrumentation Service. This could be due to a badly installed version of WMI, WMI repository upgrade failure, insufficient disk space or insufficient memory. |
| 0x2b | 1011 | Windows Management Instrumentation ADAP failed to connect to namespace %1 with the following error %2 |
| 0x30 | 1011 | Windows Management Instrumentation ADAP was unable to save object %1 in namespace %2 because of the following error %3 |
| 0x3a | 1011 | Windows Management Instrumentation ADAP was unable to create the Win32_Perf base class in %1:Result=%2 |
| 0x3b | 1011 | Windows Management Instrumentation ADAP was unable to create the Win32_PerfRawData base class %1 |
| 0x3f | 1011 | A provider, %1, has been registered in the Windows Management Instrumentation namespace %2 to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. |
| 0x41 | 1011 | Windows Management Instrumentation (WMI) Service is starting to restore the WMI repository |
| 0x42 | 1011 | The Windows Management Instrumentation Service has recovered from the following backup repository: %1. |
| 0x43 | 1011 | The Windows Management Instrumentation (WMI) Service is starting the backup operation for the WMI repository and is copying data to the following file: %1 |
| 0x44 | 1011 | The Windows Management Instrumentation repository backup operation completed copying data to %1 with error %2. |
| 0x15e0 | 1011 | The Windows Management Instrumentation (WMI) service detected an inconsistency with the WMI repository in the following directory: %windir%\system32\wbem\repository. The WMI service was not able to recover the repository. The WMI repository will now be deleted and a new repository will be created based on the auto-recovery mechanism. |
| 0x15e1 | 1011 | The Windows Management Instrumentation Service failed to load the repository files under the directory %windir%\system32\wbem\repository. This can be caused by a corruption in the repository files, security settings on this directory, lack of disk space, or other system resource issues like lack of memory. If this error happens every time the machine is rebooted then the administrator on this machine may need to stop WMI Service, review the security setting on this folder and files under this folder, and run WMIDiag to validate the health of Windows Management Instrumentation |
| 0x15e2 | 1011 | The Windows Management Instrumentation service detected an inconsistency in the following backup file: %1. |
| 0x15e4 | 1011 | The Windows Management Instrumentation service encountered the error %1 and was not able to restore from the following backup repository: %2. |
| 0x15e5 | 1011 | The %1 namespace is marked with the RequiresEncryption flag. Access to this namespace might be denied if the script or application does not have the appropriate authentication level. Change the authentication level to Pkt_Privacy and run the script or application again. |
| 0x15e6 | 1011 | Windows Management Instrumentation Service could not deliver results asynchronously for %1 namespace. The namespace is marked with RequiresEncryption but WinMgmt could not establish a secure connection back to the client computer. Ensure there is a trust relationship between the client and server computers so that the client recognizes the server computer account. |
| 0x15eb | 1011 | The Windows Management Instrumentation service has detected an inconsistent system shutdown. |
| 0x15ec | 1011 | Windows Management Instrumentation has stopped WMIPRVSE.EXE because a quota reached a warning value. Quota: %1 Value: %2 Maximum value: %3 WMIPRVSE PID: %4 Providers hosted in this process: %5 |
| 0x15ee | 1011 | During the service startup, the Windows Management Instrumentation service was unable to locate the repository files. A new repository will be created based on the auto-recovery mechanism. |
| 0x15ef | 1011 | Windows Management Instrumentation Service started sucessfully |
| 0x15f0 | 1011 | The Windows Management Instrumentation (WMI) repository was successfully re-created by the auto-recovery mechanism. |
| 0x15f1 | 1011 | Windows Management Instrumentation Service subsystems initialized successfully |
| 0x15ff | 1011 | WMI interop namespace class "%1" has been overwritten. Some of the Interop scenarios might not work properly. Please issue following commands from elevated command prompt to restore the behavior."mofcomp %windir%\system32\wbem\interop.mof" and similarly mofcomp all the interop.mfl under %windir%\system32\wbem and its subdirectories. |
| 0x10000038 | 1011 | Classic |
| 0x400015e0 | 1011 | The Windows Management Instrumentation (WMI) service detected an inconsistency with the WMI repository in the following directory: %windir%\system32\wbem\repository. The WMI service was not able to recover the repository. The WMI repository will now be deleted and a new repository will be created based on the auto-recovery mechanism. |
| 0x50000002 | 1011 | Error |
| 0x50000003 | 1011 | Warning |
| 0x50000004 | 1011 | Information |
| 0x8000003f | 1011 | A provider, %1, has been registered in the Windows Management Instrumentation namespace %2 to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. |
| 0x90000001 | 1011 | Microsoft-Windows-WMI |
| 0x90000002 | 1011 | Application |
| 0x91000001 | 1011 | Microsoft-Windows-WMI-Activity |
| 0xb1000001 | 1011 | GroupOperationId = %1; OperationId = %2; Operation = %3; ClientMachine = %4; User = %5; ClientProcessId = %6; NamespaceName = %7 |
| 0xb1000002 | 1011 | ProviderInfo for GroupOperationId = %1; Operation = %2; ProviderName = %3; ProviderGuid = %4; Path = %5 |
| 0xb1000003 | 1011 | Stop OperationId = %1 |
| 0xb100000b | 1011 | CorrelationId = %1; GroupOperationId = %2; OperationId = %3; Operation = %4; ClientMachine = %5; User = %7; ClientProcessId = %8; NamespaceName = %9 |
| 0xb100000c | 1011 | ProviderInfo for GroupOperationId = %1; Operation = %2; HostID = %3; ProviderName = %4; ProviderGuid = %5; Path = %6 |
| 0xb100000d | 1011 | Stop OperationId = %1; ResultCode = %2 |
| 0xb100000e | 1011 | OperationId = %1; Operation = %2; Channel = %3; Message = %4 |
| 0xb100000f | 1011 | OperationId = %1; Operation = %2; ErrorID = %3; ErrorCategory = %4; Message = %5; TargetName = %6 |
| 0xb1000010 | 1011 | OperationId = %1; Operation = %2; ErrorID = %3; Message = %4 |
| 0xb1000011 | 1011 | CorrelationId = %1; ProcessId = %2; Protocol = %3; Operation = %4; User = %5; Namespace = %6 |
| 0xb1000012 | 1011 | WMI Events were dropped. ConsumerType = %1; Possiblecause = %2 |
| 0xb1000013 | 1011 | Performing delete operation on the WMI repository. OperationID = %1; Operation = %2 |
| 0xb1000014 | 1011 | Performing Update operation on the WMI repository. OperationID = %1; Operation = %2; Flags = %3 |
| 0xb1000015 | 1011 | WMI Events were bound. ConsumerType = %1; Possiblecause = %2 |
| 0xb1000016 | 1011 | CorrelationId = %1; GroupOperationId = %2; OperationId = %3; ClassName= %4; MethodName = %5; ImplementationClass = %6; ClientMachine = %7; User = %9; ClientProcessId = %10; NamespaceName = %12 |
| 0xb1000017 | 1011 | CorrelationId = %1; GroupOperationId = %2; OperationId = %3; Commandline= %4; CreatedProcessId = %5; ClientMachine = %6; User = %8; ClientProcessId = %9 |
| 0xb1000032 | 1011 | Activity Transfer |
| 0xb1000064 | 1011 | ComponentName = %1; MessageDetail = %2; FileName = %3 |
| 0xb1000065 | 1011 | ComponentName = %1; ErrorId = %2; ErrorDetail = %3; FileName = %4 |
| 0xb10016e1 | 1011 | %1 provider started with result code %2. HostProcess = %3; ProcessID = %4; ProviderPath = %5 |
| 0xb10016e2 | 1011 | Id = %1; ClientMachine = %2; User = %3; ClientProcessId = %4; Component = %5; Operation = %6; ResultCode = %7; PossibleCause = %8 |
| 0xb10016e3 | 1011 | Namespace = %1; NotificationQuery = %2; OwnerName = %3; HostProcessID = %4; Provider= %5, queryID = %6; PossibleCause = %7 |
| 0xb10016e4 | 1011 | Namespace = %1; NotificationQuery = %2; UserName = %3; ClientProcessID = %4, ClientMachine = %5; PossibleCause = %6 |
| 0xb10016e5 | 1011 | Namespace = %1; Eventfilter = %2 (refer to its activate eventid:5859); Consumer = %3; PossibleCause = %4 |
| 0xc0000004 | 1011 | Error %1 encountered when trying to load MOF %2 while recovering .MOF file marked with autorecover. |
| 0xc000000a | 1011 | Event filter with query "%2" could not be reactivated in namespace "%1" because of error %3. Events cannot be delivered through this filter until the problem is corrected. |
| 0xc0000015 | 1011 | Event provider %1 attempted to register a syntactically invalid query "%2". The query will be ignored. The query can be corrected by examining the WMI repository with CIM studio and updating the permanent subscriptions for the listed provider and query. If the permanent subscription is created with MOF file coming with an installed product, the application vendor must be contacted to correct the faulty registration. |
| 0xc0000016 | 1011 | Event provider %1 attempted to register an intrinsic event query "%2" in %3 namespace for which the set of target object classes could not be determined. The query will be ignored. |
| 0xc0000017 | 1011 | Event provider %1 attempted to register query "%2" in %3 namespace which is too broad. Event providers cannot provide events that are provided by the system. The query will be ignored. Contact the application vendor. |
| 0xc0000018 | 1011 | Event provider %1 attempted to register query "%2" whose target class "%3" in %4 namespace does not exist. The query will be ignored. |
| 0xc0000019 | 1011 | Event provider %1 attempted to register query "%2" whose target class "%3" is not an event class. The query will be ignored. Contact the application vendor. |
| 0xc000001c | 1011 | Failed to Initialize WMI Core or Provider SubSystem or Event SubSystem with error number %1. This could be due to a badly installed version of WMI, WMI repository upgrade failure, insufficient disk space or insufficient memory. |
| 0xc000001d | 1011 | Error number %1 was returned in trying to initialize Windows Management Instrumentation Service. This could be due to a badly installed version of WMI, WMI repository upgrade failure, insufficient disk space or insufficient memory. |
| 0xc000002b | 1011 | Windows Management Instrumentation ADAP failed to connect to namespace %1 with the following error %2 |
| 0xc0000030 | 1011 | Windows Management Instrumentation ADAP was unable to save object %1 in namespace %2 because of the following error %3 |
| 0xc000003a | 1011 | Windows Management Instrumentation ADAP was unable to create the Win32_Perf base class in %1:Result=%2 |
| 0xc000003b | 1011 | Windows Management Instrumentation ADAP was unable to create the Win32_PerfRawData base class %1 |
| 0xc0000041 | 1011 | Windows Management Instrumentation (WMI) Service is starting to restore the WMI repository |
| 0xc0000042 | 1011 | The Windows Management Instrumentation Service has recovered from the following backup repository: %1. |
| 0xc0000043 | 1011 | The Windows Management Instrumentation (WMI) Service is starting the backup operation for the WMI repository and is copying data to the following file: %1 |
| 0xc0000044 | 1011 | The Windows Management Instrumentation repository backup operation completed copying data to %1 with error %2. |
| 0xc00015e1 | 1011 | The Windows Management Instrumentation Service failed to load the repository files under the directory %windir%\system32\wbem\repository. This can be caused by a corruption in the repository files, security settings on this directory, lack of disk space, or other system resource issues like lack of memory. If this error happens every time the machine is rebooted then the administrator on this machine may need to stop WMI Service, review the security setting on this folder and files under this folder, and run WMIDiag to validate the health of Windows Management Instrumentation |
| 0xc00015e2 | 1011 | The Windows Management Instrumentation service detected an inconsistency in the following backup file: %1. |
| 0xc00015e4 | 1011 | The Windows Management Instrumentation service encountered the error %2 and was not able to restore from the following backup repository: %1. |
| 0xc00015e5 | 1011 | The %1 namespace is marked with the RequiresEncryption flag. Access to this namespace might be denied if the script or application does not have the appropriate authentication level. Change the authentication level to Pkt_Privacy and run the script or application again. |
| 0xc00015e6 | 1011 | Windows Management Instrumentation Service could not deliver results asynchronously for %1 namespace. The namespace is marked with RequiresEncryption but WinMgmt could not establish a secure connection back to the client computer. Ensure there is a trust relationship between the client and server computers so that the client recognizes the server computer account. |
| 0xc00015eb | 1011 | The Windows Management Instrumentation service has detected an inconsistent system shutdown. |
| 0xc00015ec | 1011 | Windows Management Instrumentation has stopped WMIPRVSE.EXE because a quota reached a warning value. Quota: %1 Value: %2 Maximum value: %3 WMIPRVSE PID: %4 Providers hosted in this process: %5 |
| 0xc00015ee | 1011 | During the service startup, the Windows Management Instrumentation service was unable to locate the repository files. A new repository will be created based on the auto-recovery mechanism. |
| 0xc00015ef | 1011 | Windows Management Instrumentation Service started sucessfully |
| 0xc00015f0 | 1011 | The Windows Management Instrumentation (WMI) repository was successfully re-created by the auto-recovery mechanism. |
| 0xc00015f1 | 1011 | Windows Management Instrumentation Service subsystems initialized successfully |
| 0xc00015ff | 1011 | WMI interop namespace class "%1" has been overwritten. Some of the Interop scenarios might not work properly. Please issue following commands from elevated command prompt to restore the behavior."mofcomp %windir%\system32\wbem\interop.mof" and similarly mofcomp all the interop.mfl under %windir%\system32\wbem and its subdirectories. |
| 0xb1000018 | 11 | GroupOperationId = %1; Executing polling query %2 in namespace %3 |
| 0xb1010018 | 11 | GroupOperationId = %1; Executing polling query %2 in namespace %3; ClientProcessId = %4; IntervalMs = %5 |
| 95 entries | ||