Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

While running perfmon on Windows 2008 server after creating a data collector set and attempting to start I receive the following error:

"The Data Collector Set or one of its dependencies is already in use."

I have two virtual machines configured the same. It runs fine on one server, but not the other.

Any thoughts?

share|improve this question

In typical, this issue involves "NT Kernel Logger", which is a kernel event provider. This provider can not be accessed at the same time by multiple consumers (e.g., multiple data collector sets). Resource monitor accesses this provider.

See whether your DCS is collecting kernel logger information. Stop the resource monitor before running your DCS. If running multiple DCSs that collect kernel logger info, run one DCS at a time.

share|improve this answer

I had the same problem while Sysinternals Process Explorer was running. Exiting Sysinternals Process Explorer fixed the problem.

share|improve this answer
You are right, Process XP is holding on that ! – Dio Phung Mar 12 '15 at 7:53

I had a properties dialog open behind the Performance Monitor. I closed Performance Monitor, reopened Performance Monitor, then was able to start the DCS no problem.

share|improve this answer

I had the exact same problem. I found that in the Performance Monitor under Event Trace Sessions that the NT Kernel Logger was running. I stopped it and the DCS ran fine. What was weird is that on the other server that NT Kernel Logger was not there. That's why it ran with out a problem.

share|improve this answer

Open perfmon, go to the Reports folder. Expand User Defined, then your custom data collector set.

Delete the .blg files

share|improve this answer

This NT kernel logger file which is available in "Data collector set->Event Trace sessions-> NT kernel logger" should be stopped

share|improve this answer
Please provide reasoning as to why it should be stopped. If you are making a suggestion for troubleshooting, please state your answer as such. – Scott Lundberg Mar 5 at 0:50

Your Answer


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