Object Shared Search Index failed in event OnBackupComplete error
Hello, I have a scheduled task that performs a backup of my MOSS site every night. Every once in a while, the task starts to fail with the following error:
Object Shared Search Index failed in event OnBackupComplete. For more information, see the error log located in the backup directory.
I checked the error log in the backup directory and this is what I see:
[4/3/2007 3:04:32 AM]: Verbose: Starting object: Shared Search Index.
[4/3/2007 4:05:06 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
[4/3/2007 4:05:06 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)
[4/3/2007 4:05:06 AM]: Verbose: Starting object: MySiteSearchDB.and the only way of getting the backup functionality to work again is to rebuild the search index. It seems that something is locked and I don't know what.
Does anybody know what the issue could be and if there's an easier way of fixing it?
thanks
Gabo
- MovidoMike Walsh MVPMVP, Moderadorsegunda-feira, 8 de setembro de 2008 16:58Better forum (Moved from SharePoint - Setup, Upgrade, Administration and Operation to SharePoint - Search)
Todas as Respostas
yes i get the same error.
but how to rebuild the search index ?
and how to make sechadule to the bkp process
Thanks
Naggar
I ran into the same error message. I was able to get the error to go away and have the backup complete without error by:
-> Search Settings -> Reset all crawled content
After I reset the crawled content, my backups started running great.
I don't know about the long-term sustainability of this (i.e. do we have to reset all crawled content before each backup? etc...)
Hope this helps someone, sometime.
-James
Thanks gurufoo...
that was just the work around i needed...
now if only a permanant fix was introduced...
Cheers,
Hi,
I am having the same problem. Can you please let me know if we reset the crawled content, do we have any other implication to think like alerts or anything else?Thank you,
Anu- Sugerido como RespostaSidKale sexta-feira, 3 de abril de 2009 9:44
- Não Sugerido como RespostaMike Walsh MVPMVP, Moderadorsexta-feira, 3 de abril de 2009 11:36
- Moving to the Search forum
- Known issue: http://support.microsoft.com/kb/961750 havent tested it yet but I hope this fixes it.
- Hi, I had the same issue after I applied Office Server SP2 on my Production, Can someone please let me know if this hotfix http://support.microsoft.com/kb/961750 has been included in the Office Server Service Pack2 or not? If so why is it occurring again?
I will try resetting the crawled content tonight and check to see if it happens again. - Issue resolved by resetting the crawled content as suggested in previous replies, Although I am still puzzled as to why it the issue re-appeared even after applying the SP2 for MOSS and WSS 3.0. I had two SSPs on my production farm, one for SharePoint Sites and other one for MS Office Project Server 2007.
Resetting crawled content for the 2nd SSP i.e for SSP for MS Office Project Server 2007 fixed the issue.
