Error when starting to profile w3wp.exe process
I am using...
JetBrains dotTrace 2022.1.1 Build 221.0.20220428.101234 built on 2022-04-28
dotTrace 2022.1.20220428.101234
I am trying to do a Timeline profile of a w3wp.exe process. Each time I start profiling, either immediately or when I click the "Start" button in the profile view, I get the following error...
-- Message #0
-----------------------------------------------------------------The maximum number of logging sessions on the system has been reached. No new loggers can be created until a logging session has been stopped. This value defaults to 64 on most systems. You can change this value by editing the EtwMaxLoggers REG_DWORD key at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI. Permissible values are 32 through 256, inclusive. A reboot is required for any change to take effect.
Note that Loggers use system resources. Increasing the number of loggers on the system will come at a performance cost if those slots are filled
The maximum number of logging sessions on the system has been reached: unknown error (hresult_error:ADAB0007)-----------------------------------------------------------------
It is not clear why I am getting this error.
As this is a work laptop we run Threatlocker, a security software that stop non-whitelisted processes from running, I thought it might be that causing a problem. However, when Threatlocker is blocking a process it will throw message on the screen to tell me it has blocked something. But in this case nothing appears. So I am not sure if TL is a problem in this case.
Is there further log messages I can obtain that could shed more light on this issue?
Please sign in to leave a comment.
Hello,
Threatlocker software is not the reason of controller message appearing. The message appears because too many ETW sessions are in the system. You can try to change this value by editing the EtwMaxLoggers REG_DWORD key at
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI. Permissible values are 32 through 256, inclusive. A reboot is required for any change to take effect.Note that Loggers use system resources. Increasing the number of loggers on the system will come at a performance cost if those slots are filled.
IMPORTANT! Don't set this value to 0. It can destroy your system. You need to see how many current sessions you have in the system before: Computer Manager -> Performance -> Data Collector Sets -> Event Trace Sessions. Please, count numbers of these sessions and set the value such more than the count.
We've create the issue to change the number of sessions: https://youtrack.jetbrains.com/issue/DTRC-28606/Increase-the-number-of-ETW-sessions
You are welcome to follow it.
Hello.
Thank you for your response.
As this is a work laptop I am using, I am very reluctant to edit the registry, in case I make a mistake and break something. If this is an issue that you are already looking into (ie the YourTrack link you posted) then I am happy to wait until a dotTrace update is deployed in the future that resolves this problem.
All the best.
Hello,
We'll notify you when a fix is available. We would like to draw your attention to the fact that the fix will edit the registry in the same way as we suggested you do it manually.
Thank you for your interest in our products!