M
matchbox
Question: what can cause the DS Access perfmon counter to break / cause
counter ID to become out of range and thus not be available for
collection.
I have just used the lodctr dscperf.ini cmdline to load these counters.
On one cluster this worked fine. I moved on to the next cluster and it
failed. I tried unlodctr dscperf.ini and then the load cmd but it
wouldn't work.
the annoying thing is that the cluster on which the load cmd work then
lost its ds access counters. in the extensible counters listing tool
denoted as * which i beleive means out of range. I have loaded them
back in .... but we appear to have ds access issues and this might be a
symptom.
counter ID to become out of range and thus not be available for
collection.
I have just used the lodctr dscperf.ini cmdline to load these counters.
On one cluster this worked fine. I moved on to the next cluster and it
failed. I tried unlodctr dscperf.ini and then the load cmd but it
wouldn't work.
the annoying thing is that the cluster on which the load cmd work then
lost its ds access counters. in the extensible counters listing tool
denoted as * which i beleive means out of range. I have loaded them
back in .... but we appear to have ds access issues and this might be a
symptom.