Backup problem on SP 2007 - Shared search index
I am having a problem that I really can't figure out, and have found -nothing- online.
When I run a backup (fromCentral Adminor stsadm) it hangs just after trying to start the Shared Search Index, as seen from the logbelow:
Code Snippet
[8/28/2007 1:06:53 PM]: Verbose: Starting object: Shared Search Index.[8/28/2007 2:07:25 PM]: Error: Object Shared Search Index failed in event OnPrepareBackup. For more information, see the error log located in the backup directory.WebException: The current operation timed-out after 3600 seconds[8/28/2007 2:07:25 PM]: Debug: at Microsoft.Office.Server.Search.Administration.SearchSharedApplication.Microsoft.SharePoint.Administration.Backup.IBackupRestore.OnPrepareBackup(Object sender, SPBackupInformation args) at Microsoft.SharePoint.Administration.Backup.SPBackup.RunPrepareBackup(SPBackupRestoreObject node)[8/28/2007 2:07:25 PM]: Verbose: Starting object: sharepoint_company_MOSS_search.
A little bit later in the log, I get this:
Code Snippet
[8/28/2007 2:14:44 PM]: Verbose: Starting object: Shared Search Index.[8/28/2007 2:14:45 PM]: Progress: [Shared Search Index] 50 percent complete.[8/28/2007 2:14:45 PM]: Error: Object Shared Search Index failed in event OnBackup. 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.WebException: The current operation timed-out after 3600 secondsWebException: The current operation timed-out after 3600 seconds[8/28/2007 2:14:45 PM]: Debug: at Microsoft.Office.Server.Search.Administration.SearchSharedApplication.Microsoft.SharePoint.Administration.Backup.IBackupRestore.OnBackup(Object sender, SPBackupInformation args)[8/28/2007 2:14:45 PM]: Verbose: Starting object: sharepoint_company_MOSS_search.
Does anyone have any idea what could be going on?
August 29th, 2007 1:07am
I'm having the exact same problem. Everything worked fine for me for a week using this command to backup sharepoint: stsadm.exe -o backup -directory \\MOSS\MOSSBackups -backupmethod full
Then suddently after installing this latest round of MSFT updates I'm getting the errors you describe. The only update for sharepoint was one related to error reporting when opening office docs. So I don't think that's it. I've tried clearing the index and doing a full crawl, and I have the latest SQL service packs and no management jobs on the SQL server at all (so no job that would remove duplicates from the index).
Anyone else have any thoughts? MSFT?
Thanks,
Alex.
Free Windows Admin Tool Kit Click here and download it now
September 2nd, 2007 6:04pm
Hi Alex,This is a similar issue to one I am having. Take a look at this thread for a starting point to solving the problems.Cheersdarkagn
September 3rd, 2007 3:26am
Thanks for trying, but that thread didn't help. So far the only thing that has helped is restarting the osearch service just before the backup. Any one have any other thoughts? I'd really prefer to not have to restart services to make this work. I've checked and the indexing server isn't actively indexing anything at the time of the backups.
Thanks,
Alex.
Free Windows Admin Tool Kit Click here and download it now
September 11th, 2007 6:21am
I wanted to follow-up with some new information. Recently my backups started generating an error with the Shared Search Index on the onbackupcomplete event:
[10/19/2007 8:58:58 PM]: Verbose: Starting OnBackupComplete event.
...
[10/19/2007 8:59:06 PM]: Verbose: Starting object: Shared Search Index.[10/19/2007 9:59:44 PM]: 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[10/19/2007 9:59:44 PM]: 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)
After talking with MSFT they said that the sharepoint accounts may have gotten corrupted and had me re-enter them using the info in this article as a guide: http://support.microsoft.com/kb/934838/en-us I found that after doing this I needed to delete and re-create the search index propagation share (but that may have been because I may have accidentally set the account for one of the services to be something other than what it used to be). Also unfortunately I wasn't able to find any way to lookup what values were currently being used (the MSFT service rep didn't know either).
I wish I knew why things got corrupted, and how to prevent it from happening agian in the future.
Alex.
October 21st, 2007 5:48am
the same thing happened on one of our clients. in addition the timer serviceApplication Server Administration Service Timer Job was running without succeding,showing a status of Initiating and the Search status was showing Computing Ranking. the backups where alsologging the same error message as Dratcha indicated.Resetting the osearch account resolved all of these problems.Thanks,Lavi
Free Windows Admin Tool Kit Click here and download it now
November 6th, 2008 6:45pm
sorry...but what you mean with Resetting the osearch account, can you tell exactly what you did? tks a lot!
January 26th, 2010 10:16pm
I have the sane Issue in my sharepoint server, the bakcup stuck in the Shared Search Index . Thenthe log sa about 3600 seconds. How I can repair the corrupted search system in sharepoint 2007?
Free Windows Admin Tool Kit Click here and download it now
October 28th, 2010 5:23pm
I don't suppose anyone ever resolved this issue? We're currently experiencing the same thing after the latest round of Windows Updates. Our third party backup tool is also failing on the SSP and Search index.If at first you don't succeed, ask an MVP.
June 16th, 2011 8:14pm