none
SharePoint 2010 search Crawl Log Error

    Question

  • Hi All,

    I getting  Serach Crawl log error

    Central Administration  -> Application Management -> Manage Service application

    -> Search Service Application  -> Crawling (left side navigation) -> Crawl Log ->

    I am getting this error:

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

    Error

    Retrieving the COM class factory for component with CLSID {0FF1CE14-0005-0000-0000-000000000000} failed due to the following error: 8007042d.


    Troubleshoot issues with Microsoft SharePoint Foundation.

    Correlation ID: 444cbb09-5cae-48e4-925d-aff796a03855

    Date and Time: 6/21/2012 3:00:50 PM

    <-  Go back to site

    -----------------------------------------------------------------------------------------------------------
    Thanks for Advance

    GAK Austin.

    jeudi 21 juin 2012 20:30

Réponses

  • Go to services.msc from command prompt..start (or restart) the service "office sharepoint server search" .  Give IIS an IISReset for good measure and see if the error persists.

    If that fails, then the issue could be caused by lack of permission on one of the service accounts. To see the real error, run the Windows Event Viewer. Click on Run and then type Eventvwr. This particular error fell under the System log. The error was described as:

    DCOM had the error "The service did not start due to a logon failur attempting to start the service OSearch with arguments".

    The fix was to start Component Services (Under Administration Tools). Under DCOM config, you will find the OSearch component. First find out what the credentials are by using the Identity tab. If the Service is using a system account, you can either elevate the system account or supply a user with significant rights.

    Quick troubleshooting tips:
    1. Verify the username and password in the Central Administration App Pool (right click->Properties->Identity[tab])
    2. Verify that any services that are running relating to IIS or WSS/MOSS are using valid usernames and passwords.
    3. Verify that any services running for SQL Server are using the right username and password.
    4. Verify that the account in question has the proper access to the sharepoint databases.

    The moral of the story is changing service account passwords wreaks havoc on your SharePoint environment. If you are going to change passwords, there is really only one way to do it.


    Keith Tuomi | Twitter: @itgroove_keith | Blog: http://yalla.itgroove.net

    Please click "Propose As Answer" if a post solves your problem or "Vote As Helpful" if a post has been useful to you.

    vendredi 22 juin 2012 15:51

Toutes les réponses

  • Can you look under Services in your machine and see if the 'SharePoint Server Search 14' service is stopped?
    jeudi 21 juin 2012 20:43
  • no...
    vendredi 22 juin 2012 15:02
  • Go to services.msc from command prompt..start (or restart) the service "office sharepoint server search" .  Give IIS an IISReset for good measure and see if the error persists.

    If that fails, then the issue could be caused by lack of permission on one of the service accounts. To see the real error, run the Windows Event Viewer. Click on Run and then type Eventvwr. This particular error fell under the System log. The error was described as:

    DCOM had the error "The service did not start due to a logon failur attempting to start the service OSearch with arguments".

    The fix was to start Component Services (Under Administration Tools). Under DCOM config, you will find the OSearch component. First find out what the credentials are by using the Identity tab. If the Service is using a system account, you can either elevate the system account or supply a user with significant rights.

    Quick troubleshooting tips:
    1. Verify the username and password in the Central Administration App Pool (right click->Properties->Identity[tab])
    2. Verify that any services that are running relating to IIS or WSS/MOSS are using valid usernames and passwords.
    3. Verify that any services running for SQL Server are using the right username and password.
    4. Verify that the account in question has the proper access to the sharepoint databases.

    The moral of the story is changing service account passwords wreaks havoc on your SharePoint environment. If you are going to change passwords, there is really only one way to do it.


    Keith Tuomi | Twitter: @itgroove_keith | Blog: http://yalla.itgroove.net

    Please click "Propose As Answer" if a post solves your problem or "Vote As Helpful" if a post has been useful to you.

    vendredi 22 juin 2012 15:51
  • Please go to the ULS log and search the Correlation ID: 444cbb09-5cae-48e4-925d-aff796a03855 and provide the exact error message!
    vendredi 22 juin 2012 16:19