Moss 2007 SSP error 'Search for Application' {0} 'not ready. "
I am trying to fix a broken SSP on the MOSS 2007 site. The problem I am facing is the following ...
On the SSP Search Options page, I receive the following message:
The search service is currently disabled. Visit the Services on Server page in the SharePoint admin center to check if the service is enabled. It could also be due to the pointer moving.
On the SSP User Profiles and Properties page, I get this in red at the top:
An error occurred while accessing a SQL Server database or Office SharePoint Server Search service. If this is the first time you've seen this message, please try again later. If this problem persists, contact your administrator.
I contacted my administrator, but I am currently, and it turns out I don't know more than about the problem.
I get the following message in the event log:
The Execute method of the Microsoft.Office.Server.Search.Administration.IndexingScheduleJobDefinition (ID 8714973c-0514-4e1a-be01-e1fe8bc01a18) threw an exception. See below for more details.
Application search '{0}' is not ready.
The event ID is 6398, which is not as useful as I hoped, but I don't find the message interesting in the sense that it looks like a String.format call with no overridden value. Unfortunately, there is nothing interesting about what he tells me how to fix this problem.
Sharepoint's own magazine offers the following:
UserProfileConfigManager.GetImportStatus () failed to obtain crawl status: System.InvalidOperationException: Search application '{0}' is not ready.
at Microsoft.Office.Server.Search.Administration.SearchApi..ctor (WellKnownSearchCatalogs catalog, SearchSharedApplication application)
at Microsoft.Office.Server.Search.Administration.SearchSharedApplication.get_SearchApi ()
at Microsoft.Office.Server.UserProfiles.UserProfileConfigManager.c__DisplayClass3.b__0 ()
at Microsoft.Office.Server.Diagnostics.FirstChanceHandler.ExceptionFilter (Boolean fRethrowException, TryBlock tryBlock, FilterBlock filter, CatchBlock catchBlock, FinallyBlock finallyBlock)
I tried to stop and start the search service, remove and re-add it from the admin panel, and pretty much everything I can find using Sharepoint's native administrative tools, which leads me to think that the problem here might be database or permissions related ...
The same server had a second SSP installed which I think was part of the original cause of the problem, but removing it made no difference.
source to share
So it seems like the problem was a corrupted Shared Service Provider (don't know how it happened, but there you go) and the only working solution I could find was to uninstall it and start over.
I suspect there might have been a more elegant fix, changing something in the database somewhere, but I don't know the Sharepoint database model very well to find it in available times.
source to share
Maybe you can figure it out - I'm new to sharepoint, so it doesn't make much sense to me: "Service Shared", after looking for a solution, strongly stipulates this forum where the person is facing the same problem. After reading the infinity of comments I made to solve the problem, it was creating a new shared service, later it assigns other apps to it and then I put it as predefined, it initiates importing profiles and then hearing, obviously I did this first on the test site in case something happens, later fixes the first common service and finally the error that I solved. The application config registry snapshot in the database was saved correctly. Context: application `SharedServices2 '"
You haven't said anything about tapeworms, so you may be using a newer version.
Transfer:
Personally, I would try the msdn forums.
source to share
Same problem. My DBA will delete the search database correctly and it still doesn't work. I will post the solution on my blog when I find anything. At the moment we are opening a call to MS.
- New SSP created 2- In Central Administrator click on Shared Service Administration
3- Click on Edit Associations and move all web applications to the new SSP
Select the new search_DB and choose a good server to index if you are in a farm
Problems caused by this operation: We notice that we are losing statistics for our sites.
if you tried this solution please also return your feed to us
Thank.