SBS 2011: Session "WBCommandletInBuiltTracing" failed to start with the following error: 0xC0000035

Dale303
Dale303 used Ask the Experts™
on
I'm getting this error message every 30 seconds on a brand new SBS 2011 machine.

MS SBS 2011 Release docs http://technet.microsoft.com/en-us/library/gg491249.aspx says...

"The error ‘Session "WBCommandletInBuiltTracing" failed to start with the following error: 0xC0000035’ appears in Network Reports
This is a Windows Kernel-EventTracing error that appears each day in the Server Event logs section of the Network Report.

You can safely ignore this error. The server is functioning correctly.
"

but it's swamping my logs.

Anyone know how to suppress this error?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Top Expert 2011
Commented:
I am afraid the only thing you could do is ignore the error and wait till there will be a hotfix available that resolves this error.
Philip ElderTechnical Architect - HA/Compute/Storage

Commented:
Have you set up your SBS Backup with the destination drives and schedule yet?

Once the backup is set up and has been running the messages may slow down some.

Verify that there are no out of the ordinary VSS errors. There are a couple that are also in that doc to ignore though.

Philip

Author

Commented:
Yes, it's all set up. There's a bunch of other intermittent errors but they're all on the 'safely ignore' list
Exploring SQL Server 2016: Fundamentals

Learn the fundamentals of Microsoft SQL Server, a relational database management system that stores and retrieves data when requested by other software applications.

Philip ElderTechnical Architect - HA/Compute/Storage

Commented:
This one is also on the "safely ignore" list:

http://blog.mpecsinc.ca/2010/12/sbs-2011-error-wbcommandletinbuilttraci.html

Philip

Author

Commented:
I would like to ignore it but it's literary taking up 99% of the entries in my logs. I'm having difficulties spotting legitimate errors amongst pages and pages of this error.
Philip ElderTechnical Architect - HA/Compute/Storage

Commented:
You can apply a filter to the Windows Event Logs to remove the chaff.

Most of our servers throw the chaff codes once in a while. Having them throw the code to the point where the logs are full is not in our experience across many servers.

Unfortunately, until someone figures out how to fix or workaround the not-so-problem we are stuck with the log entries.

Philip

Commented:
Does this filtering supporss the errors for all users?   Does it keep the errors from showing up in the SBS Console where clients can see them and get the wrong impression?  

/kenw

Commented:
To disable WBCommandletInBuiltTracing that could be safely removed :
run (Windows + R) perfmon --> Go to Data Collector Sets --> Event Trace Sessions and disable the WBCommandletInBuiltTracing.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial