抓取日志错误“未找到对象" [英] Crawl log errors 'The object was not found'

查看:103
本文介绍了抓取日志错误“未找到对象"的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

大家好,

我们已经将DR(灾难恢复)服务器配置为与生产服务器相同.

为此,我们已将Content DB还原到DR服务器.

现在,在配置灾难恢复站点的所有配置之后,我们已运行搜寻爬网.它将抓取我的内容数据库,其中包含我在DR中的生产站点内容.


我在搜寻内容源时遇到此错误.

<身体>

<身体>
计数

错误消息


解决方案

新服务器场中是否存在DR服务器?

您的抓取帐户应在Web应用程序级别具有对用户策略的完全读取"权限.

确保搜索抓取帐户有权访问服务器.

重新创建内容源,然后开始完全爬网并比较结果.

类似的帖子供您参考:

https://clouddeveloper. space/2012/03/16/sharepoint-search-the-crawler-not-communication-with-server/

https ://sharepoint.stackexchange.com/questions/204967/2013-on-premises-sharepoint-search-crawl-log-returns-error-on-the-crawler-could

Count

Error message


解决方案

Hi Er, 

Is the DR server existing in a new farm?

Your crawl account should have the Full Read permission on the User Policy at the Web Application level. 

Make sure Search Crawl Account has access to the server.

Recreate the content source, then start a full crawl and compare the results. 

Similar issue posts for your reference:

https://clouddeveloper.space/2012/03/16/sharepoint-search-the-crawler-could-not-communicate-with-the-server/

https://sharepoint.stackexchange.com/questions/204967/2013-on-premises-sharepoint-search-crawl-log-returns-error-on-the-crawler-could

https://social.technet.microsoft.com/Forums/office/en-US/f378c45f-fa8b-48f3-88bb-739f3cd27830/the-crawler-could-not-communicate-with-the-server-check-that-the-server-is-available-and-that-the?forum=sharepointadminprevious

Best Regards, 

Lisa Chen 


这篇关于抓取日志错误“未找到对象"的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆