none
Search Service Application broken - event viewer 6482 - the device is not ready - after windows updates RRS feed

  • Question

  • Our Serach service application is still running, but any new documents are not being added to the search index.

    When clicking on anything within search administration, the page dies with a correlation error. the event viewer is logging these errors

    ""Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (4f27a523-441d-4501-9def-217dbc9ac287).

    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)""

    and

    ""

    The Execute method of job definition Microsoft.Office.Server.Search.Administration.IndexingScheduleJobDefinition (ID d25e54cc-8c66-4ab5-864d-5a2befbddc38) threw an exception. More information is included below.

    The search application '4fc3384b-e9df-4698-90cf-74bce1bedfee' on server UK1-INF-xxx-xxx did not finish loading. View the event logs on the affected server for more information.""

    We have stopped and started the services, also rebooted all servers in the farm, but at a loss on how to resolve this issue.

    any help would be great.

    The powershell commands show the search application to be online.

    Kind Regards Paul

    Wednesday, December 23, 2015 5:04 PM

Answers

  • Hi,

    According to the logs you provide, it seems that the error is caused by the search service instance.

    Please run the command below to get the ID of the search service instance.

    Get-SPEnterpriseSearchServiceInstance –Local

    Then run the command below to start the search service instance depend on the ID:

    Start-SPEnterpriseSearchServiceInstance

    Best Regards,

    Dean Wang


    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.


    Thursday, December 24, 2015 10:11 AM
    Moderator

All replies

  • Are any SharePoint updates installed along with windows updates?

    Check the status of Farm under System settings -> Servers in the farm -> Farm information and make sure that no server requires Update.



    Wednesday, December 23, 2015 5:29 PM
  • Also check view installed updated through control panel and see if anything related to SharePoint has sneaked in. 

    sachin

    Wednesday, December 23, 2015 5:47 PM
  • Hi,

    According to the logs you provide, it seems that the error is caused by the search service instance.

    Please run the command below to get the ID of the search service instance.

    Get-SPEnterpriseSearchServiceInstance –Local

    Then run the command below to start the search service instance depend on the ID:

    Start-SPEnterpriseSearchServiceInstance

    Best Regards,

    Dean Wang


    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.


    Thursday, December 24, 2015 10:11 AM
    Moderator