Moss 2007 SSP 错误“搜索应用程序 '{0}” 还没有准备好。”
我正在尝试修复 MOSS 2007 站点上损坏的 SSP。 我遇到的问题如下...
在 SSP“搜索设置”页面中,我收到此消息:
搜索服务当前处于离线状态。 访问 SharePoint 管理中心的“服务器上的服务”页面以验证该服务是否已启用。 这也可能是因为索引器移动正在进行中。
在 SSP“用户配置文件和属性”页面中,我在顶部看到红色:
访问 SQL Server 数据库或 Office SharePoint Server 搜索服务时发生错误。 如果这是您第一次看到此消息,请稍后再试。 如果此问题仍然存在,请联系您的管理员。
我已经联系了我的管理员,但目前是我,结果证明我对这个问题的了解并不多。
在事件日志中,我收到以下消息:
作业定义 Microsoft.Office.Server.Search.Administration.IndexingScheduleJobDefinition (ID 8714973c-0514-4e1a-be01-e1fe8bc01a18) 的执行方法引发异常。 下面包含更多信息。
搜索应用程序“{0}”尚未准备就绪。
事件 ID 是 6398,它没有我希望的那么有用,但我没有找到有趣的消息是它看起来像一个 String.format 调用,其中缺少替换值。 不幸的是,它没有告诉我如何解决问题。
Sharepoint 自己的日志提供了这一点:
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)
我尝试过停止和启动搜索服务,从管理面板中删除并重新添加它,以及我能找到的几乎所有其他与 Sharepoint 自己的管理工具有关的事情,这让我相信这里的问题可能与数据库或权限相关。
在同一服务器上设置了第二个 SSP,我认为这可能是问题的原始原因的一部分,但删除它并没有什么区别。
I'm trying to fix a broken SSP on a MOSS 2007 site. The problem I am running into manifests itself as follows...
In the SSP "Search Settings" page I get this message:
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.
In the SSP "User Profiles and Properties" page I get this in red at the top:
An error has occurred while accessing the SQL Server database or the Office SharePoint Server Search service. If this is the first time you have seen this message, try again later. If this problem persists, contact your administrator.
I have contacted my administrator, but that is currently me and it turns out I don't know any more than I do about the problem.
In the Event Log I get the following message:
The Execute method of job definition Microsoft.Office.Server.Search.Administration.IndexingScheduleJobDefinition (ID 8714973c-0514-4e1a-be01-e1fe8bc01a18) threw an exception. More information is included below.
Search application '{0}' is not ready.
The Event ID is 6398, which isn't as useful as I had hoped, but I don find the message interesting in that it looks like a String.format call where the substituted value is missing. Unfortunately no interesting in that it tells me how to fix the problem.
Sharepoint's own log offers this:
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 have tried stopping and starting the search service, removing and re-adding it from the administration panel, and pretty much every other thing I could find to do with Sharepoint's own administrative tools, which leads me to believe the problem here may be database or permissions related.
There was a second SSP set up on the same server, which I think may have been part of the original cause of the problem, but removing it has made no difference.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(4)
作为对此的额外警告,如果您确实删除了 SSP,您可能会发现它没有删除干净,因此您会得到一堆仍然尝试在空数据库上运行的 SQL Server 任务,如果您有以下情况,这可能会导致问题在同一数据库服务器上运行的任何其他内容。
As an additional warning to this, if you do delete your SSP you may find that it doesn't delete cleanly so that you get a bunch of SQL server tasks that still try to run on an empty database, which can cause problems if you have anything else running on the same database server.
同样的问题。 我的 DBA 正确删除了搜索数据库,但它仍然不起作用。
当我发现一些东西时,我会将解决方案发布在我的博客上。
目前,我们发起 MS 通话。
2-在中央管理中,单击共享服务管理
3- 单击“更改关联”并将所有 Web 应用程序移动到新的 SSP
选择新的 search_DB 并选择将索引的良好服务器(如果您位于场中)
此操作产生的问题:
我们注意到我们丢失了网站的统计信息。
如果您尝试过此解决方案,请也向我们提供反馈,
谢谢。
http://dejacquelot.blogspot.com/
Same problem. My DBA delete correctly the search database and it still doesn't work.
I'll post the solution on my blog when I found something.
For the moment, we open a MS call.
2- In central admin, click on shared Services Administration
3- Click on "Change Associations" and move all the web apps to the new SSP
Choose a new search_DB and select the good server that will index if you are in a farm
Problems created by this operation:
We notice that we lose statistics information for our sites.
if you tried this solution, give us your feed back too
Thanks.
http://dejacquelot.blogspot.com/
也许你可以理解这一点 - 我是 sharepoint 的新手,所以这对我来说没有什么意义:
“服务共享,在寻找解决方案后,在这个论坛上遇到了同样的问题。在阅读了无数的评论后,我为解决问题所做的就是创建一个新的共享服务,后来它将其他应用程序分配给他,后来我按照预定的方式说了,它启动配置文件的导入,然后是听证会,显然我首先在测试站点中这样做,以防万一发生什么情况,后来消除了第一个共享服务,最后我解决了错误数据库中应用程序配置的注册表快照已正确存储。上下文:应用程序`SharedServices2'”
您没有提到有关绦虫的任何内容,因此您可能正在运行较新的版本。
翻译:
http: //tecnologiainformaticait.wordpress.com/2008/11/21/error-sharepoint-search-application-0-is-not-ready/
就个人而言,我会尝试 msdn 论坛。
Maybe you can make sense of this - I'm new to sharepoint, so it makes little sense to me:
"Service Shared, after looking for the solution much encontre this forum where a person tapeworm the same problem. After reading a infinity of commentaries, which I made to solve the problem was to create a new shared service, later it assigns the other applications to him and later I put it like predetermined, it initiates the import of profiles, and later the hearings, clearly first I did it in a site of tests just in case something happened, later eliminates the First Shared Service and finally the error I am solved. The snapshot of the Registry of the configuration of the application in the data base has been stored correctly. Context: application `SharedServices2 ′"
You didn't mention anything about tapeworms, so maybe you're running a newer version.
Translation of:
http://tecnologiainformaticait.wordpress.com/2008/11/21/error-sharepoint-search-application-0-is-not-ready/
Personally, I'd try the msdn forums.
因此,问题似乎是一个损坏的共享服务提供商(不知道它是如何产生的,但你就知道了),我能找到的唯一可行的解决方案就是删除它并重新开始。
我怀疑可能有一个更优雅的修复方法,可以通过更改数据库中的某些内容来实现,但我对 Sharepoint 数据库模型的了解还不够深,无法在可用的时间内找到它。
So it seems that the problem was a corrupted Shared Service Provider ( no idea how it came about, but there you go ) and the only working solution I could find was to delete it and start again.
I suspect there may have been a more elegant fix by changing something in the database somewhere, but I don't know the Sharepoint Database model well enough to find it in the time available.