简体   繁体   English

在单独的服务器场上搜索到网站集时,SharePoint托管属性出现问题

[英]SharePoint managed properties issue when search on separate farm to site collection

We're having problems with managed properties in a new SharePoint 2013 web application. 新的SharePoint 2013 Web应用程序中的托管属性存在问题。 The managed properties are being used to display metadata and for sorting, however the metadata isn't being displayed and we're getting the following error whenever we try to sort 托管属性用于显示元数据和进行排序,但是未显示元数据,并且在尝试排序时会出现以下错误

Property doesn't exist or is used in a manner inconsistent with schema settings.

I have seen this error before when the managed property in question weren't defined, or set to sortable/refinable. 在未定义托管属性或将其设置为可排序/可精炼之前,我已经看到此错误。 However, I can clearly see that this is not the case from the search schema and there are not errors in the Crawl Log. 但是,我可以清楚地看到,从搜索模式来看并非如此,并且抓取日志中没有错误。

After digging into the logs, all I can find is 深入日志后,我只能找到

Exception occured in scope Microsoft.Office.Server.Search.Query.SearchExecutor.ExecuteQueries. Exception=SortList

The application is being deployed into an integrated development environment, on a shared app farm. 该应用程序已部署到共享应用程序场中的集成开发环境中。 Also, we are using a separate farm for Search so the managed properties are created there. 另外,我们将单独的服务器场用于搜索,因此将在此处创建托管属性。 The application/managed properties worked as expected on a developers slice, however search was located on the same farm as the application. 应用程序/托管属性在开发人员切片上按预期工作,但是搜索与应用程序位于同一服务器场。

We have tried recreating the content source, numerous full crawls, verified the managed properties are set correctly but still getting the same problem. 我们尝试重新创建内容源,进行大量完全爬网,验证托管属性设置正确,但仍然遇到相同的问题。

Has anybody any suggestions? 有什么建议吗? Thanks in advance. 提前致谢。

So it appears that this was a bug from December CU/SP1 to the April CU. 因此看来,这是从12月CU / SP1到4月CU的错误。 Basically, there was an issue with the schema that could prevent new properties from actually getting added successfully. 基本上,模式存在问题,可能会阻止新属性实际成功添加。 The fix was first released in the May security update and is in the June CU as well. 该修复程序最初在5月的安全更新中发布,并且也在6月的CU中发布。 (If you are on the October 2013 or older CU, then the bug isn't present there.) (如果您使用的是2013年10月或更旧的CU,则该错误不存在。)

Getting the latest June Update, and running a full crawl has everything working as expected. 获取最新的June更新并运行完全爬网,一切正常。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM