Sharepoint 2007 SSP Search DB too Large
I am running a Sharepoint 2007 server with an SQL 2005 backend. I have 2 WFE and an SQL Server. I have been trying to reduce the size of the SSP Search DB. Currently the .mdf is about 270GB. I have a maintenance plan in place that backs up the DB, truncates the logs, and shrinks the DB. When I attempt to Reset the crawled content, I get an error page, and nothing is removed from the DB. SHort of recreating the SSP, how can I fix this?
February 17th, 2011 7:36pm

What is the error you get when resetting the index? Once this gets fixed I think the search database would be cleared. Thanks, DipDip http://dzeee.net/sharepoint
Free Windows Admin Tool Kit Click here and download it now
February 20th, 2011 10:41am

What is the error you get when resetting the index? Once this gets fixed I think the search database would be cleared. Thanks, DipDip http://dzeee.net/sharepoint
February 20th, 2011 10:41am

The follwoing pops in the application log about the time Search Administration returns the error web page. Event: 6482 Source: Office Sharepoint Server Category: Office Server Shared services. Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (fa7b54d1-c05f-4910-b4ce-702366d992cd). Reason: The operation has timed out Techinal Support Details: System.Net.WebException: The operation has timed out at Microsoft.Office.Server.Search.Administration.SearchApi.RunOnServer[T](CodeToRun`1 remoteCode, CodeToRun`1 localCode, Boolean useCurrentSecurityContext, Int32 versionIn) at Microsoft.Office.Server.Search.Administration.SearchApi..ctor(WellKnownSearchCatalogs catalog, SearchSharedApplication application) at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize() at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob) For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Free Windows Admin Tool Kit Click here and download it now
February 21st, 2011 11:53am

The follwoing pops in the application log about the time Search Administration returns the error web page. BTW the Search Administration web page is just a generic error page and does not give a code or clue what is wrong, other than a time out. Event: 6482 Source: Office Sharepoint Server Category: Office Server Shared services. Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (fa7b54d1-c05f-4910-b4ce-702366d992cd). Reason: The operation has timed out Techinal Support Details: System.Net.WebException: The operation has timed out at Microsoft.Office.Server.Search.Administration.SearchApi.RunOnServer[T](CodeToRun`1 remoteCode, CodeToRun`1 localCode, Boolean useCurrentSecurityContext, Int32 versionIn) at Microsoft.Office.Server.Search.Administration.SearchApi..ctor(WellKnownSearchCatalogs catalog, SearchSharedApplication application) at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize() at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob) For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
February 21st, 2011 11:53am

Hi, Thanks to share your post. For the issue, do you mean that the “operation has time out” error happened when you reset the crawled content? If yes, this should be a web service error; my suggestion is to set the SendTimeOut and ReceiveTimeOut property in the web.config. And the followed references should also give you a hand: http://www.pcreview.co.uk/forums/system-net-webexception-operation-has-timed-out-again-t2898704.html. Hope this could help you! Leo
Free Windows Admin Tool Kit Click here and download it now
February 28th, 2011 3:57am

I am by no means a master of IIS/Webservers, so please bare with me. I checked the web.config in both the Sharepoint site VD and the SSP VD and neither had the timeout comment. I checked the web.config file in c:\program files\common files\microsoft shared\web server extensions\12\template\admin and made changes to the time out and had no effect I made changes to the web.config file in the .net directory, and it had no effect. I made the changes to timeout in web.config file at c:\program files\common files\microsoft shared\web server extensions\12\template\layouts and it had no effect The web page that is erroring is http://<server>:<port>/ssp/admin/_layouts/searchreset/aspx it says Error The search service is currently offline. Visit the services on Server page in SharePoint Central Administration to verify whether the service is enabled. This might be because an indexer move is in progress. Unfortunately the service is running.
March 1st, 2011 7:02pm

I am by no means a master of IIS/Webservers, so please bare with me. I checked the web.config in both the Sharepoint site VD and the SSP VD and neither had the timeout comment. I checked the web.config file in c:\program files\common files\microsoft shared\web server extensions\12\template\admin and made changes to the time out and had no effect I made changes to the web.config file in the .net directory, and it had no effect. I made the changes to timeout in web.config file at c:\program files\common files\microsoft shared\web server extensions\12\template\layouts and it had no effect The web page that is erroring is http://<server>:<port>/ssp/admin/_layouts/searchreset/aspx it says Error The search service is currently offline. Visit the services on Server page in SharePoint Central Administration to verify whether the service is enabled. This might be because an indexer move is in progress. Unfortunately the service is running.
Free Windows Admin Tool Kit Click here and download it now
March 1st, 2011 7:02pm

Perform the followig steps to fix the search offline issue and then try to reset the index. Stop and start search services on index server and other servers running the query role Restart the search servcie via central administration under Operations --> Services on server Go to service.msc and restart the Office Search Service manually Make sure that the search service account has correct rights to SQL Thanks, Dip Dip http://dzeee.net/sharepoint
March 1st, 2011 9:55pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics