Windows typeperf and pound signs.

Posted by Weegee on Server Fault See other posts from Server Fault or by Weegee
Published on 2009-10-07T20:02:27Z Indexed on 2010/03/28 4:03 UTC
Read the original article Hit count: 455

Filed under:
|

I'm currently trying to use typeperf to access some Windows performance counters. Unfortunately, a few of the instances I'm trying to check are of the format service#1.

The command

 typeperf "\\server\Process(service#1)\Working Set Peak"

is unfortunately returning the data for \\server\Process(service)\Working Set Peak rather than the data for the instance service#1. This holds true for any of the services that have pound signs in the counter string. Does anyone know of a method to get around this problem?

Sample output:

I:\>typeperf -s server "\Process(service#1)\Working Set"

"(PDH-CSV 4.0)","\\server\Process(service)\Working Set"
"10/08/2009 09:37:29.070","1643274240.000000"
"10/08/2009 09:37:30.070","1643274240.000000"
"10/08/2009 09:37:31.070","1643274240.000000"

The command completed successfully.

I:\>typeperf -s server "\Process(service#2)\Working Set"

"(PDH-CSV 4.0)","\\server\Process(service)\Working Set"
"10/08/2009 09:37:39.273","1643274240.000000"
"10/08/2009 09:37:40.273","1643274240.000000"
"10/08/2009 09:37:41.273","1643274240.000000"
"10/08/2009 09:37:42.273","1643274240.000000"
"10/08/2009 09:37:43.273","1643274240.000000"

The command completed successfully.

I can confirm in PerfMon that the Working Set value "1643274240.000000" is incorrect for both service#1 and service#2.

I am running Windows XP Service Pack 2, but a co-worker who is running Windows Server 2003 was having the same troubles.

© Server Fault or respective owner

Related posts about Windows

Related posts about typeperf