How to delete Content Source in Sharepoint 2013 Search Service

I want to delete Default Content Source in Search
Service in SharePoint 2013 but delete button is disable?Please see the below image. Content Source Type=SharePoint Sites
How to do it?
If In Content Source type=Files than delete button enables but
not for the Content Source type=Sharepoint sites
Vishal Goyal

Hi,
try to remove it using powershell
$searchapp = Get-SPEnterpriseSearchServiceApplication "NameofSearchAPp"
Remove-SPEnterpriseSearchCrawlContentSource -SearchApplication $searchapp -Identity "Name"\Regards
Whenever you see a reply and if you think is helpful,Vote As Helpful! And whenever you see a reply being an answer to the question of the thread, click Mark As Answer

Similar Messages

How to properly create and configure SharePoint 2013 Search service with PowerShell?

Hello Forum,
I have installed SharePoint 2013 across three tier servers:
WFE Server (Of course, SharePoint is installed here. Bsically this is just a Web server)
APP Server (Of course, SharePoint is installed here + Central Admin + Service Apps).
SQL Server
I now want to create and configure the Search service, obviously on the APP Server, But of course the search functionality should work correctly on the WFE server to.
I want to do this via a proper PowerShell script. I found Spence Harbar's script on: (http://www.harbar.net/articles/sp2013mt.aspx), But it has three problems, and they are as follows:
1) Spence Harbar himself literally stated on his article that this script is for: "deploying on a single server farm", But what if I have three tier servers? Could anyone please help me out in suggesting the required tweaks in the
script?
2) By default Search uses the SP_Farm account, So, How can I change the script to use other dedicated account for the search service e.g. SP_SearchAcc ?
3) How can I modify the script to specify a default Search center?
4) Apart from all the three aforementioned point - Is the script missing anything?
I would greatly appreciate your inputs - Thanks !

the only differences are where you place the components. if you are doing a small server farm with a 1-1-1, most likely you just need to change the script so that you set the index and query processing component on the front end, but the others on
the app server. just a 2 second update... just keep in mind this will work, but I am making several assumptions without any knowledge of your farm, users, capabilities.
generally, there would be more of a breakout on the topology than that, but im guessing for this farm that you wont have dedicated search servers. also, a lot depends on # users (rps really), # items in index, size of VMs (RAM for query processing,
Disk for index, etc, etc), and making sure the topology works for your particular environment and needs.
if you want more detailed topology help, which aligns as closely as possible to "best practices" (not that those exist in SharePoint, go ahead and provide the total # users, average/peak RPS for search, current index size, content source types,
VM specs RAM, CPU, #/Size of drives, HA concerns/priority (obviously isn't, since only 1-1-1)
Christopher Webb | MCM: SharePoint 2010 | MCSM: SharePoint Charter | MCT | http://christophermichaelwebb.com

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

How can I force delete SharePoint 2013 search service?

I installed Search service using PowerShell. It failed. I tried to remove the service and only partially removed. Now when i try to remove it again it says I cannot login to the search database - the search database no longer exists. Is there
a way to force delete the service?

Get -SPServiceApplication
Grab the Search Service Application id – [for example] 30b15b57-6bec-46b5-990d-541d99bab53b
then use this
Stsadm -o deleteconfigurationobject -id 30b15b57-6bec-46b5-990d-541d99bab53b (Preferred over the next method of PowerShell)
this was working for me even the ps command failed (I had corrupted DB)
Martin

Sharepoint 2013 - Search service not working

We have set the search service application to crawl incrementally. The crawls are taking a long time. The content is not vast over the single farm but we do have a few sizable document libraries, lists and media assets. Suggestions as to what to check
again first? Screen shot of the search admin page.

Hi,
According to your post, my understanding is that Search service failed to work in SharePoint 2013.
The cause is that Accounts that are used by application pools or services are members of the Administrators group on the local computer.
I recommend to change the user account to a predefined account, or to a domain user account that is not a member of the Administrators group.
More information:
http://technet.microsoft.com/en-us/library/hh344224(v=office.15).aspx
http://alstechtips.blogspot.com/2013/12/health-analyzer-accounts-used-by.html
http://absolute-sharepoint.com/2013/01/sharepoint-2013-service-accounts-best-practices-explained.html
Best Regards,
Linda Li
Linda Li
TechNet Community Support

Can you refine people search results using a SharePoint 2013 search service application connected in SharePoint 2010?

We have an SP2010 farm which is now using some of the service applications from an SP2013 farm, including the search, managed metadata and user profile. This is part of an upgrade programme of work which will involve upgrading infrastructure and
then gradually the sites, and this is seen as one way to minimise the impact.
So, the SP2010 search results are being generated by the SP2013 which is indexing the SP2010 content. The initial results appear fine, however, the refiners in the people results for Job Title and Department are no longer working. We are receiving
a 404 page not found, even though the page is there as was working before.
If we compare the URL generated in SP2010 for refining results to an OOTB SP2013 search centre site, there is clearly a big difference to the format. Example below is where LastName is Smith and then refined where Department is HR.
SP2010 URL which now gives a 404 error:
http://intranet2010/search/pages/peopleresults.aspx?k=LastName%3Asmith&r=%22owstaxIdSPShDepartment%22%3D%23832e3479%2Dd168%2D4620%2Dac69%2D9b00a4c4205b%3A%22HR%22
OOTB SP2013 URL:
http://intranet2013/search/pages/peopleresults.aspx?k%3Asmith#Default=%7B%22k%22%3A%22smith%22%2C%22r%22%3A%5B%7B%22n%22%3A%22Department%22%2C%22t%22%3A%5B%22%5C%22%C7%82%C7%824335%5C%22%22%5D%2C%22o%22%3A%22and%22%2C%22m%22%3Anull%2C%22k%22%3Afalse%7D%5D%7D
I've looked at the URL decoded versions so can see how the query is built up.
Any ideas? Is this even possible?
Matt

All working now. Turns out there was an entry in the web.config which was causing issues.
<denyQueryStringSequences>
<add sequence="ID" />
</denyQueryStringSequences>
Seems IIS is denying something in the query string. We removed the whole section as was not needed.
http://www.iis.net/configreference/system.webserver/security/requestfiltering/denyquerystringsequences
Thanks to a colleague who spotted this; I would've never of thought to check the web.config for something like this.

How to add content source in office 365 ?

How to add content source in office 365 , where I can add find Manage Content Sources page to click on New Content Source LInk

You can't. Only sources available is what is already set up...which is SharePoint/OneDrive4B and Exchange via eDiscovery.
Thanks,
Mikael Svenson - Search Enthusiast
SharePoint MVP/MCPD/P-TSP - If you find an answer useful, please up-vote it.
http://techmikael.blogspot.com/
Author of
SharePoint Search Queries Explained and
Working with FAST Search Server 2010 for SharePoint

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.

Unable to open search service content sources from SharePoint

HI
unable to open search service content sources from SharePoint , I got this error in search server event viewer .
A database error occurred. Source: Microsoft SQL Server Native Client 10.0 Code: 1205 occurred 1 time(s) Description: Transaction (Process ID 66) was deadlocked
on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
Context: Application 'SP_SearchApp'
adil

Hi,
Based on the error message, I recommend to stop all the crawl process in SharePoint search service application by using PowerShell and then check the results:
http://blogs.technet.com/b/heyscriptingguy/archive/2010/09/28/how-to-use-sharepoint-2010-windows-powershell-cmdlets-to-manage-search-crawls.aspx
The deadlock error will occurs when there are too many overlapping crawls, so I recommend to schedule the crawl to not overlap in SharePoint and add more crawl components if needed.
http://blogs.msdn.com/b/sharepoint_strategery/archive/2014/02/10/sharepoint-search-and-deadlocks-in-sql-server.aspx
If above cannot work, please also check the ULS log and SQL server for detailed error messages.
Best regards.
Thanks
Victoria Xia
TechNet Community Support

How to delete a source system in BW?

Hello All!
Can anone please inform me about the procedure to delete a source system or inform me in which document i can find this information. Actually i wish to assing my newly installed BW3.5 system to a new logical system (i.e) its currently assigned to some other logical system where it has ME as default source system. to change the logical system we need to delete all the source systems in the old logical syste. So please explaing me how to delete the source system Myself(current BWsystem). there is no data and no data sources existing in the system its abosolutly fresh.
Thanking you for help in advance
with regards
Ashwin Kumar Gadi

Hello Roberto!
Thanks for ur response. But there bo such delete option available under the context menu for the source system for the Myself source(current BW). only change buton appears but when we click that it say changes are no posible. Is the any other way to delete it manually.
with regards
Ashwin

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.

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

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?

SharePoint server 2013 Search Service App on Windows server 2012 R2 not working

Hi all,
I installed SharePoint server 2013 on Windows server 2012 R2 using VirtualBox. I created a DC(domain controller) server with a domain set up on one VM and it has SQL server 2012 SP1 installed. Then SharePoint 2013 on another VM
was set up to access the DC server. Everything seems working except Search Service App which cannot be sucessfully set up. Creation process for Search service app says Successful and 4 search databases were created and look fine. But when I navigate
to search service app admin page, it gives error info:
System status: The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component '386f2cd6-47ca-4b3a-aeb5-d9116772ef16' in search application 'Search Service Application 1' is
in a good state and try again.
Search Application Topology: Unable to retrieve topology component health states. This may be because the admin component is not up and running.
From event viewer, I see following errors:
(1) Error From source: SharePoint Server
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
Reason: The object you are trying to create already exists. Try again using a different name.
Technical Support Details:
System.Runtime.InteropServices.COMException (0x80040D02): The object you are trying to create already exists. Try again using a different name.
   at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
   at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)
(2) Error From source: SharePoint Server Search
Could not access the Search database. A generic error occurred while trying to access the database to obtain the schema version info.
Context: Application '386f2cd6-47ca-4b3a-aeb5-d9116772ef16'
(3) Warning from source: SharePoint Server Search
A database error occurred. Source: .Net SqlClient Data Provider Code: 8169 occurred 0 time(s) Description: Error ordinal: 1 Message: Conversion failed when converting from a character string to uniqueidentifier., Class: 16, Number: 8169, State: 2
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
(4) Error From source: SharePoint Server
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
Reason: The gatherer application could not be mounted because the search administration database schema version does not match the expected backwards compatibility schema version. The database might not have been upgraded.
Technical Support Details:
System.Runtime.InteropServices.COMException (0xC0041235): The gatherer application could not be mounted because the search administration database schema version does not match the expected backwards compatibility schema version. The database might not have
been upgraded.
Since separate DC server and SharePoint server do not work, I installed SharePoint 2013 on DC server ( so DC server has everything on it now ) but it gives exactly same result. Later I installed SharePoint 2013 SP1 and still have the same problem
with Search Service app. I spent two weeks tried all suggestions available from Web and Google but SharePoint Search Service simply does not work. Config and other databases work but why Search Service has this issue seemingly related to search DB.
Could anybody please help out? You deserve a top SharePoint consultant award if you could find a solution. I am so frustrated and so tired by this issue.
Thanks a lot.

Hi,
According to your post, my understanding is that SharePoint server 2013 Search Service App did not work on Windows server 2012 R2.
Please make sure you configure Search Service Application correctly. You can refer to:Create and configure a Search service application in SharePoint Server 2013
I recommend to created new Search Service Application, and made a full crawl. Then assigned the new SSA as the default SSA for webapplications. Finnlay checked the issue doesnt occur now,
If all search related components now are online, to keep the enviroonment clean, you can delete the old SSA.
Thank you for your understanding.
Best Regards,
Linda Li
Linda Li
TechNet Community Support

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.

How to delete Content Source in Sharepoint 2013 Search Service

Similar Messages

Maybe you are looking for