none
Error: OfficeSearch14HealthSession

    Question

  • Enviorment: Two Sharepoint VM's in a Farm (Array NLB), with a SQL 2008 Ent (Cluster) VM for the database backbone.

    SharePoint 2010: Error in windows event log. (Repeats Everyday @ or close to the same hour.)

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

     ------------------------

    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="Microsoft-Windows-Kernel-EventTracing" Guid="{B675EC37-BDB6-4648-BC92-F3FDC74D3CA2}" />
      <EventID>2</EventID>
      <Version>0</Version>
      <Level>2</Level>
      <Task>2</Task>
      <Opcode>12</Opcode>
      <Keywords>0x8000000000000010</Keywords>
      <TimeCreated SystemTime="2010-08-08T10:11:14.353338200Z" />
      <EventRecordID>11425</EventRecordID>
      <Correlation />
      <Execution ProcessID="4196" ThreadID="5228" />
      <Channel>Microsoft-Windows-Kernel-EventTracing/Admin</Channel>
      <Computer>atlas1.ess.est</Computer>
      <Security UserID="********Deleted for Security Reasons********" />
      </System>
    - <EventData>
      <Data Name="SessionName">OfficeSearch14HealthSession</Data>
      <Data Name="FileName" />
      <Data Name="ErrorCode">3221225525</Data>
      <Data Name="LoggingMode">256</Data>
      </EventData>
      </Event>

    Tuesday, August 10, 2010 10:43 PM

Answers

  • I have the same problem here. It is directly related to SharePoint 2010. No other software or services is installed or enabled.


    I think that this is Microsoft doing poor multithreaded programming. First, 0xC0000035 stands for STATUS_OBJECT_NAME_COLLISION. I made up the following PowerShell script to reliably reproduce the error:

    # Restart SharePoint 2010 Tracing service.
    Start-Job -ScriptBlock {Restart-Service sptracev4} # Returns without waiting for the service.

    # Run "Search Health Monitoring - Trace Events" SharePoint Timer Job now.
    $job = Get-SPTimerJob -Identity "Search Health Monitoring - Trace Events"
    $job.Execute([System.Guid]::Empty)

    # Now go to Event Log to see the new error.

    Possible explanation (sequence of events):
    1. The timer job detects that a new log file must be created (in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS).
    2. Tracing Service starts up and actually creates the new log file.
    3. The timer job tries to create the file with the same time-derived name, which of course fails.

    During usual operations - in unfortunate occasion when "Search Health Monitoring - Trace Events" job runs (it does so every minute) at the same time when tracing rolls over to a new log file, you get this error.


    The conclusion is that this event log entry may be disturbing, but probably false alarm, and should be ignored.


    Rock Wang, can you confirm?

    Thursday, August 12, 2010 2:55 PM

All replies

  • Hi Exchange Street Solutions,

     

    From the provider name, it seems that it isn’t related to SharePoint 2010. Did you install any other software or enable other service on your SharePoint server?

     

    If so, please uninstall or disable them, then check the effect.

     

    From your post, you can find the following information:

     

    <Execution ProcessID="4196"ThreadID="5228" />

     

    You can use Process Monitor to capture the log, and investigate who the process is.

     

    Process Monitor v2.8

    http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx

     

    In addition, please post the description of the error into the forum for further analyze.

     

     


    Regards, Rock Wang Microsoft Online Community Support
    • Proposed as answer by Marli Butler Monday, March 18, 2013 9:23 AM
    Thursday, August 12, 2010 8:26 AM
  • I have the same problem here. It is directly related to SharePoint 2010. No other software or services is installed or enabled.


    I think that this is Microsoft doing poor multithreaded programming. First, 0xC0000035 stands for STATUS_OBJECT_NAME_COLLISION. I made up the following PowerShell script to reliably reproduce the error:

    # Restart SharePoint 2010 Tracing service.
    Start-Job -ScriptBlock {Restart-Service sptracev4} # Returns without waiting for the service.

    # Run "Search Health Monitoring - Trace Events" SharePoint Timer Job now.
    $job = Get-SPTimerJob -Identity "Search Health Monitoring - Trace Events"
    $job.Execute([System.Guid]::Empty)

    # Now go to Event Log to see the new error.

    Possible explanation (sequence of events):
    1. The timer job detects that a new log file must be created (in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS).
    2. Tracing Service starts up and actually creates the new log file.
    3. The timer job tries to create the file with the same time-derived name, which of course fails.

    During usual operations - in unfortunate occasion when "Search Health Monitoring - Trace Events" job runs (it does so every minute) at the same time when tracing rolls over to a new log file, you get this error.


    The conclusion is that this event log entry may be disturbing, but probably false alarm, and should be ignored.


    Rock Wang, can you confirm?

    Thursday, August 12, 2010 2:55 PM
  • Session "OfficeSearch14HealthSession" failed to start with the following error: 0xC0000035

    OfficeSearch14HealthSession <--- Is appart of sharepoint 2010's search services

    *Fresh install of SharePoint 2010, In a farm enviorment.

     

    My VM's

    SharePoint 2010 Ent(Farm)(Server 1)

    SharePoint 2010 Ent(Farm)(Server 2)

    SQL 2008 Ent (Cluster) (Server 1)

    SQL 2008 Ent (Cluster) (Server 2)

    Exchange 2010 Ent (Array)(CAS)(SRV1)

    Exchange 2010 Ent (Array)(CAS)(SRV2)

    Exchange 2010 Ent (Cluster)(DB)(SRV3)

    Exchange 2010 Ent (Cluster)(DB)(SRV4)

     

    Wednesday, August 18, 2010 12:25 AM
  • I am also getting this every 24 hours, does anyone have a solution apart from ignore it?

    Is there a way to remove events from the event log that can be 'safely' ignored?

    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="Microsoft-Windows-Kernel-EventTracing" Guid="{B675EC37-BDB6-4648-BC92-F3FDC74D3CA2}" />
      <EventID>2</EventID>
      <Version>0</Version>
      <Level>2</Level>
      <Task>2</Task>
      <Opcode>12</Opcode>
      <Keywords>0x8000000000000010</Keywords>
      <TimeCreated SystemTime="2011-01-27T17:12:09.014469800Z" />
      <EventRecordID>804</EventRecordID>
      <Correlation />
      <Execution ProcessID="6600" ThreadID="2956" />
      <Channel>Microsoft-Windows-Kernel-EventTracing/Admin</Channel>
      <Computer>...</Computer>
      <Security UserID="..." />
      </System>
    - <EventData>
      <Data Name="SessionName">OfficeSearch14HealthSession</Data>
      <Data Name="FileName" />
      <Data Name="ErrorCode">3221225525</Data>
      <Data Name="LoggingMode">256</Data>
      </EventData>
      </Event>

    mmm... coffee...
    Friday, January 28, 2011 3:21 AM
  • Same here... repeats every 24 hours at the same time (about 6:11am). I recently pushed the "Timer Service Recycle" job to start at 6:30am instead of 6am. This also pushed the error for the OfficeSearch14HealthSession up by exactly 30 minutes (6:41am).

    So 11 minutes after the Timer Service Recycle job runs, this error occurs.

    Thursday, March 03, 2011 5:10 PM
  • Same here. I configured search service yesterday, and today at 6:11 am got this error.

    Physical server farm, Win2008R2, SQL Server 2008 R2 in the same machine.

    Friday, March 04, 2011 8:54 AM
  • Same here. repeats every 24hours at the same time: 6:11am

    Virtual server farm Win2008R2, SQL Server 2008 R2 in two diffrent machines.

    Thanks to Janis Norvelis for his explanation.

    Thursday, March 10, 2011 7:36 AM
  • Here same.

    Repeats every 24 hours. Exactly 11 Minutes after the service "Timer Service Recycle" starts.
    Also if the service is started manually.

    Any News?

    Monday, June 06, 2011 7:47 AM
  • Ditto, repeats every 24hours at the same time: 6:11am.

    xen virtual (yuk), wfe, app, sql
    Thursday, August 11, 2011 8:41 PM
  • Me 2. Did anybody get an answer for this?


    davidh
    Monday, December 05, 2011 3:35 PM
  • any news on this?
    Tuesday, March 27, 2012 1:24 PM
  • I'm getting the same error
    Wednesday, April 04, 2012 8:34 AM
  • Same error eror here too.
    Thursday, April 26, 2012 11:44 AM
  • Same error here too .... brand new farm, February 2012 cumulative updates. 

    Lady_M MCITP SharePoint 2010 MOCS SharePOint 2010

    Tuesday, May 08, 2012 12:46 PM
  • I, too, am having this same issue.  Any assistance that can be given would be grateful.

    Thank you.

    Michael D. Arnell
    SharePoint Administrator

    Wednesday, May 09, 2012 9:53 PM
  •  Hi,

    now we wait nine months for a microsoft developer who find a solution for this issue.


    Viele Grüße / best regards Markus M.

    • Proposed as answer by Marli Butler Monday, March 18, 2013 9:48 AM
    Wednesday, May 09, 2012 10:28 PM
  • Dear Microsoft,

    We are trying to use SharePoint 2010 but there are a number of issues that continue on a daily basis. The forum questions (like this one) go unanswered.

    We cannot go on waiting and waiting and we need a resolution if you want us to keep using SharePoint (especially in production).

    We know it is a complex piece of software and you should be devoting sufficient resources to its development.

    So far we have only received huge Hotfixes which do not inspire us with any confidence that the product development cycle is proceeding correctly.

    We are an extension of you to our users and if you continue to keep us in the dark, we will have little choice but to choose something else. I urge you to improve the transparency and help us help you to get this product sorted out and running smoothly.

    Please have someone respond to the forum questions in a timely and professional manner.

    Thank you

    Friday, August 03, 2012 5:06 PM
  • Same here...

    Tuesday, August 21, 2012 4:57 PM
  • Same here...

    My production logs are beautiful, save this annoying error. MS, please resolve ASAP, and dont just say "Do you have SP1 and the latest CU installed?"

    • Proposed as answer by Marli Butler Monday, March 18, 2013 9:48 AM
    Saturday, October 27, 2012 6:08 AM
  • Hi there,

    Still no solution?

    I have a new farm and getting this problem.

    Kind Regards,

    Marli

    Monday, November 19, 2012 9:06 AM
  • Same problem here.

    Brand new SharePoint 2010 virtual farm with an app server, a web server and a SQL Server.

    Brand new install, no other software running on the server.  Configured by Dell Services.

    Dell says it a "Microsoft problem".

    Monday, November 19, 2012 4:04 PM
  • Hi there,

    I've had this problem for a few weeks now.  Yesterday I tried a few things such as restarting the services and restarting the server and now my Search problem is gone.  I'm saying gone as I've tried these things before and it didn't work - so I don't know what the sollution was.

    Kind Regards,

    Marli

    • Proposed as answer by Marli Butler Friday, November 30, 2012 6:22 AM
    Tuesday, November 20, 2012 8:32 AM
  • Getting the same error in SharePoint 2010 and no other application\service is installed.


    Faiza

    Thursday, March 14, 2013 2:49 PM
  • Session "OfficeSearch14HealthSession" failed to start with the following error: 0xC0000035

    I'm seeing the same error logged at least once per day on all of my WFE and APP servers.  This has been going on since the farm was created in June of 2012.  Based on this thread and others like it, I've just been ignoring this error as I'm not seeing any real issues with the farm.  Everything is running smoothly.  Like those before me, I have to ask the same questions.

    1. Has anyone resolved this and know how they resolved it?
    2. Is it worth worrying about or should I continue to ignore it?

    Any useful help is appreciated.


    Colorless Green Ideas Sleep Furiously http://www.sharepointnerd.com

    Thursday, April 25, 2013 2:09 PM
  • This is also showing up on a new SharePoint Server 2013 RTM installation. 


    Tuesday, October 29, 2013 5:39 PM
  • ditto same here SP 2013 server, +PU +OCt CU.

    would love a solution

    Monday, December 16, 2013 2:16 PM