none
"Object Shared Search Index failed in event OnPrepareBackup" when doing Central Admin's Full farm backup RRS feed

  • Question

  • I'm using Central Admin > Operations to Perform a Backup (Full backup of the farm)

     

    But it fails with this error:

    Object Shared Search Index failed in event OnPrepareBackup. For more information, see the error log located in the backup directory. KeyNotFoundException: Object a4341e0c-60fb-4243-8bb3-b9d0ab4bb66b not found.

     

    If no other suggestions, will try rebuilding indexes. 

     

    Other errors that are probably related to the error above:

    Error On SharedServices1, Search Settings: The search service is currently offline. 

    Error On SharedServices1, User Profiles and Properties: An error has occurred while accessing the SQL Server database or the Office SharePoint Server Search service

    I have been working with MS Support on these two errors and decided we need to restore from backup, but that will have to wait since I'm going out of town.  I have backup of the content database but the automated backup backs up the farm.  I want to make sure I can restore from that.

     

    MOSS

    Live, Production

    1 WFE + 1 SQL2005 db server

     SharedServices1 (Default)  
     *  Default Web Site 
     *  PersonalSites - 8081 
     *  SharedServices - 8080 (Administration site host)

     

    Thanks for any suggestions.

    • Edited by Mike Walsh FIN Saturday, January 3, 2009 2:11 PM attempt to improve Subject
    Wednesday, October 3, 2007 4:04 AM

All replies

  • Hi, im getting the same error when trying to do a backup before i install KB960011.

    Did you manage to get a solution?

    Thanks

    Sunday, January 25, 2009 3:11 PM
  • I found this:

    SharePoint bug: extending web application breaks the backup process

    http://blogs.objectsharp.com/cs/blogs/max/

    Is it a step in the right direction?

    There appears to be a bug in SharePoint (WSS or MOSS) that breaks the backup process after extending a web application. If you need to add host headers or load balancing URL to your SharePoint web application, the only way to do that is to extend your web application (SharePoint Central Administration >> Application Management >> Create or extend Web application >> Extend an existing Web application). Even though extending web application allows you to add load balancing URL and host headers, for some reason, it breaks the backup for all site collections and sites that use that web application. You could still backup SharePoint site collection using stsadm.exe command (stsadm.exe –o backup –url http://damagedWebApp/ -filename backup_damaged_webapp.bak), but built-in SharePoint backup through Central Administration wouldn't work. You will start receiving an error (Error: Object SharePoint - 80 failed in event OnPrepareBackup. For more information, see the error log located in the backup directory. KeyNotFoundException: The given key was not present in the dictionary) every time you attempt to backup modified web application using Central Administration website.

    To get backup process working again you will have to perform the following steps:

    1. Backup your web application database through Microsoft SQL Server Management Studio!!!
    2. Detach the content database from the web application:
      1. Go to SharePoint Central Administration >> Application Management >> Content Databases
      2. Make sure to select damaged web application form the drop down list, otherwise you will messing with the wrong web application
      3. Click on the content database used by damaged web application
      4. Check "Remove content database" and click OK (ignore the warning). Removing the content database does not delete the database; it only removes the association of the database with the Web application. This action is analogous to detaching a database in SQL Server in that the content of the database remains intact.
    3. Delete the web application (remove SharePoint from it):
      1. Go to SharePoint Central Administration >> Application Management >> Delete Web Application
      2. Make sure to select damaged web application form the drop down list
      3. Leave "Delete Content Databases" and "Delete IIS Websites" options set to "No". You can always remove them later, right now we are only interested in removing SharePoint references to the damaged web application
    4. Create a new web application with the appropriate settings for host header, load balancing URL and so on:
      1. Go to SharePoint Central Administration >> Application Management >> Create or extend Web application >> Create new Web application
      2. Configure new web application settings. Don't forget host headers, new website and port settings, and load balancing URL (as needed) and click OK
    5. Remove content database of the newly created web application by running
      stsadm.exe -o deletecontentdb -url http://newwebapplication:port -databasename NEW_WEBAPP_DB
      Go to http://technet.microsoft.com/en-us/library/cc262449.aspx for more information on deletecontentdb operation of stsadm.exe command
    6. Attach the existing database to the new web application by running
      stsadm.exe -o addcontentdb -url http://newwebapplication:port -databasename OLD_WEBAPP_DB
      Go to http://technet.microsoft.com/en-us/library/cc263422.aspx for more information on addcontentdb operation of stsadm.exe command
    7. Make sure that host headers in IIS as well as Alternate Access Mapping is set properly and try running the full SharePoint backup again through Central Administration.

    After those steps you will probably also have to configure search server setting for your content database (SharePoint Central Administration >> Application Management >> Content Databases >> Select Search Server from drop-down list) and get full crawl running to make sure that your search is up-to-date and working properly.

    Now that your backup is running again, it should safe to remove:

    • the database that was created with new web application (see Step 5 above)
    • the website used by damaged web application (assuming you don't need this website for anything else)
    Sunday, January 25, 2009 3:14 PM
  • And guess i must post the errors im getting:

     

    In app log:

    Event Type: Error
    Event Source: Office SharePoint Server
    Event Category: Office Server Shared Services
    Event ID: 6482
    Date:  2009/01/25
    Time:  06:01:07 PM
    User:  N/A
    Computer: Server1
    Description:
    Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (1480cfc9-c77e-4063-9d48-c952957b7026).

    Reason: Object 7a8d48ae-9509-470e-a263-b67152aa1a34 not found.

    Techinal Support Details:
    System.Collections.Generic.KeyNotFoundException: Object 7a8d48ae-9509-470e-a263-b67152aa1a34 not found.
       at Microsoft.Office.Server.Search.Administration.SearchApi.get_App()
       at Microsoft.Office.Server.Search.Administration.SearchApi.SetUsersPermittedToQuery(String[] userNames, Boolean force)
       at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
       at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)

    In backup log:

    Error: Object Shared Search Index failed in event OnBackupComplete. For more information, see the error log located in the backup directory.
     Object Shared Search Index failed in event OnPrepareBackup. For more information, see the error log located in the backup directory.
     UpdatedConcurrencyException: The program attempted to update an object that was updated by another user.
     UpdatedConcurrencyException: The program attempted to update an object that was updated by another user.

    In Older backup log:

     

    [1/24/2009 5:22:10 AM]: Error: Object Shared Search Index failed in event OnPrepareBackup. For more information, see the error log located in the backup directory.

                    KeyNotFoundException: Object 7a8d48ae-9509-470e-a263-b67152aa1a34 not found.

    [1/24/2009 5:22:10 AM]: Debug:    at Microsoft.Office.Server.Search.Administration.SearchApi.get_App()

       at Microsoft.Office.Server.Search.Administration.SearchApi.get_Project()

       at Microsoft.Office.Server.Search.Administration.SearchApi.CatalogResumeCrawlInternal(Int32 reason)

       at Microsoft.Office.Server.Search.Administration.SearchApi.<>c__DisplayClass104.<CatalogResumeCrawlRequest>b__103()

       at Microsoft.Office.Server.Search.Administration.SearchApi.RunVoidOnServer(VoidCodeToRun remoteCode, VoidCodeToRun localCode, Boolean useCurrentSecurityContext, Int32 versionIn)

    [1/24/2009 5:22:10 AM]: Verbose: Starting object: SharedServices9_Search_DB.

     

    Sunday, January 25, 2009 5:19 PM
  • you migt want to try resetting your search indext and give it a try. SSp-> Search settings -> reset index.  Then perfrom a full crawl. 

    HK

    Sunday, January 25, 2009 9:39 PM
  • Ok, i have reset the Index server.

    Now it is a little diffrent, it takes very long on Completing backup and then fail with msg:

     [2009/01/26 09:35:03 AM]: Verbose: Starting object: Shared Search Index.
    [2009/01/26 10:35:35 AM]: Error: Object Shared Search Index failed in event OnBackupComplete. For more information, see the error log located in the backup directory.
     WebException: The current operation timed-out after 3600 seconds
    [2009/01/26 10:35:35 AM]: Debug:    at Microsoft.Office.Server.Search.Administration.CatalogPauseTimeout.WaitAndThrowIfTimeout()
       at Microsoft.Office.Server.Search.Administration.SearchApi.CatalogResumeCrawl(GathererPauseReason reason)
       at Microsoft.Office.Server.Search.Administration.SearchSharedApplication.Microsoft.SharePoint.Administration.Backup.IBackupRestore.OnBackupComplete(Object sender, SPBackupInformation args)
    [2009/01/26 10:35:35 AM]: Verbose: Starting object: SharedServices9_Search_DB.

     There is 3 error msg's under Crawl settings:

     http://my/
    Crawling this document could not be completed because the remote server did not respond within the specified timeout. Try crawling the server later, or increase the timeout value. You may also try scheduling crawls during off-peak usage times. Local Office SharePoint Server sites 11/30/2008 2:01 AM 
     
      sts3://my
    Crawling this document could not be completed because the remote server did not respond within the specified timeout. Try crawling the server later, or increase the timeout value. You may also try scheduling crawls during off-peak usage times. Local Office SharePoint Server sites 11/30/2008 2:01 AM 
     
      sts3://my/contentdbid={7d0a8757-387c-4c84-af54-...
    Crawling this document could not be completed because the remote server did not respond within the specified timeout. Try crawling the server later, or increase the timeout value. You may also try scheduling crawls during off-peak usage times. Local Office SharePoint Server sites 11/30/2008 2:01 AM 
     

     

     

     

    Monday, January 26, 2009 10:23 AM
  • Well there probably aren't many users on your farm at 2am in the morning.  But you might want to double-check that you aren't running something else during that time (like SharePoint or SQL backups).

    If none of that helps you, then you might actually need to increase the timeout settings as the error suggests.  Here's the instructions to do that:  http://technet.microsoft.com/en-us/library/cc263406.aspx

    -PlateSpinner

    Wednesday, February 11, 2009 6:13 PM