cloud.net

Tuesday, August 31, 2010

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.

4 comments:

Jay said...

Have you ever figured out a fix to this?

rayone said...

No unfortunately I didn't, and that's all my logs contain... 1 everyday.

GeekBoy said...

Still nothing?

rayone said...

Sorry GeekBoy, it annoys me too... I'm guessing everybody gets the error and just ignores it. All my machines with the Enterprise Search SA have it, and seems to be in the dll, so very little that can be done except complain to the developer.
If I get some time I'll see what effect stopping some of the logging has.