Session "WbadminUIInBuiltTracing" failed to start with the following error: 0xC0000035


  • Windows Server 2008 R2 Standard.

    I open the “Windows Server Backup” node in the Server Manager and see the error message in the system log after that.

    Sourece: Kernel-EventTracing

    EventID: 2

    Session "WbadminUIInBuiltTracing" failed to start with the following error: 0xC0000035

    - System 
     - Provider 
      [ Name] Microsoft-Windows-Kernel-EventTracing 
      [ Guid] {B675EC37-BDB6-4648-BC92-F3FDC74D3CA2} 
      EventID 2 
      Version 0 
      Level 2 
      Task 2 
      Opcode 12 
      Keywords 0x8000000000000010 
     - TimeCreated 
      [ SystemTime] 2010-12-01T11:17:19.937490400Z 
      EventRecordID 17 
     - Execution 
      [ ProcessID] 3472 
      [ ThreadID] 3100 
      Channel Microsoft-Windows-Kernel-EventTracing/Admin 
     - Security 
      [ UserID] S-1-5-21-1644491937-706699826-1417001333-3605 
    - EventData 
     SessionName WbadminUIInBuiltTracing 
     ErrorCode 3221225525 
     LoggingMode 2 

    What causes the error? What do I need to do to avoid it?

    Wednesday, December 01, 2010 11:36 AM


All replies

  • Hi,

    It is recommanded to post the question in following forum instead:

    Backup – Windows and Windows Server

    I found a same issue and support engineer mentioned it is harmless and will fix it in future release:

    Shaon Shan| TechNet Subscriber Support in forum| If you have any feedback on our support, please contact
    • Marked as answer by Vadim Mitin Thursday, December 09, 2010 7:30 PM
    Monday, December 06, 2010 7:49 AM
  • I have the same issue on Windows Server 2008 R2 SP1

    >will fix it in future release

    What is the next release for my Windows Server? When will it be released?

    Thursday, February 20, 2014 7:31 AM
  • Bingo, I am having the same issue:


    2008 R2

    <menu id="menuid" type="context"><menuitem icon="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQBAMAAADt3eJSAAAAMFBMVEX////4+Pf38eb/5br/257Z3OHX1tX/wmW4u7v/rTCSkpJzc3NBQUEcHBwODg4AAAB/HwUdAAAAAXRSTlMAQObYZgAAAAlwSFlzAAAOwwAADsMBx2+oZAAAAItJREFUeJxjYWDoCeLbGs/AwsBRzMAQBWKIMuxkt1d4wMLAf8ZD9pHDAhaGK2YRYQwMQCnG1c4CYAZX8J39gSBGy7/WvWCGwv8FeWApBsakRIaAhSwMBwK6BRmUy1gYZjcIbVfvf8TicidTtzrsMwPL/pK/69yVpfJZ/vaUpTHcygXq+tuu9O8BAwMA0z4ovkizRgYAAAAASUVORK5CYII%3D" label="Search"></menuitem></menu>
    Monday, March 03, 2014 1:28 AM
  • ***FIVE YEARS*** later

    way to go Micro$oft -- on top of everything as usual.

    you cannot find ONE junior level person to address things like this??????

    You say it can be ignored... is it EVER an issue?  Can I disable the trace of WbadminUIInBuiltTracing?  WHY have it?  Is this a REAL error or is it reporting a bad fail?  Will disabling this trace hide possible future issues?  Will ignoring this log entry mask real issues?  

    DO NOT TELL the community to *ignore* a big-red-x event entry without the details of why, what the impact would be.  WHY do you pay engineers to occasionally monitor these boards?  Such a lazy response with no followup is unacceptable, but is the M$ way.  NO respect for administrator community.

    The traditional solution for Micro$oft:

    1) Promise a fix "soon"

    2) Ignore the problem

    3) Propagate the problem to the next OS version

    ... and the tradition continues ...

    Software developer

    • Edited by David Wasy Saturday, November 28, 2015 12:51 PM spelling
    Saturday, November 28, 2015 12:45 PM