Quantcast
Channel: Silk Performer
Viewing all articles
Browse latest Browse all 4084

Wiki Page: Why do I encounter the error "PerfMon: error when accessing a Windows PerfMon counter (PDH: 288 - Attempt to release mutex not owned by caller., )" when executing a SilkCentral Infrastructure monitor?

$
0
0
If you encounter the error message: "RepMessage(RT: 14 - Custom Message, PerfMon: error when accessing a Windows PerfMon counter (PDH: 288 - Attempt to releasemutex not owned by caller., ); Monitor will be restarted.)" when executing a SilkCentral "Self Monitoring Infrastructure Monitor" the most likely cause of the error is that the "Self Monitoring Infrastructure Monitor" isattempting to monitor part of the SilkCentral Performance Manager installation which does not reside on the same machine as the "Infrastructure Server" which is executing the monitor. For example the error message has occurred on distributed SilkCentral Performance Manager installations in which the SQLServer Database was located on a different machine from the Infrastructure Monitor Server (which hosted the SilkCentral App,Frontend, Charting and Execution Server). To resolve the error in this scenario you would set the value of the "SQL Server" project attribute to FALSE, so that when the "Self Monitoring Infrastructure Monitor" is executed it will not attempt to monitor SQL Server for data, thus avoiding the error message.

Viewing all articles
Browse latest Browse all 4084

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>