Search service is offline, no search even on new SSP's
in [Portal Server]
|
Prev: Sharepoint Upload error
Next: Editing 'My Website'
From: Diego Moore on 10 Jan 2008 05:54 Well where do I start, we've been working on fixing the search on our Intranet SSP for days and are not getting very far but I believe we're getting close... In summary we had a severe SQL server crash (20Gb of dump/log files ensured the c: drive was filled) as a result of indexing some Internet sites and we had to force the crawling to stop. Since then the search has been off-line will not come back online even if we create new SSP's! We've setup a new server as it all appeared to point to a broken installation. Installed MOSS and restored the 3 databases via SQL (Intranet_Content_DB, IntranetSSP_Content_DB & IntranetSSP_Search_DB) but still nothing. So we created a brand new application, site and SSP and nothing. When we go to the either of the SSP admin sites and click on Search settings we get: "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 also be because an indexer move is in progress." When we go to Manage Search Service in CA we get: Query and Index Servers Server name: moss2007 Search service: Office SharePoint Server Search Indexing and Query Remaining disk space: E: 15GB SSPs hosted: IntranetSSP, SharedServices1 Shared Service Providers with Search Enabled SSP name: IntranetSSP Crawling Status: Search service offline Items in index: 6706 Propagation status: Search service offline SSP name: SharedServices1 Crawling Status: Search service offline Items in index: 0 Propagation status: Search service offline This is what we get in the Event log every second: Event Type: Error Event Source: Office Server Search Event Category: Gatherer Event ID: 10032 Date: 10/01/2008 Time: 08:08:44 User: N/A Computer: MOSS2007 Description: Could not create a database session. Context: Application '051ac206-d635-4f04-b751-aeb332834fbb' Details: The database connection string is not available. (0xc0041228) Event Type: Error Event Source: Office Server Search Event Category: Gatherer Event ID: 10046 Date: 10/01/2008 Time: 08:08:44 User: N/A Computer: MOSS2007 Description: The database connection string is not available. Context: Application '051ac206-d635-4f04-b751-aeb332834fbb' Followed by this information (not an error): Event Type: Information Event Source: Office Server Search Event Category: Search service Event ID: 1013 Date: 10/01/2008 Time: 08:08:44 User: N/A Computer: MOSS2007 Description: The search service stopped normally. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. And then: Event Type: Error Event Source: Office SharePoint Server Event Category: Office Server Shared Services Event ID: 6482 Date: 10/01/2008 Time: 08:08:46 User: N/A Computer: MOSS2007 Description: Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (2c25186a-5c21-485d-982e-7ddcfbfa7ad3). Reason: The database connection string is not available. Techinal Support Details: System.Runtime.InteropServices.COMException (0xC0041228): The database connection string is not available. 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.AddApp(Role role) at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.InstallGathererApplicationIf() at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize() at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob) Here are some more details: 051ac206-d635-4f04-b751-aeb332834fbb - This is the index for the SSP which can be found on E:\SharePoint Data\Microsoft Office Servers \12.0\Data\Office Server\Applications\051ac206-d635-4f04-b751- aeb332834fbb Any ideas? Many thanks in advanced, Diego Moore
From: John Timney (MVP) on 10 Jan 2008 14:57 Have you tried resetting the index from the admin console. Remove your query servers from the farm, reboot the server and re-add them - then reset the index and see if it helps. Regards John Timney (MVP) http://www.johntimney.com http://www.johntimney.com/blog "Diego Moore" <diego.moore(a)gmail.com> wrote in message news:242fcf46-596d-433f-a008-51b42dc65daa(a)z17g2000hsg.googlegroups.com... > Well where do I start, we've been working on fixing the search on our > Intranet SSP for days and are not getting very far but I believe we're > getting close... > > In summary we had a severe SQL server crash (20Gb of dump/log files > ensured the c: drive was filled) as a result of indexing some Internet > sites and we had to force the crawling to stop. Since then the search > has been off-line will not come back online even if we create new > SSP's! > > We've setup a new server as it all appeared to point to a broken > installation. Installed MOSS and restored the 3 databases via SQL > (Intranet_Content_DB, IntranetSSP_Content_DB & IntranetSSP_Search_DB) > but still nothing. > > So we created a brand new application, site and SSP and nothing. When > we go to the either of the SSP admin sites and click on Search > settings we get: > > "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 also be because an indexer move is in > progress." > > When we go to Manage Search Service in CA we get: > > Query and Index Servers > Server name: moss2007 > Search service: Office SharePoint Server Search Indexing and Query > Remaining disk space: E: 15GB > SSPs hosted: IntranetSSP, SharedServices1 > > > Shared Service Providers with Search Enabled > SSP name: IntranetSSP > Crawling Status: Search service offline > Items in index: 6706 > Propagation status: Search service offline > > SSP name: SharedServices1 > Crawling Status: Search service offline > Items in index: 0 > Propagation status: Search service offline > > > This is what we get in the Event log every second: > > > Event Type: Error > Event Source: Office Server Search > Event Category: Gatherer > Event ID: 10032 > Date: 10/01/2008 > Time: 08:08:44 > User: N/A > Computer: MOSS2007 > Description: > Could not create a database session. > > Context: Application '051ac206-d635-4f04-b751-aeb332834fbb' > > Details: > The database connection string is not available. (0xc0041228) > > > > > Event Type: Error > Event Source: Office Server Search > Event Category: Gatherer > Event ID: 10046 > Date: 10/01/2008 > Time: 08:08:44 > User: N/A > Computer: MOSS2007 > Description: > The database connection string is not available. > > Context: Application '051ac206-d635-4f04-b751-aeb332834fbb' > > > > > Followed by this information (not an error): > > Event Type: Information > Event Source: Office Server Search > Event Category: Search service > Event ID: 1013 > Date: 10/01/2008 > Time: 08:08:44 > User: N/A > Computer: MOSS2007 > Description: > The search service stopped normally. > > For more information, see Help and Support Center at > http://go.microsoft.com/fwlink/events.asp. > > And then: > > Event Type: Error > Event Source: Office SharePoint Server > Event Category: Office Server Shared Services > Event ID: 6482 > Date: 10/01/2008 > Time: 08:08:46 > User: N/A > Computer: MOSS2007 > Description: > Application Server Administration job failed for service instance > Microsoft.Office.Server.Search.Administration.SearchServiceInstance > (2c25186a-5c21-485d-982e-7ddcfbfa7ad3). > > Reason: The database connection string is not available. > > Techinal Support Details: > System.Runtime.InteropServices.COMException (0xC0041228): The database > connection string is not available. > 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.AddApp(Role > role) > at > Microsoft.Office.Server.Search.Administration.SearchServiceInstance.InstallGathererApplicationIf() > at > Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize() > at > Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean > isAdministrationServiceJob) > > > Here are some more details: > > 051ac206-d635-4f04-b751-aeb332834fbb - This is the index for the SSP > which can be found on E:\SharePoint Data\Microsoft Office Servers > \12.0\Data\Office Server\Applications\051ac206-d635-4f04-b751- > aeb332834fbb > > > Any ideas? > > Many thanks in advanced, > Diego Moore
From: Diego Moore on 14 Jan 2008 07:18 On Jan 10, 7:57 pm, "John Timney \(MVP\)" <xyz_j...(a)timney.eclipse.co.uk> wrote: > Have you tried resetting the index from the admin console. Remove your > query servers from the farm, reboot the server and re-add them - then reset > the index and see if it helps. I'm not entirely sure how to reset the index via stsadmin but I've read that changing the location of the Index would cause a re-index (is reset the same as re-index?!). So I've done that many times before... Let me look into how your *meant* to reset the index and I will follow your guidelines by the line and see what happens. Thanks,
From: Diego Moore on 14 Jan 2008 14:40 On Jan 14, 12:18 pm, Diego Moore <diego.mo...(a)gmail.com> wrote: > On Jan 10, 7:57 pm, "John Timney \(MVP\)" > > <xyz_j...(a)timney.eclipse.co.uk> wrote: > > Have you tried resetting the index from the admin console. Remove your > > query servers from the farm, reboot the server and re-add them - then reset > > the index and see if it helps. > > I'm not entirely sure how to reset the index via stsadmin but I've > read that changing the location of the Index would cause a re-index > (is reset the same as re-index?!). So I've done that many times > before... > > Let me look into how your *meant* to reset the index and I will follow > your guidelines by the line and see what happens. Well I've reset it as per instructions: 1. Stopped the the search from Central Administration 2. Rebooted 3. Started the search service with a new default Index location (MS say this resets the Index http://technet2.microsoft.com/Office/en-us/library/8228ae26-b611-48b8-bb8c-011c707d3c4d1033.mspx?mfr=true): stsadm -o osearch -action start -role index -farmcontactemail email(a)example.org -farmperformancelevel maximum -farmserviceaccount DOMAIN\SPSharedServicesAcct -farmservicepassword pass(a)word1 - defaultindexlocation "E:\SharePoint Data\Microsoft Office Servers \12.0\Data\Office Server\Applications2" 4. Rebooted again (why not?, stsadm -o osearch -list was telling me search was online but CA did not think so!) 5. Selected the indexing server for the two SSP's 6. Checked out E:\SharePoint Data\Microsoft Office Servers\12.0\Data \Office Server\Applications2 which is now empty! 7. Last reboot for my own sanity... Result? Nada! Now the other SSP that was working is now offline as well and the Applications2 folder is still empty. I'm starting to think it doesn't like to move the Indexer. Any other ideas? Let me see if I can move the Index back to the original folder and recover the other SSP...
From: John Timney (MVP) on 14 Jan 2008 16:05
I have seen problems with farms where the index and query server file locations do not match and reset doesn't help. If this was me, I would remove the index and query servers and then recreate them after a full IIS reset or reboot. Get your index working first with the alternate access mappings in place before you re-add the query server. With luck it will beging to propogate one the query server gets added into the farm. Regards John Timney (MVP) http://www.johntimney.com http://www.johntimney.com/blog "Diego Moore" <diego.moore(a)gmail.com> wrote in message news:4c705bd8-707d-4927-ab11-1ce256cd003b(a)f3g2000hsg.googlegroups.com... > On Jan 14, 12:18 pm, Diego Moore <diego.mo...(a)gmail.com> wrote: >> On Jan 10, 7:57 pm, "John Timney \(MVP\)" >> >> <xyz_j...(a)timney.eclipse.co.uk> wrote: >> > Have you tried resetting the index from the admin console. Remove your >> > query servers from the farm, reboot the server and re-add them - then >> > reset >> > the index and see if it helps. >> >> I'm not entirely sure how to reset the index via stsadmin but I've >> read that changing the location of the Index would cause a re-index >> (is reset the same as re-index?!). So I've done that many times >> before... >> >> Let me look into how your *meant* to reset the index and I will follow >> your guidelines by the line and see what happens. > > Well I've reset it as per instructions: > > 1. Stopped the the search from Central Administration > 2. Rebooted > 3. Started the search service with a new default Index location (MS > say this resets the Index > http://technet2.microsoft.com/Office/en-us/library/8228ae26-b611-48b8-bb8c-011c707d3c4d1033.mspx?mfr=true): > > stsadm -o osearch -action start -role index -farmcontactemail > email(a)example.org -farmperformancelevel maximum -farmserviceaccount > DOMAIN\SPSharedServicesAcct -farmservicepassword pass(a)word1 - > defaultindexlocation "E:\SharePoint Data\Microsoft Office Servers > \12.0\Data\Office Server\Applications2" > > 4. Rebooted again (why not?, stsadm -o osearch -list was telling me > search was online but CA did not think so!) > 5. Selected the indexing server for the two SSP's > 6. Checked out E:\SharePoint Data\Microsoft Office Servers\12.0\Data > \Office Server\Applications2 which is now empty! > 7. Last reboot for my own sanity... > > Result? Nada! Now the other SSP that was working is now offline as > well and the Applications2 folder is still empty. I'm starting to > think it doesn't like to move the Indexer. > > Any other ideas? > > Let me see if I can move the Index back to the original folder and > recover the other SSP... |