Unable to Manage the Search Service
in [Portal Server]
|
Prev: Survey export to Excel
Next: Shared Service Error
From: monster on 28 Nov 2006 10:44 It turns out Microsoft SharePointPS Search is mssearch.exe. :-o monster wrote: > The only service that appears to be close to what your describing is > Microsoft SharePointPS Search. It was running, but unfortunately, I > attempted to restart the service which ended up failing to do so. > Currently it is caught in the "stopping" phase and will continue to be > until I reboot the box (which is production). > > Is accessing specific settings dependent on certain services running? > I ask because in my dev. environment, the Microsoft SharePointPS Search > service is not running and I'm still able to access links under "Search > Settings and Indexed Content" (under Site Settings), etc, etc > > richard.markiewicz wrote: > > Are the relevant sevices running? e.g. mssearch > > > > Rich
From: richard.markiewicz on 28 Nov 2006 16:49 I can't answer your question, but we had the same issue before on our prod. servers just after installing a new indexing server. The search had developed a problem, we restarted mssearch and it got stuck in the "stopping" stage as you describe. We rebooted the server and all was well, but fortunately it was out of hours so we had that luxury. As for the difference between your prod. and dev. environments, is the topology different? Is advanced search enabled/disabled on both? That's quite interesting. Rich
From: Danne on 29 Nov 2006 04:57 Have you tried to disable/enable the search service in SPS central admin? (probably have..) It can solve problems sometimes. I've also had this problem, don't remember the end of the story thou, think it was on a less critical machine so i could handle it the way i wanted without disturbing anyone so the solution to that one would hardly fit as best practice anyhow. //D richard.markiewicz skrev: > I can't answer your question, but we had the same issue before on our > prod. servers just after installing a new indexing server. > > The search had developed a problem, we restarted mssearch and it got > stuck in the "stopping" stage as you describe. We rebooted the server > and all was well, but fortunately it was out of hours so we had that > luxury. > > As for the difference between your prod. and dev. environments, is the > topology different? Is advanced search enabled/disabled on both? That's > quite interesting. > > Rich
From: monster on 29 Nov 2006 12:23 Rich: Hmm... the only difference is the dev. box is both the web/sql server whereas in prod we have a dedicated web server and a dedicated sql server. Both are similar in that the job, web, search, and index components are all assigned to the web server. We ended up rebooting the web/sql server which makes me feel like we just opened up a whole new can of worms. Now I can access the search links under "Search Settings and Indexed Content" but, whenever I do I get an error stating: The gatherer index was not initialized. The content index must be remounted. If the index is still not initialized, remove it. Also, content targeted to specific audiences are now being displayed for everyone ><; Danne: With the previous issue of not being able to access any search settings and now getting error listed above, I'm not able to try to attempt to enable/disable. Danne wrote: > Have you tried to disable/enable the search service in SPS central > admin? (probably have..) > It can solve problems sometimes. > I've also had this problem, don't remember the end of the story thou, > think it was on a less critical machine so i could handle it the way i > wanted without disturbing anyone so the solution to that one would > hardly fit as best practice anyhow. > > //D > > richard.markiewicz skrev: > > > I can't answer your question, but we had the same issue before on our > > prod. servers just after installing a new indexing server. > > > > The search had developed a problem, we restarted mssearch and it got > > stuck in the "stopping" stage as you describe. We rebooted the server > > and all was well, but fortunately it was out of hours so we had that > > luxury. > > > > As for the difference between your prod. and dev. environments, is the > > topology different? Is advanced search enabled/disabled on both? That's > > quite interesting. > > > > Rich
From: richard.markiewicz on 29 Nov 2006 16:32
If the situation is really critical you might think about opening a support ticket. However - on the Sharepoint media there is a support\tools folder with a program called (I think) catutil.exe. You can use it to manually move and delete content indexes. I used it to move all my indexes to a new drive not long ago and it worked very well. Rich |