none
Windows Search Service Crashes on Windows Server 2012 R2

    Question

  • Hi, 

    I'm running Windows Search service on a Windows Server 2012 R2 (24GB RAM, 8-core proc). The index catalog has a little over 2 million items (files and folders indexed). 

    Every once in a while this service crashes, and either remains in limbo or automatically recovers and restarts the index from zero. I'm trying to find out information about what may be causing the crashes and about how to prevent them. Unfortunately, I don't seem to be able to find much about the Windows Search service on Windows Server 2012 R2. So anyone who may have input on this, please chip in.

    Additional info:
    - As mentioned above, the server OS is Windows Server 2012 R2. This is a physical server with 24GB RAM, 8-core proc and over 2TB of storage. 

    - This server acts as a DC and as a File Server. In addition to this and Windows Search service, there are no other major services running here

    - Symantec Endpoing protection is installed and running on this server, but I've made sure to exclude the Window Search database from SEP

    Here are some of the errors that are generated when the issue happens:

    The error below may show up in the event logs. If it shows up more than once, the indexing service has likely crashed and won't recover. 

    Log Name: System 
    Source: Service Control Manager 
    Date: 1/23/2015 3:32:15 PM 
    Event ID: 7011 
    Task Category: None 
    Level: Error 
    Keywords: Classic 
    User: N/A 
    Computer: myserver.mydomain.local 
    Description: 
    A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. 

    I attempted to stop the indexing service, but it didn't stop. I noticed though that the indexing GUI started responding as soon as the the service stop command failed. The indexing service seems to have picked up where it was (~300K items) and continued indexing. 

    Logs sequence: 

    Log Name: Application 
    Source: ESENT 
    Date: 1/23/2015 3:57:01 PM 
    Event ID: 102 
    Task Category: General 
    Level: Information 
    Keywords: Classic 
    User: N/A 
    Computer: myserver.mydomain.local 
    Description: 
    SearchIndexer (18232) Windows: The database engine (6.03.9600.0000) is starting a new instance (0).

    ====

     Log Name: Application 
    Source: ESENT 
    Date: 1/23/2015 3:57:01 PM 
    Event ID: 300 
    Task Category: Logging/Recovery 
    Level: Information 
    Keywords: Classic 
    User: N/A 
    Computer: myserver.mydomain.local  
    Description: 
    SearchIndexer (18232) Windows: The database engine is initiating recovery steps. 

    ====

    Log Name: Application 
    Source: ESENT 
    Date: 1/23/2015 3:57:01 PM 
    Event ID: 301 
    Task Category: Logging/Recovery 
    Level: Information 
    Keywords: Classic 
    User: N/A 
    Computer: myserver.mydomain.local 
    Description: 
    SearchIndexer (18232) Windows: The database engine has begun replaying logfile X:\IndexingService\Search\Data\Applications\Windows\edb0053D.log. 

    ====

    Log Name: Application 
    Source: ESENT 
    Date: 1/23/2015 3:57:01 PM 
    Event ID: 301 
    Task Category: Logging/Recovery 
    Level: Information 
    Keywords: Classic 
    User: N/A 
    Computer: myserver.mydomain.local 
    Description: 
    SearchIndexer (18232) Windows: The database engine has begun replaying logfile X:\IndexingService\Search\Data\Applications\Windows\edb0053E.log. 

    ====


    Log Name: Application 
    Source: ESENT 
    Date: 1/23/2015 3:57:02 PM 
    Event ID: 301 
    Task Category: Logging/Recovery 
    Level: Information 
    Keywords: Classic 
    User: N/A 
    Computer: myserver.mydomain.local
    Description: 
    SearchIndexer (18232) Windows: The database engine has begun replaying logfile X:\IndexingService\Search\Data\Applications\Windows\edb.log. 

    ====

    Log Name: Application 
    Source: ESENT 
    Date: 1/23/2015 3:57:02 PM 
    Event ID: 302 
    Task Category: Logging/Recovery 
    Level: Information 
    Keywords: Classic 
    User: N/A 
    Computer: myserver.mydomain.local
    Description: 
    SearchIndexer (18232) Windows: The database engine has successfully completed recovery steps. 

    ====

    Log Name: Application 
    Source: ESENT 
    Date: 1/23/2015 3:57:02 PM 
    Event ID: 105 
    Task Category: General 
    Level: Information 
    Keywords: Classic 
    User: N/A 
    Computer: myserver.mydomain.local 
    Description: 
    SearchIndexer (18232) Windows: The database engine started a new instance (0). (Time=1 seconds) 
      
    Internal Timing Sequence: [1] 0.000, [2] 0.000, [3] 0.000, [4] 0.032, [5] 1.046, [6] 0.094, [7] 0.000, [8] 0.000, [9] 0.000, [10] 0.000.

    ====

    Log Name: Application 
    Source: ESENT 
    Date: 1/23/2015 3:57:02 PM 
    Event ID: 326 
    Task Category: General 
    Level: Information 
    Keywords: Classic 
    User: N/A 
    Computer: myserver.mydomain.local 
    Description: 
    SearchIndexer (18232) Windows: The database engine attached a database (1, X:\IndexingService\Search\Data\Applications\Windows\Windows.edb). (Time=0 seconds) 
      
    Internal Timing Sequence: [1] 0.000, [2] 0.000, [3] 0.016, [4] 0.000, [5] 0.000, [6] 0.000, [7] 0.000, [8] 0.000, [9] 0.000, [10] 0.000, [11] 0.000, [12] 0.000. 
    Saved Cache: 1 0 

    Monday, January 26, 2015 4:11 PM

All replies