If you receive a message – An error occurred while trying to generate this report, the data collector set or one of its dependencies is already in use, when running perfmon / report to generate a report using the resource and performance monitor, then this message explains what you can do about it.
Resource Monitor is a nice built-in tool that allows you to monitor and study how the applications you run affect your computer’s performance, both in real time and by collecting log data for later analysis. You can also use it to generate a system health report.
To generate a performance report for your system, open Run, type the following, and press Enter:
But sometimes, instead of generating the report, you may receive an error message.
The data collection set or one of its dependencies is already in use
This issue involves «NT Kernel Logger», which is a kernel event provider. This provider cannot be accessed by multiple consumers at the same time (for example, multiple sets of data collectors). To resolve this issue, verify that DCS collects information from the kernel log. Stop monitoring resources before running DCS. If you are running multiple DCSs that collect information from the kernel log, run one DCS at a time.
If you’re facing this issue, here are some things you might want to try:
1]Restart the computer and run it perfmon / report and see if it works this time. Otherwise, perform Clean Boot and try running perfmon / report and you see it generating a report.
2]Download and use Process manager from Microsoft and see if you can identify the process that the data set can use. This is an advanced monitoring tool for Windows that shows the real-time file system, registry and process / thread activity.
3]Open the Service Manager and make sure that the following Windows services are configured in the Manual:
Performance logs and alerts.
Problem reporting and solution control panel support.
You can manually start these services here and then run perfmon / report and see.
4]From the Start menu, open Event Manager and navigate to the following logs:
Event Viewer> Application and Services Log> Microsoft> Windows> Diagnostics-PLA
Write down the event ID, error details, and try searching for online help on Microsoft sites.
Hope this helps.