Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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.

share|improve this question
    
I get different, but consistent, results for every pair (with and without #1) that I tried. Perhaps you could add sample results to your question. Also, in case it makes a difference, you should post which version of Windows. –  Dennis Williamson Oct 7 '09 at 20:42
    
Updated with sample output. –  Weegee Oct 8 '09 at 14:45
1  
I thought a pound sign was £... –  Mark Henderson May 11 '10 at 22:29

1 Answer 1

Interesting, I'm having similar issues. However, my behavior is different.

For me, the # signs are recognized properly under Windows Server 2003 (SP2) and Vista. But I have the same issue with XP SP2.

An interesting thing to note as well, typeperf can seem to list or output the counters with # signs, it just can't seem to report them when you supply them as input, from the command line or a counter input file.

Perfmon can report them fine. I wonder why all this difference.

Too bad there is not enough typeperf users out there to get this resolved or looked into by Microsoft or others.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.