Version

Argent XT 8.0A-1104 or above; possibly on Argent AT as well as this appears to be a Microsoft bug

Date

Tuesday, 7 Jan 2014

Summary

Intermittent PDH error 102 on Windows 2012 Enterprise Server causes false correction notification Alert

Technical Background

It is seen that although the condition is still valid (Rule is considered broken), often correction notification Alerts are received

The following lines are present in Relator Trace Log which suggests that unsuccessful connection to the PDH interface results in PDH error 102

Because of this after a number of connection retries, it gives up connecting to the PDH interface of the server until the next scheduled run time of the Relator

This results in the Metric not being available (in this case Free Megabyte); hence the Relator comes up with Not Broken verdict, resets the escalation and issues the correction notification Alert

Excerpts from the Relator Trace Log

Tue Jan 07 07:48:07.341 ARG1 A1 Start testing server WIN2012 using 64-bit Monitor Engine



Tue Jan 07 07:54:57.420 ARG1 A1 Any(REGEXPR([C-Z]:)) of \LogicalDisk(*)\Free Megabytes not available - Not Broken



Tue Jan 07 07:54:57.420 ARG1 A1 >>> Total Time Consumed: 410.015 <<<



Tue Jan 07 07:49:07.359 ARG1 A1 PDH error 102 on machine WIN2012(PdhOpenQuery) (Rel: REL_PRF_FREE_5GB)



Tue Jan 07 07:49:17.359 ARG1 A1 Retry connecting to PDH interface of server 'WIN2012'



Tue Jan 07 07:54:57.420 ARG1 A1 Give up connecting to PDH interface of server WIN2012(Rel: REL_PRF_FREE_5GB)



Tue Jan 07 07:55:37.508 ARG1 A1 (Result) Any(REGEXPR([C-Z]:)) of \LogicalDisk(*)\Free Megabytes not available



Tue Jan 07 07:55:45.525 ARG1 A1 Rule 'PRF_DISK_FREE_SPACE_5GB' is no longer broken. Reset escalation

Resolution

This issue is under investigation