KQL Query - Sharepoint 2013 Search - Filter by empty date value

Hey,
I'm using Microsoft.Office.Server.Search.Query.KeywordQuery class to query the search service. By using the following KQL query, I can get all the crawled items of a specific content type filtered by Expiration Date:
(ContentType:"MyContentType") (PublishingExpirationDateOWSDATE>=2013/08/07)
PublishingExpirationDateOWSDATE is of type Date (it's not the default metadata property that SP creates when you do a full crawl, since that one is of type text, i deleted and recreated it as date time). I just did this because i needed to be able to sort
the results by that value, and it was impossible when it was just text.
So, now my problem comes when i want to include those values where the PublishingExpirationDateOWSDATE > (today) or are emtpy (in other words, the not expired items).
I found no way of targeting the items where the date is empty. Is there some way? Some special syntax to get them?
I just come up with another idea, that would be having another managed property bound to the same crawled property of type "text", and just comparing that one to "". But i don't want to have the need of having to separate properties.
Is there some way?
Antonio Briones Northridge Systems C# .net developer for win and web forms. I work for

Hi Antonio,
Search does not create index of any field which is left empty. A query filtering data based on PublishingExpirationDateOWSDATE
> (today). Will give you all the records with date greater than today's date ignoring the time also. Records with date empty will not appear in your results.
You will not be able to achieve this with custom search results web part also.
Try CQWP.
Navish Rampal

Similar Messages

SharePoint 2013 Search: Instant Refinement of Multi-Value Properties with out clicking Apply

Hi All,
I will need help in modifying the Filter_Multivalue.htm file .
The default multivalue refinement behaves as step 1 & 2.
steps:1 When one configure a refinement as multi-value, the user is presented with the list of available filters with checkboxes
Step:2The user must select one or more checkboxes and then click on the Apply link. After they click on the Apply link, the results are refined by the selected filters but only the selected filters are presented:
Need solution for the below:
Need an Instant Refinement solution, all filters are displayed all of the time and when the user clicks on a checkbox, the results are instantly refined without the need to click on an Apply link.
Any one might have come a cross this scenairo , please share the code and details working steps.
Thanks in advance.
Regards,
ajay

Hi Ajay,
According to your description, my understanding is that you want to make the refinement of multi-value properties without clicking Apply.
I recommend to follow the steps in the link below to achieve the goal:
http://stevemannspath.blogspot.com/2013/07/sharepoint-2013-search-instant.html
With the Instant Refinement solution, all filters are displayed all of the time and when the user clicks on a checkbox, the results are instantly refined without the need to click on an Apply link.
Best regards.
Thanks
Victoria Xia
TechNet Community Support

If Condition in Keyword Query Language (SharePoint 2013 Search Results)

Hi All,
Can we have an "If" condition in Query text box in SharePoint 2013 Search results page. For example, i want to hide all list items whose
status is "HideItem" from appearing in search results?
I am trying this: {?{searchTerms} (contentclass:STS_ListItem -ListItemStatus:"HideItem")}
But, this hides all items like aspx pages, pdf's, docs and displays only list items.
Similarly, hide pages of some name like: AllItems.aspx, ViewDetails.aspx, AllAssets.aspx
{?{searchTerms} (contentclass:STS_ListItem_850 -filename:"AllItems.aspx")}
Any help would be great. Thanks in advance.

Thanks Steve. I found this solution after a bit of struggle :).
Also, date comparision is not working as expected.
{?{searchTerms} NOT(contentclass:STS_ListItem AND ListItemStatus:"HideItem" AND
PublishDate<{Today})} is not working and throwing syntax error.
I don't see any solid reference to KQL syntax except this msdn link.
Can you please suggest any good material on KQL syntax ?
Thank you once again.

Create Refinement topics for web application in SharePoint 2013 Search

Is there a way we can add available web application name in refinement panel in SharePoint 2013 search. there is a search called Enterprise search which is named as Everything, that search from all the web applications available. is there a way we can have
a search refinement panel which is the list of web applications so that it allows us to filter the results by web application.
can we add a refinement panel like below in SharePoint Search 2013
here is an image for
kukdai

Hi kukdai,
To use result source or query rule to distinguish search results, besides adding custom search vertical, you could also consider using result block:
http://blogs.technet.com/b/mspfe/archive/2013/02/01/how-query-rules-and-result-sources-can-be-used-to-customize-search-results.aspx
http://www.sharepoint2013.me/Blog/Post/261/SharePoint-2013---Create-and-display-results-blocks
Quote:
In SharePoint, result block will display the search results as a group. We can promote result block depending on the query condition as specific result. While configuring query conditions for results block, we can use query variables. We can specify query
variables as place holders for unknown values in SharePoint query.
Then we can use Path in query rule to divide search results into several web applications.
Regards,
Rebecca Tu
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Sharepoint 2013 search component best practice

hi
With a big SharePoint 2013 farm:
2 WFE
2 App server
2 Search App server (havent set up these servers yet)
What would the best way to divide the search componment between the two serarch app servers?
Crawl component
Crawls content sources to collect crawled properties and metadata from crawled items and sends this information to the content processing component.
Content processing component
Transforms the crawled items and sends them to the index component. This component also maps crawled properties to managed properties.
Analytics processing component
Carries out search analytics and usage analytics.
Index component
Receives the processed items from the content processing component and writes them to the search index. This component also handles incoming queries, retrieves information from the search index and sends back the
result set to the query processing component.
Query processing component
Analyzes incoming queries. This helps optimize precision, recall and relevance. The queries are sent to the index component, which returns a set of search results for the query.
Search administration component
Runs the system processes for search, and adds and initializes new instances of search components.
If you ignore the need for redunancy (we may add another 2 search app servers for that later).
brgs
Bjorn

Hi Bjorn,
According to your description, my understanding is that you want to deploy the search components in two search app servers.
It depends on how many search service applications you need and the size of your environment.
Here is a link about how to configure topology for one search service application with multiple search components across 2 servers for redundancy and performance:
http://blogs.msdn.com/b/chandru/archive/2013/02/19/sharepoint-2013-configuring-search-service-application-and-topology-using-powershell.aspx
You can also run the Query Processing component in web front server and run the other components in the search servers or application servers.
Please refer to the link below:
http://blogs.technet.com/b/meamcs/archive/2013/04/09/configuring-sharepoint-2013-search-topology.aspx?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+yahoo%2FZfiM+(Team+blog+of+MCS+%40+Middle+East+and+Africa)
Best regards.
Thanks
Victoria Xia
TechNet Community Support

Autocomplete is not working for Sharepoint 2013 search box.

I added the below code in cewp in sharepoint 2010 and autocomplete worked fine.
http://sharesilver.wordpress.com/2011/11/26/auto-suggestioncomplete-in-sharepoint-search-text-box-with-jquery-like-in-google-part-1/#comment-605
when i added this code in sharepoint 2013 by changing the searchbox class name in the code. it is not working. why ??
Sharepoint 2010 searchbox class name ="ms-sbplain"
what is Sharepoint 2013 searchbox class name ?? i added "ms-textLarge" as class name but it didn't work.
Thanks in advance.
M.M

Hi M.M,
The class for SharePoint 2013 Search box input element is as follow, please check if it is what you want.
class="ms-textLarge ms-srch-sbLarge-fullWidth ms-srch-sb-prompt ms-helperText"
The project code you are using is updated in codeplex, and the query suggestions (similar to this autocomplete) is an OOB feature in SharePoint 2013 enterprise verison, you can take a look.
http://spautosuggestion.codeplex.com/
http://technet.microsoft.com/en-us/library/jj721441.aspx
Thanks
Daniel Yang
TechNet Community Support

HELP: SharePoint 2013 Search NOT working - unable to resolve

I'm a newbie still and don't understand how to read the log to solve this problem. I haven't been able to get search working since deployment.
************* Log Below ***********************
Exception occured in scope Microsoft.Office.Server.Search.Query.SearchExecutor.ExecuteQueries. Exception=Microsoft.Office.Server.Search.Query.InternalQueryErrorException: Search has encountered a problem that prevents results from being returned. If
the issue persists, please contact your administrator.
at Microsoft.Office.Server.Search.Administration.SearchServiceApplicationProxy.ThrowGenericQueryException(String operationName)
at Microsoft.Office.Server.Search.Administration.SearchServiceApplicationProxy.DoSpLoadBalancedUriWsOp[T](WebServiceBackedOperation`1 webServiceCall, Int32 timeoutInMilliseconds, Int32 wcfTimeoutInMilliseconds, String operationName)
at Microsoft.Office.Server.Search.Administration.SearchServiceApplicationProxy.DoWebServiceBackedOperation[T](String operationName, Int32 timeoutInMilliseconds, Int32 wcfTimeoutInMilliseconds, WebServiceBackedOperation`1 webServiceCall)
at Microsoft.Office.Server.Search.Administration.SearchServiceApplicationProxy.Execute(QueryProperties properties)
at Microsoft.Office.Server.Search.Query.Query.ExecuteQuery()
at Microsoft.Office.Server.Search.Query.SearchExecutor.ExecuteQueryInternal(Query query)
at Microsoft.Office.Server.Search.Query.SearchExecutor.ExecuteQuery(Query query)
at Microsoft.Office.Server.Search.Query.SearchExecutor.ExecuteQueries(Dictionary`2 queries, Boolean handleExceptions)
at Microsoft.Office.Server.Search.Query.SearchExecutor.<>c__DisplayClass16.<ExecuteQueries_Client>b__14()
at Microsoft.Office.Server.Search.Query.SearchExecutor.RunWithRemoteAPIsPermission[T](Func`1 f)
at Microsoft.Office.Server.Search.Query.SearchExecutor.ExecuteQueries_Client(String[] queryIds, Query[] queries, Boolean handleExceptions)
at Microsoft.Office.Server.Search.Query.SearchExecutorServerStub.InvokeMethod(Object target, String methodName, XmlNodeList xmlargs, ProxyContext proxyContext, Boolean& isVoid)
at Microsoft.SharePoint.Client.ServerStub.InvokeMethodWithMonitoredScope(Object target, String methodName, XmlNodeList args, ProxyContext proxyContext, Boolean& isVoid)

Hi cagman,
Please make sure Search Host Controller Service, Search Query and Site Settings Service, SharePoint Server Search are started on manange services on server.
Then check the Search service application, and make sure search application topology is ok.
Then reset Index, and run a full crawl. After crawling, search again, compare the result.
In addition, here are some similar posts, please check if they are useful for you:
http://sp-vinod.blogspot.jp/2014/02/getting-results-failed.html
http://williamvanstrien.blogspot.jp/2014/06/sharepoint-2013-search.html
Thanks,
Wendy
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Bypass content-based format detection so I can use a custom iFilter in Sharepoint 2013 Search

Can I get SharePoint 2013 Search to bypass the content-based format detection and use the file extension to determine the format (and therefore the format handler so that I can use a customer iFilter)?
We have a proprietary file format which uses xml, and we use a specific filename extension to indicate the type of file. We have a custom iFilter to parse the file, because we only want some of the content to be indexed. The iFilter works with
Windows Search. I’m now trying to use our custom iFilter to search the same files with SharePoint 2013. SharePoint 2013 Search appears to determine a file’s format from its content and not from its file extension (I have confirmed this by changing
the extensions of .docx and .txt files). SharePoint 2013 search appears to use the built-in XML format handler to index our proprietary files. Can I get SharePoint 2013 Search to bypass the content-based format detection and use the file extension
to determine the format (and therefore the format handler)? I think SharePoint 2010 may allow this, but I can’t find out if/how it is done in SharePoint 2013.
I understand that built-in format handlers can’t be replaced by custom iFilters, but I don’t want to replace the XML format handler for .xml files.

Hi jeh271,
quite interesting, because as i know iPersistStream should be installed when you need to use ifilter when using windows search.
just curious, if you also restart the spsearchhostcontroller?
as i know the search should have the content-based format,we cant bypass it, if we bypass it, then it may broke.
i saw some thread about this before:
http://social.technet.microsoft.com/Forums/sharepoint/en-US/944e6878-a7f0-4c0e-98b7-a7fb9faeef1b/bcs-connector-and-mimetypefield
ifilter example:
http://msdn.microsoft.com/en-us/library/hh694268(v=office.14).aspx
last time i did this, seems similar issue:
• The custom iFilter is working in SP 2010 but when we followed the same process of registering the iFilter in SP 2013, it was not working.
• So, we knew that we were some missing some extra step in registering the filter in SP 2013.
• Finally, we involved the Product group and we found out that we need to run an extra PowerShell commandlet apart from following the steps to register it in SP 2010 (given in this link:- http://msdn.microsoft.com/en-us/library/hh694268(v=office.14).aspx )
• We ran the commandlet described here in this article http://technet.microsoft.com/en-us/library/jj219556.aspx.
• The New-SPEnterpriseSearchFileFormat cmdlet adds a new file format and a corresponding file name extension to the search parsing system. This binds the file format to a filter-based format handler in the search parsing system. Thus, the search parsing system can only parse the new file format if the user has installed a corresponding filter-based format handler, an IFilter, for the new file format. If the installed IFilter registers more than one file name extension, the user must use the New-SPEnterpriseSearchFileFormat cmdlet to add a new file format to the parsing system for each of these file name extensions. The user must also ensure that the file name extension of the new file format is a member of the file-type inclusion list. The file-type inclusion list specifies which files that are crawled, based on their file name extensions. The system will only consider the new file format after a restart of the content processing components
• The example for our scenario would be something like this:-
New-SPEnterpriseSearchFileFormat -SearchApplication $ssa -FormatId dwg -FormatName DWGFiles -MimeType application/dwg
• Then, we restarted the SharePoint Search Host controller service on the machine where you have installed the iFilter and this resolved our issue and we were able to successfully search with .dwg files using the custom iFilter.
i am not quite sure if search treating your file as an XML file, if it is true, perhaps you can check this xmlmapper:http://msdn.microsoft.com/en-us/library/ff795813(v=office.14).aspx
Regards,
Aries
Microsoft Online Community Support
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Stemming not working on SharePoint 2013 Search

We have SharePoint search enabled on our farm. There are close to 20 million items in the farm. Looking through the logs and user's feedback, we were able to find that the stemming feature is not actually working
When i search for "Order" i couldnt see a document whose title contains ordering in the search result.
This is horrible. Am i missing any thing??
Sreeharsha Alagani | MCTS Sharepoint 2010 |
Linkedin | Blog

Hi,
Stemming means that nouns and adjectives in a query are expanded to different possible inflections. Stemming essentially performs searches for words that share the same stem. Stemming in SharePoint 2013 is enabled by default.
You can export your Search Result Web Part and Open the Web Part in a text editor, then verify whether the value for EnableStemming is ture.
Reference:
http://stevemannspath.blogspot.com/2013/04/stemming-in-sharepoint-2013-search.html
https://social.technet.microsoft.com/Forums/en-US/1e507083-0664-4c3f-b49d-b785a11960f5/fast-search-stemming-not-working?forum=sharepointadminprevious
Best Regards,
Eric
Eric Tao
TechNet Community Support

Office web Apps preview of SharePoint 2010 source in SharePoint 2013 search results

Hi Team,
We have crawled SharePoint 2010 source in SharePoint 2013 and able to get results successfully. Now our requirement is to show Office Web Apps previes of 2010 documents in 2013 search results.
Any guidance on this please.
Thanks,
Manjeera

Hi,
Take a look at this blog post on how to do this: http://blogs.msdn.com/b/murads/archive/2012/10/11/utilizing-web-apps-2010-to-get-powerpoint-previews-of-sharepoint-2010-content-from-sharepoint-2013-search.aspx
Thanks,
Mikael Svenson
Search Enthusiast - SharePoint MVP/MCT/MCPD - If you find an answer useful, please up-vote it.
http://techmikael.blogspot.com/
Author of Working with FAST Search Server 2010 for SharePoint

Sharepoint 2013 search error - The search application 'Search Service Application 1' on server is not provisioned.Confirm that the Microsoft SharePoint Foundation Timer service and Central Administration service are running on the server.

Hi All,
I'm getting the below error in My SHarepoint 2013 search Administration page.
Crawler background activity - The search application 'Search Service Application 1' on server "" is not provisioned. Confirm that the Microsoft SharePoint Foundation Timer service and Central Administration service are running
on the server.
and when i click on Crawl Log and content source
it throws the below error
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
When i check the search status
Get-SPEnterpriseSearchServiceInstance, it shows all the components are online.
As of now search service application is online and search is working.But not sure why it throws the above error.
I have restarted timer service,search service in services.msc and cleared the sharepoint cache as well.
But no luck,This is happening in my prodcution environment.
Any help will be greatly appreciated.
There are the logs i have found
05/23/2014 13:03:22.71 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation Logging Correlation Data xmnv Medium Name=Request (GET:http://dca-app-617:90/_admin/search/listcontentsources.aspx?appid=e830c1b3%2Dc3e4%2D4097%2D85fd%2Daa5248346d2e) d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.71 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation Authentication Authorization agb9s Medium Non-OAuth request. IsAuthenticated=True, UserIdentityName=, ClaimsCount=0 d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.73 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation Logging Correlation Data xmnv Medium Site=/ d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.79 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Server Search Administration djs2 High [Forced due to logging gap, cached @ 05/23/2014 13:03:22.76, Original Level: VerboseEx] {0} d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.79 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Server Database 8acb High [Forced due to logging gap, Original Level: VerboseEx] Reverting to process identity d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.80 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Server Search Administration djj1 High Unable to find application 'b9c8106c-c7ed-4eb3-96c9-ae1881ffb695' d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.82 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Server Search Administration djj1 High Unable to find application 'b9c8106c-c7ed-4eb3-96c9-ae1881ffb695' d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.82 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation General 8nca Medium Application error when access /_admin/search/listcontentsources.aspx, Error=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.   at Microsoft.Office.Server.Search.Internal.UI.SearchCentralAdminPageBase.ErrorHandler(Object
sender, EventArgs e)     at Microsoft.Office.Server.Search.Internal.UI.SearchCentralAdminPageBase.OnError(EventArgs e)     at System.Web.UI.Page.HandleError(Exception e)     at System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)     at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)     at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)     at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()     at System.Web.HttpApplication.ExecuteStep(IExecutionStep
step, Boolean& completedSynchronously) d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.82 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation Runtime tkau Unexpected Microsoft.SharePoint.SPException: 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.    at Microsoft.Office.Server.Search.Internal.UI.SearchCentralAdminPageBase.ErrorHandler(Object sender, EventArgs e)
at Microsoft.Office.Server.Search.Internal.UI.SearchCentralAdminPageBase.OnError(EventArgs e)     at System.Web.UI.Page.HandleError(Exception e)     at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint,
Boolean includeStagesAfterAsyncPoint)     at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)     at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)     at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()     at System.Web.HttpApplication.ExecuteStep(IExecutionStep
step, Boolean& completedSynchronously) d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.82 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation General ajlz0 High Getting Error Message for Exception Microsoft.SharePoint.SPException: 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.     at Microsoft.Office.Server.Search.Internal.UI.SearchCentralAdminPageBase.ErrorHandler(Object
sender, EventArgs e)     at Microsoft.Office.Server.Search.Internal.UI.SearchCentralAdminPageBase.OnError(EventArgs e)     at System.Web.UI.Page.HandleError(Exception e)     at System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)     at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)     at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)     at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()     at System.Web.HttpApplication.ExecuteStep(IExecutionStep
step, Boolean& completedSynchronously) d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.82 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation General aat87 Monitorable  d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.82 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation DistributedCache ah24q Unexpected SPDistributedCachePointerWrapper::InitializeDataCacheFactory - No cache hosts are present in the farm. d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.82 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation DistributedCache ah24w Unexpected Unexpected Exception in SPDistributedCachePointerWrapper::InitializeDataCacheFactory for usage 'DistributedViewStateCache'
- Exception 'System.InvalidOperationException: SPDistributedCachePointerWrapper::InitializeDataCacheFactory - No cache hosts present in the farm.     at Microsoft.SharePoint.DistributedCaching.SPDistributedCachePointerWrapper.InitializeDataCacheFactory()'. d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.82 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation General ajb4s Monitorable ViewStateLog: Failed to write to the velocity cache:
http://dca-app-617:90/_admin/search/listcontentsources.aspx?appid=e830c1b3-c3e4-4097-85fd-aa5248346d2e d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.82 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (Request (GET:http://dca-app-617:90/_admin/search/listcontentsources.aspx?appid=e830c1b3%2Dc3e4%2D4097%2D85fd%2Daa5248346d2e)).
Execution Time=109.695855199474 d4c6939c-b10d-4000-6d95-14caeefe67df
Anil Loka

Please try below mentioned steps:
1. Central Administration > Monitoring > Review job definitions > Look for following timer job "Application Server Administration Service Timer Job" > Disable
2. Then open windows administrative services (services.msc), stop SharePoint Timer Service
3. Clear SharePoint Timer configuration cache by following steps mentioned in below blog:
http://blogs.msdn.com/b/jamesway/archive/2011/05/23/sharepoint-2010-clearing-the-configuration-cache.aspx
4. Start SharePoint Timer Service and give it a few seconds so that the new XML files from the location you deleted then are re-populated.
5.Central Administration > Monitoring > Review job definitions > Look for following timer job "Application Server Administration Service" Timer Job > Enable
Please ensure that you mark a question as Answered once you receive a satisfactory response.

Trying to link SharePoint 2010 Enterprise with SharePoint 2013 Search Server raises error

Hi,
I am currently working for a multinational who has SharePoint 2010 Enterprise Edition installed, 2 WFE SERVERS, 3 APP SERVERS, 1 DB SERVER. They also installed SharePoint 2013 Exterprise recently.
   Microsoft have recently come in and set up the SharePoint 2013 Search Server to crawl content in SharePoint 2010 as the replacement search to SharePoint 2010 Search. So they have gone through process of certificates and permissions
setups I guess. I was told it was working, but recently failed. When I type in the search box on a web site for SharePoint 2010 I get the message:
         The search request was unable to connect to the Search Service.
I checked the Event log and the Critical error (in Task Category:Timer) I get is the notorious:
The Execute method of job definition Microsoft.Office.Server.Search.Administration.CrawlReportJobDefinition (ID fa882704-80d9-415b-9b9d-eae5e9bdefd4) threw an exception. More information is included below.
        The search service is not able to connect to the machine that hosts the administration
        component. Verify that the administration component 'e9172a05-22ec-4904-9508-
        e5431a180c2b' in search application 'Search_Service_Application' is in a good state and
        try again.
I know administration component is the crawler. I am assuming this is permissions.
The SharePoint 2013 Search Server is picking up SharePoint 2010 site collections items fine i.e. The SharePoint 2013 search shows items from 2010 as expected.
On the SharePoint 2010 central admin box the search service enabled and running (checked with powershell). (SharePoint Server Search 14)
The Search Service id: e9172a05-22ec-4904-9508-e5432a180c2b
I also get the message in event log for gatherer on SharePoint 2010 CA and Search Server:
       Could not access the Search database. A generic error occurred while trying to access the database to obtain
       the schema version info.
       Context: Application 'e9172a05-22ec-4904-9508-e5431a180c2b'
Details:
            (0x80040e09)
Is this permissions to delete something from crawler??????
I would appreciate if someone could help on this. I have tried to be as concise as possible.
Thanks.
John.

It was a case that someone had fiddled with the Service App Associations. Hadn't ticked SharePoint 2013 search. Was still point at 2010. Thanks.
The SharePoint 2013 Search works correctly for SharePoint 2010.
Can someone confirm that the Search Service Application on SharePoint 2010 still needs to exist and hence SharePoint Server Search 14 Service still needs to be running? I am guessing it would as you search from 2010 interface not 2013. I am getting a critical
error in the Event Viewer:
CrawlReportJobDefinition (Id <SharePoint 2010 Crawler>)
The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component <crawler id> in search application "Search Service Application" is in a good state and try
again.
I think this is related to the fact we have SharePoint 2013 doing the search instead of 2010.
Any ideas?
John.

SharePoint 2013 Search - Zip - Parser server ran out of memory - Processing this item failed because of a IFilter parser error

Moving content databases from 2010 to 2013 August CU. Have 7 databases attached and ready to go, all the content is crawled successfully except zip files. Getting errors such as
Processing this item failed because of a IFilter parser error. ( Error parsing document 'http://sharepoint/file1.zip'. Error loading IFilter for extension '.zip' (Error code is 0x80CB4204). The function encountered an unknown error.; ; SearchID = 7A541F21-1CD3-4300-A95C-7E2A67B2563C
Processing this item failed because the parser server ran out of memory. ( Error parsing document 'http://sharepoint/file2.zip'. Document failed to be processed. It probably crashed the server.; ; SearchID = 91B5D685-1C1A-4C43-9505-DA5414E40169 )
SharePoint 2013 in a single instance out-of-the-box. Didn't install custom iFilters as 2013 supports zip. No other extensions have this issue. Range in file size from 60-90MB per zip. They contain mp3 files. I can download and unzip the file as needed.
Should I care that the index isn't being populated with these items since they contain no metadata? I am thinking I should just omit these from the crawl.

This issue came back up for me as my results aren't displaying since this data is not part of the search index.
Curious if anyone knows of a way to increase the parser server memory in SharePoint 2013 search?
http://sharepoint/materials-ca/HPSActiveCDs/Votrevieprofessionnelleetvotrecarrireenregistrement.zip
Processing this item failed because the parser server ran out of memory. ( Error parsing document 'http://sharepoint/materials-ca/HPSActiveCDs/Votrevieprofessionnelleetvotrecarrireenregistrement.zip'. Document failed to be processed. It probably crashed the
server.; ; SearchID = 097AE4B0-9EB0-4AEC-AECE-AEFA631D4AA6 )
http://sharepoint/materials-ca/HPSActiveCDs/Travaillerauseindunequipemultignrationnelle.zip
Processing this item failed because of a IFilter parser error. ( Error parsing document 'http://sharepoint/materials-ca/HPSActiveCDs/Travaillerauseindunequipemultignrationnelle.zip'. Error loading IFilter for extension '.zip' (Error code is 0x80CB4204). The
function encountered an unknown error.; ; SearchID = 4A0C99B1-CF44-4C8B-A6FF-E42309F97B72 )

Office Web Apps - Preview Sharepoint 2010 documents in Sharepoint 2013 Search Results

Hi,
We have a Sharepoint 2013 search site collection. The content sources for the Search service application includes some Sharepoint 2010 sites. We also have Office Web Apps server deployed. When searching for documents, the OWA preview works for all the document
in local sharepoint 2013 farm. However document preview doesn't work for documents in the sharepoint 2010 farm.
Any idea why this happens?
Regards,
Muthu

Could you please elaborate more on open url / please give us some syntax how to use that is display template?
When we use open url do we still need to install office webapps in the 2010 environment?

Office Web Apps - Preview Sharepoint 2010 documents in Sharepoint 2013 Search Results...again

Hi,
I found a thread in this forum With an answere to a similiar question here:
http://social.technet.microsoft.com/Forums/en-US/28bc1e27-4a65-4c61-9b3e-cb9dad17f779/office-web-apps-preview-sharepoint-2010-documents-in-sharepoint-2013-search-results?forum=sharepointsearch&prof=required
...With the answere:
"OWA uses an access token to talk to SharePoint 2013. It cannot use this when talking to 2010. In order to work with 2010, you have to create a custom display template that converts the file url to an openurl link. "
BUT...
may anyone give more information how to do this?
Links to articles? Links to description and samples?
jik

Hi,
According to your description, my understanding is that you want to preview documents from SharePoint 2010 in search results in SharePoint 2013.
Per my knowledge, the Office Web Apps is configured to work with SharePoint 2013, so it will not work with documents in SharePoint 2010.
I recommend to configure Office Web Apps to work with SharePoint 2010
and make sure that documents can be previewed in SharePoint 2010 using Office Web Apps to see if the documents can be previewed in SharePoint 2013 search result.
http://technet.microsoft.com/en-us/library/ff431687(v=office.14).aspx
Best regards.
Thanks
Victoria Xia
TechNet Community Support

KQL Query - Sharepoint 2013 Search - Filter by empty date value

Similar Messages

Maybe you are looking for