I have duplicated this on 4 different workstations running WinXP and the
..Net framework. Viewing any of the .NET CLR counters in PerfMon works fine
when viewing then "live," but fails to capture any data when setting them up
as scheduled captures under Counter Logs. All of the non-.Net counters
capture fine, but not the .Net ones?!? Has anyone else seen this and does
anyone know of a workaround?

tia,
Bill

Which counters are you logging? Which process are you binding it to?
Perfmon will display only those processes that have the .net framework
loaded when displaying processes for the .NET counters. Are you sure your
process name will be unique when you have even the non .NET processes are
taken into consideration?

"bu" wrote:

Santosh,

Thanks for the reply.

I am using a mixture of .Net CLR Memory, Data, Interop, Locks & Threads, and
a few others and am binding them to an in-house application written using
the framework. I am also using some Process counters tied to the same
application and those capture fine. The only issue is with the .Net CLR
counters - when configuring them as Counter Logs (logged to the drive
instead of viewed on screen), absolutely no data gets recorded.... though
it gets recorded for all other non-.Net counters... including the Process
counters tied to the same application....

Bill


"Santosh" <Santosh (AT) discussions (DOT) microsoft.com> wrote

Hmm. Am not sure if this will help, But I had a similar issue because the
Image name that ws being used was not unique. I wanted to profile the dllhost
process which contained my ServicedComponent. If you see in the 'Process'
Performance object, you will see multiple dllhosts shown as dllhost,
dllhost#1, and so on. However, At the same instance of time, the .NET CLR
counters will show only dllhost(when only one ServicedComponent is
initialized). So, when I switch on logging, I was logging the dllhost which
is the System Application where as the one that had to be logged was
dllhost#1.
Hope this helps.

"bu" wrote:

Nevermind... I found the fix. You need to change the Logon Account that the
"Performance Logs and Alerts" service uses... the default is set to Network
Service, but changing it to either a local Administrator account or the
Local System Account will fix the issue.




"bu" <bu (AT) nospam (DOT) com> wrote