Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

SEPM Corrupts Windows Performance Counters

Updated: 21 May 2010 | 2 comments
STF's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

Hey Everyone, Just got involved with SEP 11 MR4 and had an issue with our management software not being able to get at the Windows Performance Counters on the SEPM server. After extensive troubleshooting I determined that SEPM is mangling the counters by appending "sem5" to all of the counters and instances. I am working with Support and the engineer found the same problem on his system with SEPM installed so I am thinking that this is a bug. Has anyone else had this problem?

 

C:\Documents and Settings\admin_admin>typeperf -qx | findstr sem5 | more
\System(sem5)\% Processor Time
\System(sem5)\8
\System(sem5)\File Read Operations/sec
\System(sem5)\File Write Operations/sec
\System(sem5)\File Control Operations/sec
\System(sem5)\File Read Bytes/sec
\System(sem5)\File Write Bytes/sec
\System(sem5)\File Control Bytes/sec
\System(sem5)\22
\System(sem5)\Available Bytes
\System(sem5)\Committed Bytes
\System(sem5)\Page Faults/sec
\System(sem5)\Commit Limit
\System(sem5)\Write Copies/sec
\System(sem5)\Transition Faults/sec
\System(sem5)\Cache Faults/sec

Comments

STF's picture
21
Jan
2009
0 Votes 0
Login to vote

This gets better... If you stop the Symantec Embedded Database the performance counters all go back to normal. Woah... I am still talking to them now... They are trying to figure it out.

STF's picture
22
Jan
2009
0 Votes 0
Login to vote

Turns out if you unreg the DLL for the Sybase Performance counters it helps the situation. All of the counters come back to normal. Only issue that remains for me is that the counters are not remotely available when polling them with our monitoring solution. If I stop the SEPM database service they become available to our management solution. I still cannot believe that I am the first person that discovered this issue.

 

C:\Program Files\Symantec\Symantec Endpoint Protection Manager\ASA\win32>regsvr32 /u dbctrs9.dll