Code, Code, Revolution!
I just have to share this problem I ran into this week and just couldn’t find the solution for. I recently installed and configured new Sharepoint MOSS 2007 farm. It has two servers, one server hosts all services and the other is a plain WFE. After a week or so in production the search server decided to give up and die. Everything looked fine and dany, it was running and I could start/stop it through “services on server” in central admin. But when trying to access the search service settings in the SSP it gave me this informative 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 also be because an indexer move is in progress.
It was running but offline. I had no reoccuring errors in the event log but trying to open the settings through SSP it gave me a cryptic error and when checking log file there was another the another informative error (NOT):
Fail to obtain crawl status. Microsoft.Office.Server.Search.Administration.DeletedConcurrencyException: Object e26da097-50ff-4386-b3f6-2b2b30f73b96 not found.
I tried restarting the services. Ran the Sharepoint repair tool. Verified the service accounts. Tried everything I could find on Google, which was quite a lot. Nothing could resurrect the search service from its either offline or moving state. Before going through the tedious work of re-installing the entire farm I disconnected both servers from the farm and re-connected them to the same farm. I cheered like a little girl on her first alcohol buzz when the search service was once again operational. It saved me plenty of sleep! If you are unfortunate enough to encounter the same problem, i hope this will save you some sleep too.
With this blog I try to provide useful tips and solutions for programming .NET, Objective-C and more. My name is Björn Sållarp, and I love writing code.
Micke
March 24th, 2009 at 3:25 pm
Hi!
Thank you for your post.
I had excatly the same problem and you pointed me in the right direction.
I run command:
psconfig -cmd upgrade -inplace b2b -wait
and just like magic the problems were gone!
Regard
Micke
Hari
May 18th, 2009 at 8:20 am
Hi,
i am getting same error “Search Service currently offline” and i am getting below error in evebt viewer –
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (3f22a128-d726-4184-9fd2-e9cee9ae275c).
Reason: Object e28ba8b5-41e2-4a6e-996a-c9b3bb9dae05 not found.
Techinal Support Details:
System.Collections.Generic.KeyNotFoundException: Object e28ba8b5-41e2-4a6e-996a-c9b3bb9dae05 not found.
Can u pls tell me steps to disconnect and connect from form server?
Will there be any loss in data’s? because this error is in production server and i need to make sure no data’s should get lost.
Kindly support me to solve this issue since its in production i cannot take more time to fix.
Regards,
Thiru
Björn Sållarp
May 18th, 2009 at 9:32 pm
First, did you test the solution Micke posted, using psconfig? If it solves the problem it will be the easiest solution (I havn’t tested it). If it doesn’t fix your problem, at least it won’t break anything.
In my case the farm was very small, only two servers. I don’t know what your setup is like but you could try to disconnect the server running the search service from the farm. Here’s a howto from MS: http://office.microsoft.com/en-us/sharepointportaladmin/HA011604591033.aspx
Depending on your farm setup this could make certain features unavailable unless you host them on other servers as well. I’m not sure but I would think you loose the search index by doing this, but that’s usually not a problem unless your application/company relies heavily on search and there’s a lot to index. But if they do, the search isn’t working anyways….
Let me know how it works out! Others will also be curious about benefiting from your experience.
Binoj
October 22nd, 2009 at 8:31 pm
Thanks for this great post. I ran into this same problem after I reset all crawled content. After restting the crawled content, I was not able to access the SSP search setting and started getting the same message you got. Before applying your solution I ran the command suggested by Micke and it worked like a charm.
jp matthew
November 24th, 2009 at 2:48 pm
excellent just like magic it was, “psconfig -cmd upgrade -inplace b2b -wait”, worked really well thank you..
maxmorgan
November 28th, 2009 at 12:53 pm
Yeah!
Magic words “psconfig -cmd upgrade -inplace b2b -wait”
Larry
December 17th, 2009 at 6:26 pm
Hi,
Are you able to post the actual steps to run psconfig, i.e how do you start psconfig..? I can see it in the BIN folder but need to know how to use it.
Thanks
Björn Sållarp
December 17th, 2009 at 7:52 pm
No offence Larry but if you don’t know that perhaps you shouldn’t mess around with psconfig.. Anyhow. Start the command shell by pressing win+r buttons and type cmd in the box. This will start your command shell. Make your way to the bin folder using the “cd” command. When you arrive at the bin folder, run psconfig.
Good Luck!
Pablo Appezzato
February 2nd, 2010 at 4:55 pm
YEAHHH!!! That fix my problem!!
thanks a LOTTT!!!!
links for 2010-03-31 « Jet Grrl
April 1st, 2010 at 1:21 am
[...] The search service is currently offline… | blog.sallarp.com (tags: search sharepoint) [...]