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

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



Cause:
The Search Health Monitoring - Trace Events job can't access a Health Monitoring resource.

The offending class is Microsoft.Office.Server.Search.Monitoring.TraceDiagnosticsProvider this job is run every minute and if it conflicts with another job accessing the same resource it will fail.

The following PS command will return Jobs scheduled to run < every 5 minutes:

Get-SPTimerJob | Where {$_.IsDisabled -eq $FALSE -and $_.Schedule.Description -eq "Minutes" -and $_.Schedule.Interval -lt "5"} | Foreach-Object{$_.PSObject.Properties | Select-Object Name,Value;}



Fix:
Changed the Search Health Monitoring - Trace Events job schedule to every 2 minutes, if you really want to have clean logs.

Update: I'm working on the fix but it seems related to current SP log file.

Proactively monitoring SPS 2010 and MOSS

I was recently introduced to what is now a critical tool. The ULS Viewer http://code.msdn.microsoft.com/ULSViewer



The ULSViewer tool performs various actions against the data from ULS log files in order to better analyze it. ULSViewer allows the user to: 

• Highlight data of importance to the user on the fly


• Bookmark log entries


• Append logs to other logs in order to track trends


• Hide unimportant data


• Only view critical log entries by sorting data by severity


• Write rules to prompt the user when certain events occur


• View your data in a spreadsheet instead of the text file ULS generates


• Monitor remote machines logs that are running ULS services


• Open multiple logs at the same time in order to compare log files.


• Open logs files from multiple machines at the same time.