none
SharePoint Server 2010 Search error

    คำถาม

  • Hy,

    When I want to go the Content Sources section in the search admin service application to configure a new content source, i've the following error :
    "The search application '787388c1-53bf-45d0-af33-7e7d9fcf7647' on server 2K10RC0 did not finish loading. View the event logs on the affected server for more information.

    Troubleshoot issues with Microsoft SharePoint Foundation.

    Correlation ID: ce0efaa0-48db-4b12-8e40-c59dcdc0b5fa

    Date and Time: 2/15/2010 3:29:50 PM"

    In the Event Viewer, i've the following errors :
    "
    Log Name:      Application
    Source:        Microsoft-SharePoint Products-SharePoint Foundation
    Date:          2/15/2010 3:25:31 PM
    Event ID:      6398
    Task Category: Timer
    Level:         Critical
    Keywords:     
    User:          DEMOS\service_sharepoint
    Computer:      2k10rc0.demos.local
    Description:
    The Execute method of job definition Microsoft.Office.Server.Search.Administration.IndexingScheduleJobDefinition (ID aad65028-46d4-414b-bef4-2dc3ccc92bb6) threw an exception. More information is included below.

    The search application '787388c1-53bf-45d0-af33-7e7d9fcf7647' on server 2K10RC0 did not finish loading. View the event logs on the affected server for more information.
    Event Xml:
    <Event xmlns="
    http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-SharePoint Products-SharePoint Foundation" Guid="{6FB7E0CD-52E7-47DD-997A-241563931FC2}" />
        <EventID>6398</EventID>
        <Version>14</Version>
        <Level>1</Level>
        <Task>12</Task>
        <Opcode>0</Opcode>
        <Keywords>0x4000000000000000</Keywords>
        <TimeCreated SystemTime="2010-02-15T14:25:31.643959400Z" />
        <EventRecordID>16434</EventRecordID>
        <Correlation ActivityID="{D85E7D37-2C64-4FBD-8746-BB8E5621B307}" />
        <Execution ProcessID="1756" ThreadID="3736" />
        <Channel>Application</Channel>
        <Computer>2k10rc0.demos.local</Computer>
        <Security UserID="S-1-5-21-215455182-427695971-3249245710-1108" />
      </System>
      <EventData>
        <Data Name="string0">Microsoft.Office.Server.Search.Administration.IndexingScheduleJobDefinition</Data>
        <Data Name="string1">aad65028-46d4-414b-bef4-2dc3ccc92bb6</Data>
        <Data Name="string2">The search application '787388c1-53bf-45d0-af33-7e7d9fcf7647' on server 2K10RC0 did not finish loading. View the event logs on the affected server for more information.</Data>
      </EventData>
    </Event>"

    "Log Name:      Application
    Source:        Microsoft-SharePoint Products-SharePoint Server
    Date:          2/15/2010 3:25:59 PM
    Event ID:      6482
    Task Category: Shared Services
    Level:         Error
    Keywords:     
    User:          DEMOS\service_sharepoint
    Computer:      2k10rc0.demos.local
    Description:
    Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (48ad2dc8-dec4-42a3-b223-3902a86aba0b).

    Reason: The device is not ready. 

    Technical Support Details:
    System.IO.FileNotFoundException: The device is not ready. 
       at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
       at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)
    Event Xml:
    <Event xmlns="
    http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-SharePoint Products-SharePoint Server" Guid="{C33B4F2A-64E9-4B39-BD72-F0C2F27A619A}" />
        <EventID>6482</EventID>
        <Version>14</Version>
        <Level>2</Level>
        <Task>3</Task>
        <Opcode>0</Opcode>
        <Keywords>0x4000000000000000</Keywords>
        <TimeCreated SystemTime="2010-02-15T14:25:59.846850100Z" />
        <EventRecordID>16435</EventRecordID>
        <Correlation ActivityID="{425AF8DE-0163-4E72-B9AF-C86EFC61886E}" />
        <Execution ProcessID="1756" ThreadID="332" />
        <Channel>Application</Channel>
        <Computer>2k10rc0.demos.local</Computer>
        <Security UserID="S-1-5-21-215455182-427695971-3249245710-1108" />
      </System>
      <EventData>
        <Data Name="string0">Microsoft.Office.Server.Search.Administration.SearchServiceInstance</Data>
        <Data Name="string1">48ad2dc8-dec4-42a3-b223-3902a86aba0b</Data>
        <Data Name="string2">The device is not ready.  </Data>
        <Data Name="string3">System.IO.FileNotFoundException: The device is not ready. 
       at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
       at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)</Data>
      </EventData>
    </Event>"


    Any ideas ?

    Regards,

    FMD

    15 กุมภาพันธ์ 2553 14:47

คำตอบ

  • The search application for '{1}' on server {0} did not finish loading.” This is exactly the error message you will see when you go to manage the Search Service application in SharePoint 2010 Central Administration. This will occur when you follow the article “Setting Up the Development Environment for SharePoint 2010 on Windows Vista, Windows 7, and Windows Server 2008” and choose Windows Server 2008. You install all cumulative updates up to and including the SharePoint 2010 Dec 2012 CU. You then install Visual Studio plus SharePoint Designer and run Windows Update several times until there are no more updates.

    Now if you try searching using “Search This Site” on the front end web server you will get an error saying “The search request was unable to connect to the Search Service”. So you go to Central Admin and will see the “did not finish loading option” in the Search Service Application.

    When you examine the log files in the SharePoint hive you will find the solution: the Search service software is newer and not compatible with the search database. The way to fix this is to open PowerShell Commandlet (choose the import option):

    • Enter following command: psconfig -cmd upgrade inplace b2B wait

     

    Wait for the process to complete

    Go to Central Admin / Manage Service Applications / Search

    On screen”Central Administration Search Service Application: Search Administration”

    • The “Crawl Component” now shows status “Online”

     

    Extract from logs below:

                  Line 2531: 01/13/2012 09:36:21.44         OWSTIMER.EXE (0x0D28)                                 0x0BB4 SharePoint Server Search            Administration                              ewf2     High      Synchronization of the search component: 8829b926-5973-4d21-b04c-0856674fc0ef belonging to the search application Search Service Application has failed on the server SPSDEV because of compatibility breaking schema change(s) with one or more databases. For more details see below              0ea49fa1-ba5f-4859-9d48-327ba35e4646

                  Line 2533: 01/13/2012 09:36:21.45         OWSTIMER.EXE (0x0D28)                                 0x0BB4 SharePoint Server Search            Administration                              ewf4     Critical  The synchronization operation of the search component: 8829b926-5973-4d21-b04c-0856674fc0ef associated to the search application: Search Service Application on server: SPSDEV has failed. The component version is not compatible with the search database: Search_Service_Application_CrawlStoreDB_98a21940ab3a421981c861153e12e104 on server: SPSDEV. The possible cause for this failure is The database schema version is less than the minimum backwards compatibility schema version that is supported for this component. To resolve this problem upgrade this database..              0ea49fa1-ba5f-4859-9d48-327ba35e4646

    Wim De Groote

    wimdg@hotmail.com                

     

     

     

    • เสนอเป็นคำตอบโดย Sventje_1 20 มีนาคม 2555 8:25
    • ทำเครื่องหมายเป็นคำตอบโดย Cornelius J. van DykMVP, Editor 26 มีนาคม 2556 18:37
    16 มกราคม 2555 22:15
  • Hi all,

    For solving this problem:

    Get-SPEnterpriseSearchServiceApplication -Identity <application name>

    In your case the <application name> it's same as "Search Service Application".

    After you retrieved the GUID in the ID field from the response to the above command in PowerShell, the STSADM command worked:

    STSADM -o deleteconfigurationobject -id <GUID>

    Remove the Search* databases, recreate the Search Service Application and reconfigure it.

    Good work.

    Raffa!!!

    • เสนอเป็นคำตอบโดย Matteo Fazioli 5 กรกฎาคม 2554 9:02
    • ทำเครื่องหมายเป็นคำตอบโดย Cornelius J. van DykMVP, Editor 26 มีนาคม 2556 18:37
    26 มิถุนายน 2554 21:26

ตอบทั้งหมด

  • Hi,

    I am having the same problem as well. Seems not to be an isolated issue. Will post if I get to solve it.

    Joe

    25 มีนาคม 2553 8:44
  • What does the event log /ULS log on the machine 2k10rc0.demos.local says?  Is the search service on the machine 2k10rc0.demos.local running fine or running into some sort of issues?

    Arun

    26 มีนาคม 2553 21:52
  • Similar problem:

    Event ID: 6398

    User: NETWORK SERVICE

    Task category: Timer

    The Execute method of job definition Microsoft.Office.Server.Search.Administration.IndexingScheduleJobDefinition (ID d7e515c7-9ec6-42cc-a4ce-b67f67fb06be) threw an exception. More information is included below.

    The search application '3cb67978-7fd0-4a74-a9c6-1becc93da9d6' on server SPF10V1 did not finish loading. View the event logs on the affected server for more information.

     

    Any idea?

    Charles

    1 กรกฎาคม 2553 9:19
  • I had installed the SearchServerExpress 2010 on my SharePoint server.

    I saw 2 services started in the Windows 2008 services console:

    1. SharePoint Foundation Search V4
    2. SharePoint Server Search 14

    It seems that the second one replaces now the first one. So I stopped the "SharePoint Foundation Search V4" services and it works now.


    Charles
    • เสนอเป็นคำตอบโดย Stephen Gorsch, MCTS 13 กรกฎาคม 2553 13:17
    1 กรกฎาคม 2553 15:12
  • I also have this same error in my event logs, and my Foundation Search V4 service is not running and is disabled (as configured automatically). There may be other causes of this problem.
    29 พฤศจิกายน 2553 22:21
  • Does anyone know a status on this issue. I have periodically the same issue on multiple SharePoint 2010 Farms. Can't find a consistant answer anywhere.
    18 มีนาคม 2554 12:30
  • I am also witnessing this problem as I am attempting to learn about SharePoint (new to it). While I do not have a solution, what I suspect about my instance, which is a virtual machine in VirtualBox, was this probably started surfacing after VirtualBox.exe itself crashed while shutting down the VM one day. I cannot guarantee that is the 100% cause though.

    On suggestion from other sources, I deleted the only standing Search Service Application, and attempted an Index Reset for the search service. But that ended up in error.

    Log Name:      Application
    Source:        Microsoft-SharePoint Products-SharePoint Server Search
    Date:          3/30/2011 5:53:04 PM
    Event ID:      74
    Task Category: Content Index Server
    Level:         Error
    Keywords:     
    User:          SYSTEM
    Computer:      WIN-NG0HQ5HJR6U
    Description:
    Component: 373c2f03-0d80-42ac-930e-892b76a6c7d8
     An index corruption of type WidSetFormat was detected in catalog Portal_Content. Stack trace is
         tquery offset=0x0000000000034FEC (0x000007FED8A44FEC)
         tquery offset=0x000000000001E311 (0x000007FED8A2E311)
         tquery offset=0x00000000000ED3E4 (0x000007FED8AFD3E4)
         tquery offset=0x000000000012BC00 (0x000007FED8B3BC00)
         tquery offset=0x000000000012C3C3 (0x000007FED8B3C3C3)
         tquery offset=0x0000000000124326 (0x000007FED8B34326)
         tquery offset=0x0000000000124BF7 (0x000007FED8B34BF7)
         tquery offset=0x0000000000126821 (0x000007FED8B36821)

    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-SharePoint Products-SharePoint Server Search" Guid="{C8263AFE-83A5-448C-878C-1E5F5D1C4252}" />
        <EventID>74</EventID>
        <Version>14</Version>
        <Level>2</Level>
        <Task>138</Task>
        <Opcode>0</Opcode>
        <Keywords>0x4000000000000000</Keywords>
        <TimeCreated SystemTime="2011-03-30T09:53:04.042634000Z" />
        <EventRecordID>13803</EventRecordID>
        <Correlation />
        <Execution ProcessID="2088" ThreadID="4840" />
        <Channel>Application</Channel>
        <Computer>WIN-NG0HQ5HJR6U</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="string0">Component: 373c2f03-0d80-42ac-930e-892b76a6c7d8
    </Data>
        <Data Name="string1">WidSetFormat</Data>
        <Data Name="string2">Portal_Content</Data>
        <Data Name="string3">
         tquery offset=0x0000000000034FEC (0x000007FED8A44FEC)
         tquery offset=0x000000000001E311 (0x000007FED8A2E311)
         tquery offset=0x00000000000ED3E4 (0x000007FED8AFD3E4)
         tquery offset=0x000000000012BC00 (0x000007FED8B3BC00)
         tquery offset=0x000000000012C3C3 (0x000007FED8B3C3C3)
         tquery offset=0x0000000000124326 (0x000007FED8B34326)
         tquery offset=0x0000000000124BF7 (0x000007FED8B34BF7)
         tquery offset=0x0000000000126821 (0x000007FED8B36821)
    </Data>
      </EventData>
    </Event>

     

    Log Name:      Application
    Source:        Microsoft-SharePoint Products-SharePoint Server Search
    Date:          3/30/2011 5:53:04 PM
    Event ID:      71
    Task Category: Content Index Server
    Level:         Error
    Keywords:     
    User:          SYSTEM
    Computer:      WIN-NG0HQ5HJR6U
    Description:
    Content index on Component: 373c2f03-0d80-42ac-930e-892b76a6c7d8
     could not be initialized. Error Portal_Content.The content index is corrupt.   0xc0041800
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-SharePoint Products-SharePoint Server Search" Guid="{C8263AFE-83A5-448C-878C-1E5F5D1C4252}" />
        <EventID>71</EventID>
        <Version>14</Version>
        <Level>2</Level>
        <Task>138</Task>
        <Opcode>0</Opcode>
        <Keywords>0x4000000000000000</Keywords>
        <TimeCreated SystemTime="2011-03-30T09:53:04.042634000Z" />
        <EventRecordID>13804</EventRecordID>
        <Correlation />
        <Execution ProcessID="2088" ThreadID="4840" />
        <Channel>Application</Channel>
        <Computer>WIN-NG0HQ5HJR6U</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="string0">Component: 373c2f03-0d80-42ac-930e-892b76a6c7d8
    </Data>
        <Data Name="string1">Portal_Content</Data>
        <Data Name="string2">The content index is corrupt.   0xc0041800</Data>
      </EventData>
    </Event>

     

    Log Name:      Application
    Source:        Microsoft-SharePoint Products-SharePoint Server Search
    Date:          3/30/2011 5:53:04 PM
    Event ID:      12
    Task Category: Gatherer
    Level:         Error
    Keywords:     
    User:          SYSTEM
    Computer:      WIN-NG0HQ5HJR6U
    Description:
    The plug-in in OSearch14.Indexer.1 cannot be initialized.

    Context: Application '373c2f03-0d80-42ac-930e-892b76a6c7d8', Catalog 'Portal_Content'

    Details:
      (0xc0041800)
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-SharePoint Products-SharePoint Server Search" Guid="{C8263AFE-83A5-448C-878C-1E5F5D1C4252}" />
        <EventID>12</EventID>
        <Version>14</Version>
        <Level>2</Level>
        <Task>137</Task>
        <Opcode>0</Opcode>
        <Keywords>0x4000000000000000</Keywords>
        <TimeCreated SystemTime="2011-03-30T09:53:04.042634000Z" />
        <EventRecordID>13805</EventRecordID>
        <Correlation />
        <Execution ProcessID="2088" ThreadID="4840" />
        <Channel>Application</Channel>
        <Computer>WIN-NG0HQ5HJR6U</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="string0">OSearch14.Indexer.1</Data>
        <Data Name="string1">

    Context: Application '373c2f03-0d80-42ac-930e-892b76a6c7d8', Catalog 'Portal_Content'

    Details:
      (0xc0041800)</Data>
      </EventData>
    </Event>

     

    Log Name:      Application
    Source:        Microsoft-SharePoint Products-SharePoint Server Search
    Date:          3/30/2011 5:53:04 PM
    Event ID:      11
    Task Category: Gatherer
    Level:         Error
    Keywords:     
    User:          SYSTEM
    Computer:      WIN-NG0HQ5HJR6U
    Description:
    The gatherer object cannot be initialized.

    Context: Application 'Search_Service_Application', Catalog 'Portal_Content'

    Details:
      (0xc0041800)
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-SharePoint Products-SharePoint Server Search" Guid="{C8263AFE-83A5-448C-878C-1E5F5D1C4252}" />
        <EventID>11</EventID>
        <Version>14</Version>
        <Level>2</Level>
        <Task>137</Task>
        <Opcode>0</Opcode>
        <Keywords>0x4000000000000000</Keywords>
        <TimeCreated SystemTime="2011-03-30T09:53:04.058259000Z" />
        <EventRecordID>13806</EventRecordID>
        <Correlation />
        <Execution ProcessID="2088" ThreadID="4840" />
        <Channel>Application</Channel>
        <Computer>WIN-NG0HQ5HJR6U</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="string0">

    Context: Application 'Search_Service_Application', Catalog 'Portal_Content'

    Details:
      (0xc0041800)</Data>
      </EventData>
    </Event>

     

    Log Name:      Application
    Source:        Microsoft-SharePoint Products-SharePoint Server Search
    Date:          3/30/2011 5:53:04 PM
    Event ID:      25
    Task Category: Gatherer
    Level:         Error
    Keywords:     
    User:          SYSTEM
    Computer:      WIN-NG0HQ5HJR6U
    Description:
    The application cannot be initialized.

    Context: Application 'Search_Service_Application'

    Details:
      (0xc0041800)
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-SharePoint Products-SharePoint Server Search" Guid="{C8263AFE-83A5-448C-878C-1E5F5D1C4252}" />
        <EventID>25</EventID>
        <Version>14</Version>
        <Level>2</Level>
        <Task>137</Task>
        <Opcode>0</Opcode>
        <Keywords>0x4000000000000000</Keywords>
        <TimeCreated SystemTime="2011-03-30T09:53:04.058259000Z" />
        <EventRecordID>13807</EventRecordID>
        <Correlation />
        <Execution ProcessID="2088" ThreadID="4840" />
        <Channel>Application</Channel>
        <Computer>WIN-NG0HQ5HJR6U</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="string0">

    Context: Application 'Search_Service_Application'

    Details:
      (0xc0041800)</Data>
      </EventData>
    </Event>

    It looks like the "index" is corrupted but do not know how to clean up this index or where to find it.


    The melody of logic will always play out the truth. ~ Narumi Ayumu, Spiral
    30 มีนาคม 2554 9:57
  •  An index corruption of type WidSetFormat was detected in catalog Portal_Content.

    Content index on Component: 373c2f03-0d80-42ac-930e-892b76a6c7d8
     could not be initialized. Error Portal_Content.The content index is corrupt.

    The plug-in in OSearch14.Indexer.1 cannot be initialized.

    Context: Application '373c2f03-0d80-42ac-930e-892b76a6c7d8', Catalog 'Portal_Content'

    The gatherer object cannot be initialized.

    Context: Application 'Search_Service_Application', Catalog 'Portal_Content'

    Ok, if you have this "portal_content" errors like mine, then it is probably SharePoint search service unable to delete/overwrite the corrupted files in the Indexer folder located at (GUID may differ)

    C:\Program Files\Microsoft Office Servers\14.0\Data\Office Server\Applications\373c2f03-0d80-42ac-930e-892b76a6c7d8\Projects\Portal_Content

    More report here http://icelava.net/forums/thread/7410.aspx


    The melody of logic will always play out the truth. ~ Narumi Ayumu, Spiral
    30 มีนาคม 2554 12:11
  • I'm receiving this error after that I have configured Automatic password change about Serach service account.

    I think that this issue is connected with this account that is blocked :(


    Fabio Alivernini
    16 พฤษภาคม 2554 15:08
  • Hi all,

    For solving this problem:

    Get-SPEnterpriseSearchServiceApplication -Identity <application name>

    In your case the <application name> it's same as "Search Service Application".

    After you retrieved the GUID in the ID field from the response to the above command in PowerShell, the STSADM command worked:

    STSADM -o deleteconfigurationobject -id <GUID>

    Remove the Search* databases, recreate the Search Service Application and reconfigure it.

    Good work.

    Raffa!!!

    • เสนอเป็นคำตอบโดย Matteo Fazioli 5 กรกฎาคม 2554 9:02
    • ทำเครื่องหมายเป็นคำตอบโดย Cornelius J. van DykMVP, Editor 26 มีนาคม 2556 18:37
    26 มิถุนายน 2554 21:26
  • You people never cease to amaze me... Just delete it when it doesn't work. That's fine unless you have a 5,000,000 document index.
    Todd
    28 ตุลาคม 2554 14:57
  • If you have a backup from your environment, you can follow

    http://technet.microsoft.com/en-us/library/ee748654.aspx


    http://SharePoint4Arab.blogspot.com
    28 ตุลาคม 2554 18:17
  • In My case (Sharepoint 2010 and FAST 2010), even after re-creation I've still got the same problem After taking the search service account from administrators  ( because I was creating schedule jobs with admin priveliges for the search account.)

    So after re-creation the SSA and not creating crawl scheduling everithing seemed to work.

    Now I had only the schedule creating problem.

    To solve this, Crawl Schedule creations, I followed the KB http://support.microsoft.com/kb/926959  suggestion  from Microsoft Support.

    After geaving access (Read and write)  to c:\windows\tasks to the WSS_WPG group I was able to create Schedule.

    I guess that if i've not recreated and followed this KB would work for me.

    Hope it helps someone

    7 ธันวาคม 2554 13:08
  • The search application for '{1}' on server {0} did not finish loading.” This is exactly the error message you will see when you go to manage the Search Service application in SharePoint 2010 Central Administration. This will occur when you follow the article “Setting Up the Development Environment for SharePoint 2010 on Windows Vista, Windows 7, and Windows Server 2008” and choose Windows Server 2008. You install all cumulative updates up to and including the SharePoint 2010 Dec 2012 CU. You then install Visual Studio plus SharePoint Designer and run Windows Update several times until there are no more updates.

    Now if you try searching using “Search This Site” on the front end web server you will get an error saying “The search request was unable to connect to the Search Service”. So you go to Central Admin and will see the “did not finish loading option” in the Search Service Application.

    When you examine the log files in the SharePoint hive you will find the solution: the Search service software is newer and not compatible with the search database. The way to fix this is to open PowerShell Commandlet (choose the import option):

    • Enter following command: psconfig -cmd upgrade inplace b2B wait

     

    Wait for the process to complete

    Go to Central Admin / Manage Service Applications / Search

    On screen”Central Administration Search Service Application: Search Administration”

    • The “Crawl Component” now shows status “Online”

     

    Extract from logs below:

                  Line 2531: 01/13/2012 09:36:21.44         OWSTIMER.EXE (0x0D28)                                 0x0BB4 SharePoint Server Search            Administration                              ewf2     High      Synchronization of the search component: 8829b926-5973-4d21-b04c-0856674fc0ef belonging to the search application Search Service Application has failed on the server SPSDEV because of compatibility breaking schema change(s) with one or more databases. For more details see below              0ea49fa1-ba5f-4859-9d48-327ba35e4646

                  Line 2533: 01/13/2012 09:36:21.45         OWSTIMER.EXE (0x0D28)                                 0x0BB4 SharePoint Server Search            Administration                              ewf4     Critical  The synchronization operation of the search component: 8829b926-5973-4d21-b04c-0856674fc0ef associated to the search application: Search Service Application on server: SPSDEV has failed. The component version is not compatible with the search database: Search_Service_Application_CrawlStoreDB_98a21940ab3a421981c861153e12e104 on server: SPSDEV. The possible cause for this failure is The database schema version is less than the minimum backwards compatibility schema version that is supported for this component. To resolve this problem upgrade this database..              0ea49fa1-ba5f-4859-9d48-327ba35e4646

    Wim De Groote

    wimdg@hotmail.com                

     

     

     

    • เสนอเป็นคำตอบโดย Sventje_1 20 มีนาคม 2555 8:25
    • ทำเครื่องหมายเป็นคำตอบโดย Cornelius J. van DykMVP, Editor 26 มีนาคม 2556 18:37
    16 มกราคม 2555 22:15
  • Thank you Wim De Groote! Your solution helped me. I'm curious as to why these updates were released in such manner.  What happen to QA?
    25 เมษายน 2555 16:22
  • Thank you Wim, this was on the money.
    26 กรกฎาคม 2555 22:44
  • Ok.  After reading the post I did NOT want to delete my Search Service Application.  I tried all the suggestions offered by all in the forum.  Thanks.  

    My solution:  I checked my SQL Server and looked at the databases.  I noticed that the Search_Service_Application_CrawlStoreDB was not in production.  It did not have the + sign to allow me to expand the database. The same was true for WSS_UsageApplication.  I checked my night backups and noticed that the backups for those databases stopped on 11/1.  I restored the databases in a test environment to verify that all content was there and it was.  

    So I took both databases offline and then brought them back online.  The + sign then reappeared on both databases.  I did an IISRESET on my APP Server just to be sure everything would work correctly.  

    After a period of time the Search Service Application picked up the database and continued its nightly full backup. 

    Thanks. 

    9 พฤศจิกายน 2555 17:48
  • I had the same error on my search server express edition 2010 server. My index is located on a separate partition and sharepoint lost the connection to it due the disk went offline. After taking back online, starting the configuration wizard and restarting the machine (do not know if that was necessary) search worked again.

    Hope that helps! Andreas

    • เสนอเป็นคำตอบโดย Andreas Kranister 27 พฤศจิกายน 2555 13:08
    27 พฤศจิกายน 2555 13:07