T
Tony Hinkle
I have a customer (running Windows 2003 SP2) that is attempting to enable
email alerts with Double-Take, and the following event is generated by
WinMgmt when doing so:
Event Type: Error
Event Source: WinMgmt
Event ID: 10
Description:
Event filter with query "SELECT * FROM __InstanceCreationEvent
WHERE TargetInstance ISA 'Win32_NTLogEvent' AND
(TargetInstance.SourceName = 'Double-Take' OR
TargetInstance.SourceName = 'dblhook' OR
TargetInstance.SourceName = 'NSIPH' OR
TargetInstance.SourceName = 'ExchFailover') AND
(TargetInstance.EventType = '1' OR TargetInstance.EventType = '2')" could
not be (re)activated in namespace "//./root/CIMV2" because of error
0x80042002. Events may not be delivered through this filter until the problem
is corrected.
This is occurring on only three of their servers, and we have never had this
issue reported by other customers (thousands of licenses deployed).
The error code is WBEMESS_E_REGISTRATION_TOO_PRECISE, which means, "A WITHIN
clause was not used in this query." I'm prone to disbelieve this is
accurate, as that is the same query that gets activated successfully on other
servers.
Please let me know if you have any ideas about what could be causing this.
We have tested WMI functionality in general and it is working fine except for
this.
email alerts with Double-Take, and the following event is generated by
WinMgmt when doing so:
Event Type: Error
Event Source: WinMgmt
Event ID: 10
Description:
Event filter with query "SELECT * FROM __InstanceCreationEvent
WHERE TargetInstance ISA 'Win32_NTLogEvent' AND
(TargetInstance.SourceName = 'Double-Take' OR
TargetInstance.SourceName = 'dblhook' OR
TargetInstance.SourceName = 'NSIPH' OR
TargetInstance.SourceName = 'ExchFailover') AND
(TargetInstance.EventType = '1' OR TargetInstance.EventType = '2')" could
not be (re)activated in namespace "//./root/CIMV2" because of error
0x80042002. Events may not be delivered through this filter until the problem
is corrected.
This is occurring on only three of their servers, and we have never had this
issue reported by other customers (thousands of licenses deployed).
The error code is WBEMESS_E_REGISTRATION_TOO_PRECISE, which means, "A WITHIN
clause was not used in this query." I'm prone to disbelieve this is
accurate, as that is the same query that gets activated successfully on other
servers.
Please let me know if you have any ideas about what could be causing this.
We have tested WMI functionality in general and it is working fine except for
this.