locked
Faulting application name: mssearch.exe RRS feed

  • Question

  • I have SharePoint 2007 SP2 installed on Windows Server 2008 R2. Yesterday at about 1am the server underwent a scheduled reboot and when it cam back up the following errors started appearing in the Windows error log in 1 minute intervals:

    --- ERRORS START

    The system exception c0000005 occurred, and will be handled.  If this causes problems, contact Microsoft Product Support Services and include the stack trace in the event. 0000000069F6C5A7.

    ---

    Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (cbd31aab-a3b1-48ff-96d2-d221ba995a3b).

    Reason: The remote procedure call failed. (Exception from HRESULT: 0x800706BE)

    Techinal Support Details:
    System.Runtime.InteropServices.COMException (0x800706BE): The remote procedure call failed. (Exception from HRESULT: 0x800706BE)
       at Microsoft.Office.Server.Search.Administration.MSSITLB.IGatherManagerAdmin3.get_ConfigurationVersion()
       at Microsoft.Office.Server.Search.Administration.Gatherer.ProvisionGlobalProperties()
       at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
       at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)

    ---

    The Execute method of job definition Microsoft.Office.Server.Search.Administration.IndexingScheduleJobDefinition (ID b779d60a-5b06-41a5-89f1-794e601db72e) threw an exception. More information is included below.

    The remote procedure call failed. (Exception from HRESULT: 0x800706BE)

    ---

    Faulting application name: mssearch.exe, version: 12.0.6600.1000, time stamp: 0x4ddea3ba
    Faulting module name: tquery.dll, version: 12.0.6604.1000, time stamp: 0x4e12046a
    Exception code: 0xc0000005
    Fault offset: 0x000000000022c5a7
    Faulting process id: 0xcc8
    Faulting application start time: 0x01cdfd4262aa66a5
    Faulting application path: C:\Program Files\Microsoft Office Servers\12.0\Bin\mssearch.exe
    Faulting module path: C:\PROGRA~1\MICROS~1\12.0\Bin\tquery.dll
    Report Id: a14ee91c-6935-11e2-9451-0050569d0b8c

    --- ERRORS END

    I have stopped Office SharePoint Server Search and Windows SharePoint Services Help Search, rebooted, then started them again. Google has not been my friend today.

    Tuesday, January 29, 2013 7:12 AM

Answers

  • The search service was failing to start. This meant that it wasn't indexing or responding to queries. Eventually we just restored a backup of the VM and everything worked, though we have no idea what actually went wrong.

    • Marked as answer by David Orme Monday, February 4, 2013 6:57 AM
    Monday, February 4, 2013 6:55 AM

All replies

  • Hi,

    Have you checked that whether the search service application works as expected?

    You can Start the SharePoint search service and open the Search service application in Central Administration. You can search in one of your site collection and see whether there are results. If there are any error when you search, you should provide the error log about that error.

    Try the powershell command to stop and start the search service:

    To start the Office SharePoint Server Search service (Osearch), use the following syntax:stsadm -o osearch -action start

    To stop the Office SharePoint Server Search service (Osearch), use the following syntax:stsadm -o osearch -action stop[-f]

    Thanks,

    Entan Ming

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contacttnmff@microsoft.com.


    Entan Ming
    TechNet Community Support

    Wednesday, January 30, 2013 7:08 AM
    Moderator
  • The search service was failing to start. This meant that it wasn't indexing or responding to queries. Eventually we just restored a backup of the VM and everything worked, though we have no idea what actually went wrong.

    • Marked as answer by David Orme Monday, February 4, 2013 6:57 AM
    Monday, February 4, 2013 6:55 AM