Bienvenido! - Willkommen! - Welcome!

Bitácora Técnica de Tux&Cía., Santa Cruz de la Sierra, BO
Bitácora Central: Tux&Cía.
Bitácora de Información Avanzada: Tux&Cía.-Información
May the source be with you!

Monday, July 16, 2012

"Circular Kernel Context Logger" failed to start

Session "Circular Kernel Context Logger" failed to start with the following error: 0xC0000035
Event ID 2
0xC0000035 stands for STATUS_OBJECT_NAME_COLLISION, which means two objects names collide.
First of all, before going further you should confirm that the logger is actually working:
  1. Open Control Panel -> System -> Administrative Tools -> Performance Monitor.
  2. Under Data Collector Sets -> Event Trace Sessions, verify that the Context Logger is running.
If it is running, there isn't really a problem; so you should just filter or ignore the error and move on.
If there is however a problem, you can try some suggestions or analyze the prolem in more details:
  1. Check what happens with the log files by using Process Monitor and look at C:\PerfLogs\Admin and also pay noitce for any other failing operations when you restart the Context Logger yourself.
  2. Use API Monitor and hook into the object name related functions or modules, this requires research...
I found this worked for a number of people:
ipconfig /flushdns ipconfig /release /all they rebooted, but ipconfig /renew should work
They reported no errors after that.
Session "Circular Kernel Context Logger" failed to start with the following error: 0xC0000035:
Windows version: Windows 7 64bit
If you are getting this message do as follows:
  1. Start
  2. click All Programs, and then click Accessories.
  3. Right-click Command Prompt, and then click Run as administrator.
  4. Type powercfg -h on and then press ENTER.

No comments: