ISSUE:
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.
Reasons: there might be couple of reasons
1) Index file is corrupted. The index file is generally located at d:\Program Files\Microsoft Office
Servers\12.0\Data\Office\Server\Applications.
2) Your account that is used for search might not have access to the content source.
3) Your indexer might be in move as stated in the error message.
Here are some of the error messages that i have seen in the event viewer.
Event Type: Error
Event Source: Office SharePoint Server
Event Category: Office Server Shared Services
Event ID: 6483
Date: 11/12/2009
Time: 10:43:2009
User: N/A
Computer: SERVERNAME
Description:
Application synchronization failed for Microsoft.Office.Server.Search.Administration.SearchService
Reason: Cannot open database "Sharedservices1_Search_DB_36fea12f-9bf5-4286-81c8-942e5509bf57" requested by the login. The login failed.
Login failed for the user "SEARCH SERVICE ACCOUNT"
Event Type: Error
Event Source: Office Server Search
Event Category: Gatherer
Event ID: 10030
Date: 11/12/2009
Time: 10:43:26 AM
User: N/A
Computer: SERVERNAME
Description:
Error importing registry hive from the configuration database and into the registry.
Context: Application '9f2781a3-9086-4ab5-bd0d-1baec33de57b'
Details:
Access is denied. (0x80070005)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: Office Server Search
Event Category: Gatherer
Event ID: 10046
Date: 11/12/2009
Time: 10:43:26 AM
User: N/A
Computer: SERVERNAME
Description:
The database connection string is not available.
Context: Application '9f2781a3-9086-4ab5-bd0d-1baec33de57b'
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: Office Server Search
Event Category: Gatherer
Event ID: 10032
Date: 11/12/2009
Time: 10:43:26 AM
User: N/A
Computer: SERVERNAME
Description:
Could not create a database session.
Context: Application '9f2781a3-9086-4ab5-bd0d-1baec33de57b'
Here are the steps i followed to fix the search issue:
1) Stop the Office SharePoint search through "Central Adminsitration"
- From Central Administration go to Operations --> Services running on the server. Then
look for the "Office SharePoint Server Search". Then click on "stop".
2) This de-configures the search service and deletes all the indexed content permanently.
Note: when click on "stop" you might be getting a warning message asking "Are you sure you
want to uninstall the Office SharePoint Server Search from this server?"
Click on "Ok"
3) Now click on "start"
Note: in the "Service Account"(used for search service) section make sure that account has
access to the search data-base.
4) Then click "Shared Services Administration" hover over the failing SSP and select edit.
5) Now you will notice that the indexer is not configured for this Shared ServiceProvider. Select
it from drop-down.
Note: If you are using stand alone server the only the server name will be appearing in the
dropdown.
6) In the "SSP Service Credentials Section" make sure that the account has access to the Search
data-base.
7) Here is the important part. The index server you have selected is probably that you have
used before. If it is, go to the server and locate the indexer files. It is in the text box right
below the dropdown you just used. The path of the index file is written at beginning.
8) In there you will find a folder with GUID name. At the end of the folder add "_Old".
9) Now go back to SSP settings and click "Ok". Wait for one minute the indexer will create the
new GUID folder.
10) Now start the full crawl from the Shared Services Search Administartion,
Conclusion: In this case the service account that is used for search does not have access to the Search data-base. The service account will be given at Shared Services "SSP Credentials" section. And the indexer file is corrupted, By following all the above ten steps i got the Search issue fixed. Hope this post might help to others who have similar/same issue.
References:
http://vspug.com/jasonmedero/2008/09/15/moss-2007-error-when-moving-indexing-role-the-search-service-is-currently-offline-visit-the-services-on-server-page/
http://social.technet.microsoft.com/Forums/en/sharepointsearch/thread/22af594f-10d7-4672-b1f9-472f9aebd3f6
http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/2009/02/24/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.aspx
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.
Reasons: there might be couple of reasons
1) Index file is corrupted. The index file is generally located at d:\Program Files\Microsoft Office
Servers\12.0\Data\Office\Server\Applications.
2) Your account that is used for search might not have access to the content source.
3) Your indexer might be in move as stated in the error message.
Here are some of the error messages that i have seen in the event viewer.
Event Type: Error
Event Source: Office SharePoint Server
Event Category: Office Server Shared Services
Event ID: 6483
Date: 11/12/2009
Time: 10:43:2009
User: N/A
Computer: SERVERNAME
Description:
Application synchronization failed for Microsoft.Office.Server.Search.Administration.SearchService
Reason: Cannot open database "Sharedservices1_Search_DB_36fea12f-9bf5-4286-81c8-942e5509bf57" requested by the login. The login failed.
Login failed for the user "SEARCH SERVICE ACCOUNT"
Event Type: Error
Event Source: Office Server Search
Event Category: Gatherer
Event ID: 10030
Date: 11/12/2009
Time: 10:43:26 AM
User: N/A
Computer: SERVERNAME
Description:
Error importing registry hive from the configuration database and into the registry.
Context: Application '9f2781a3-9086-4ab5-bd0d-1baec33de57b'
Details:
Access is denied. (0x80070005)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: Office Server Search
Event Category: Gatherer
Event ID: 10046
Date: 11/12/2009
Time: 10:43:26 AM
User: N/A
Computer: SERVERNAME
Description:
The database connection string is not available.
Context: Application '9f2781a3-9086-4ab5-bd0d-1baec33de57b'
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: Office Server Search
Event Category: Gatherer
Event ID: 10032
Date: 11/12/2009
Time: 10:43:26 AM
User: N/A
Computer: SERVERNAME
Description:
Could not create a database session.
Context: Application '9f2781a3-9086-4ab5-bd0d-1baec33de57b'
Here are the steps i followed to fix the search issue:
1) Stop the Office SharePoint search through "Central Adminsitration"
- From Central Administration go to Operations --> Services running on the server. Then
look for the "Office SharePoint Server Search". Then click on "stop".
2) This de-configures the search service and deletes all the indexed content permanently.
Note: when click on "stop" you might be getting a warning message asking "Are you sure you
want to uninstall the Office SharePoint Server Search from this server?"
Click on "Ok"
3) Now click on "start"
Note: in the "Service Account"(used for search service) section make sure that account has
access to the search data-base.
4) Then click "Shared Services Administration" hover over the failing SSP and select edit.
5) Now you will notice that the indexer is not configured for this Shared ServiceProvider. Select
it from drop-down.
Note: If you are using stand alone server the only the server name will be appearing in the
dropdown.
6) In the "SSP Service Credentials Section" make sure that the account has access to the Search
data-base.
7) Here is the important part. The index server you have selected is probably that you have
used before. If it is, go to the server and locate the indexer files. It is in the text box right
below the dropdown you just used. The path of the index file is written at beginning.
8) In there you will find a folder with GUID name. At the end of the folder add "_Old".
9) Now go back to SSP settings and click "Ok". Wait for one minute the indexer will create the
new GUID folder.
10) Now start the full crawl from the Shared Services Search Administartion,
Conclusion: In this case the service account that is used for search does not have access to the Search data-base. The service account will be given at Shared Services "SSP Credentials" section. And the indexer file is corrupted, By following all the above ten steps i got the Search issue fixed. Hope this post might help to others who have similar/same issue.
References:
http://vspug.com/jasonmedero/2008/09/15/moss-2007-error-when-moving-indexing-role-the-search-service-is-currently-offline-visit-the-services-on-server-page/
http://social.technet.microsoft.com/Forums/en/sharepointsearch/thread/22af594f-10d7-4672-b1f9-472f9aebd3f6
http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/2009/02/24/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.aspx
No comments:
Post a Comment