Sharepoint foundation 2013 Search Service Application.

Hi all,
I want to configure search application for sharepoint foundation 2013. I have followed some of the web links.
But did not get success. Can you please provide me the working example of how to configure search application and run the crawl. And make sure the search is working correctly.
Thanks  in advance for help.

Hi Vishwajeet,
According to your description, my understanding is that you want to configure SharePoint Foundation 2013 Search service application.
In SharePoint Foundation 2013, we cannot add the Search Service to SharePoint Foundation 2013 from the Central Administration GUI after selecting a manual configuration method. It seems that the ONLY way you can add the Search Service to SharePoint Foundation
2013 is by using the SharePoint Configuration Wizard.
More information, please refer to the link:
http://blog.ciaops.com/2012/12/search-service-on-foundation-2013.html
Best Regards,
Wendy
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Wendy Li
TechNet Community Support

Similar Messages

  • Sharepoint foundation 2013 search service crawl log

    Hi all,
    Whenever I try to open the crawl log in sharepoint foundation 2013 I am getting the following error. The error says nothing about the reason of failure to open the log.
    If just shows the co-relation ID in technical details.
    Correlation ID: d85cd49c-18f6-509e-ca23-13f39afa5192 (while trying to access the Crawl log)
    Correlation ID: e85bd49c-e836-509e-ca23-1a3f0ece8c28 (while trying to access the Content source)
    I searched a lot on the net but not able to find any solution to this.
    Can you please help me
    Thanks.

    Can you please share details of this Correlation ID from ULS logs
    http://itfreesupport.com/2014/12/sharepoint-2013-2010-uls-logging-to-troubleshoot/
    If this helped you resolve your issue, please mark it Answered. You can reach me through http://itfreesupport.com/

  • SharePoint Foundation 2013 search service crawl error

    Hi all,
    When I try to view the Crawl log of Search Service Application I am getting error something like below:-
    I tried to figure out why this is happening but could not find the error details related to above Correlation ID.
    Can you please help me & guide me in right direction. I am clueless how to fix this issue. Yesterday it was working  fine but somehow it stopped working today and it even does not display the Crawl log. So it has become tough at least for me to
    fix it.
    Thanks for help.

    Did you try a using the
    Merge-SPLogFile cmdlet to retrieve the events that use this correlation ID?
    Merge-SPLogFile -Path ".\example.log" -Correlation "0467d49c-c872-509e-ca23-16445ea822d4"
    You can also check out my blog post, An even better way to get the real SharePoint error from the ULS logs which describes the
    process for using Merge-SPLogFile
    Jason Warren
    @jaspnwarren
    jasonwarren.ca
    habaneroconsulting.com/Insights

  • 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

  • SharePoint Foundation 2013 - Search Configuration Issue - 2 App Servers and 2 Front-End Servers

    Hi, 
    We have a SharePoint Foundation 2013 with SP1 Environment. 
    In that, we have 2 Front-End Servers and 2 App Servers. In the Front-End Servers, the Search Service is stopped and is in Disabled state and in the 2 App Servers in One App Server, Search is Online and in another Search is Starting but goes to Stopped sooon
    after.
    Originally, we had only 1 App Server and we were running our Search Service and Search Service Application in that. Now since the index location became full and we were unable to increase the drive there, we added one more App Server and now the issue is
    Search is not properly getting configured in either of these App servers. What we want to do is run Search only in the new App Server, because we have a lot of storage space for Index locations here, but in the older App Server, not run Search at all.  We
    tried keeping the Search Service disabled and ran the below PowerShell Scripts, but none of the ones are working. These scripts are creating the Search Service Application, but the error of "Admin Component is not Online", "Could not connect
    to the machine hosting SharePoint 2013 admin component" is coming up. 
    http://www.funwithsharepoint.com/provision-search-for-sharepoint-foundation-2013-using-powershell-with-clean-db-names/
    http://blog.falchionconsulting.com/index.php/2013/02/provisioning-search-on-sharepoint-2013-foundation-using-powershell/
    http://blog.ciaops.com/2012/12/search-service-on-foundation-2013.html
    Can I get some help please?
    Karthick S

    Hi Karthick,
    For your issue, could you provide the
    detail error message of ULS log  to determine the exact cause of the error?
    For SharePoint 2013, by default, ULS log is at      
    C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS
    For troubleshooting your issue,  you can try to run the SharePoint Products Configuration Wizard on your WFE servers and run the script for configuring the search service on SharePoint
    Foundation:
    [string]$farmAcct = "DOMAIN\service_Account"
    [string]$serviceAppName = "Search Service Application"
    Function WriteLine
    Write-Host -ForegroundColor White "--------------------------------------------------------------"
    Function ActivateAndConfigureSearchService
    Try
    # Based on this script : http://blog.falchionconsulting.com/index.php/2013/02/provisioning-search-on-sharepoint-2013-foundation-using-powershell/
    Write-Host -ForegroundColor White " --> Configure the SharePoint Foundation Search Service -", $env:computername
    Start-SPEnterpriseSearchServiceInstance $env:computername
    Start-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance $env:computername
    $appPool = Get-SPManagedAccount -Identity $farmAcct
    New-SPServiceApplicationPool -Name SeachApplication_AppPool -Account $appPool -Verbose
    $saAppPool = Get-SPServiceApplicationPool -Identity SeachApplication_AppPool
    $svcPool = $saAppPool
    $adminPool = $saAppPool
    $searchServiceInstance = Get-SPEnterpriseSearchServiceInstance $env:computername
    $searchService = $searchServiceInstance.Service
    $bindings = @("InvokeMethod", "NonPublic", "Instance")
    $types = @([string],
    [Type],
    [Microsoft.SharePoint.Administration.SPIisWebServiceApplicationPool],
    [Microsoft.SharePoint.Administration.SPIisWebServiceApplicationPool])
    $values = @($serviceAppName,
    [Microsoft.Office.Server.Search.Administration.SearchServiceApplication],
    [Microsoft.SharePoint.Administration.SPIisWebServiceApplicationPool]$svcPool,
    [Microsoft.SharePoint.Administration.SPIisWebServiceApplicationPool]$adminPool)
    $methodInfo = $searchService.GetType().GetMethod("CreateApplicationWithDefaultTopology", $bindings, $null, $types, $null)
    $searchServiceApp = $methodInfo.Invoke($searchService, $values)
    $searchProxy = New-SPEnterpriseSearchServiceApplicationProxy -Name "$serviceAppName - Proxy" -SearchApplication $searchServiceApp
    $searchServiceApp.Provision()
    catch [system.exception]
    Write-Host -ForegroundColor Yellow " ->> Activate And Configure Search Service caught a system exception"
    Write-Host -ForegroundColor Red "Exception Message:", $_.Exception.ToString()
    finally
    WriteLine
    ActivateAndConfigureSearchService
    Reference:
    https://sharepointpsscripts.codeplex.com/releases/view/112556
    Thanks,
    Eric
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected].
    Eric Tao
    TechNet Community Support

  • Team Foundation Server 2013 with SharePoint Foundation 2013 - Search not available?

    Hello,
    we installed a TFS 2013  and let it deploy SharePoint Foundation on the same server. We are now faced with the fact that search in the teamsites is not working. I tried to get that search service up and running in a number of ways but it appears
    as if there's no search service at all.
    I have seen all the blogs where people are explaining how to provision a search service application for SharePoint Foundation but none of these ways work.
    So, my question... is it possible to get it working?
    PS. Please don't advice to post this on the TFS forum... I'm coming from there. They just closed my question as answered with the advice to post it in the SharePoint forum.
    TIA,
    Bart

    Well,
    When you go to the Search Settings in the Site Actions menu of a site, a message is displayed that there's no search Service. Which is kind of normal since there's no Search Service Application provisioned.
    When I go to Central Administration => Services on Server => There's no Search Service.
    When I go to Central Administration and I run the configuration wizard, there's no search service application to be provisioned.
    There's a Search Administration section in the General Settings but it only displays the upper section. The lower section (with the Search Service Application information) just gives me nothing. An animated loading icon.
    I tried to provision the services with psconfig (psconfig -cmd services -install) but there's still no search service to be found anywhere. After this, I do have a Search Host Controller service but when I try to start it in Central Administration, it just
    gives me an error.
    I'm starting to think it's not a full SharePount Foundation which is shipped with TFS.
    The only thing we want to achieve is that a user can search for a document he uploads in a team site which is created by TFS. Seems not possible... unless I'm missing something here.

  • SharePoint foundation 2013 Search is not working

    Hi, Search was working 3 days back, but today its not working. So
    1. I Recreated Search Service Application
    2. Created Content Source and set full crawl.
    3. And service application is associated to the web application also.
    4. All Application pool id are running.
    5. Created Search Site collection, even though search is not working.
    The error message i got was shown below. How to resolve this issue. An help/thoughts.

    Try to use word Home in search
    Do we see site getting crawl in crawl logs
     Navigate to the site for which you want to control the Web Parts in search results.
    Click Site Actions, and then click Site Settings.
    Under Site Administration, click Search and offline availability.
    In the Indexing ASPX Page Content section, under
    This site does not contain fine-grained permissions. Specify the site’s ASPX page indexing behavior , 
    Always index all Web Parts on this site
    http://office.microsoft.com/en-in/sharepoint-server-help/enable-content-to-be-searchable-HA010379092.aspx

  • 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.

  • Sharepoint Foundation 2010 - Search service cannot start

    Hi,
    I'm trying to start the Search Service on SharePoint Foundation 2010 SP2, but I get the following error:
    Could not access the Search administration database. A generic error occurred while trying to access the database to obtain the schema version info.
    However the search database is well created during the process and I've checked that Shared Memory is enabled for SQL Native Client.
    Can you please suggest me on this
    Thanks

    Hi
    Alemaitre,
    If Shared Memory is enabled can you try below article
    http://svengillis.blogspot.com/2011/09/could-not-access-search-administration.html
    http://blog.arjanfraaij.com/2012/06/could-not-access-search-administration.html
    or if this is the problem after installing any SP / CU then make sure you have successfully ran PSConfig on all servers
    Let us know your results, thanks
    Regards,
    Pratik Vyas | SharePoint Consultant |
    http://sharepointpratik.blogspot.com
    Posting is provided AS IS with no warranties, and confers no rights
    Please remember to click Mark As Answer if a post solves your problem or
    Vote As Helpful if it was useful.

  • Do we need separate Unattended service account for each SharePoint Server 2013 BI service applications?

    SharePoint 2013 - I'm planning to use 'unattended service account' method of Secure Store Service - for Excel, Performance Point and Visio services. I'm about to create Active directory accounts for them.
    Question: Do we need separate Active directory accounts for each service
    DomainName\ExcelUnattendedAccount
    DomainName\PPSUnattendedAccount
    DomainName\VisioUnattendedAccount
    (or)
    Can I have just one Active Directory account DomainName\SharePointUnattendedAccount ?
    Are there any drawbacks having a single account? Any best practice around this? For all the three services the data sources are going to be the same. 
    Subash.S

    Security is the only reason you would separate accounts (as these accounts must have access to the source data). There should be no other drawbacks.
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • Sharepoint Server 2013 Search Issue

    Hi,
    running Sharepoint server 2013. search service application is not working properly. getting the below error message. 
    "Unable to retrieve topology component health states. This may be because the admin component is not up and running"
    we have 2 tier sharepoint 2013 farm architecture. please find the below server details.
    1. WFE & APP server (OS: Windows Server 2008 R2 SP1 and RAM: 8 GB) 
    2. database server (OS: Windows Server 2008 R2 SP1 and RAM: 8 GB) 
    I tried the following:
    - installed the latest sharepoint server 2013 CU.
    - OS is up to date.
    - deleted and recreated Search Service Application
    - The service account does have access to the search databases
    - one account is used, domain\sp2013search, has all necessary permissions
    Please help to fix the search issue.

    Hi Raj0639,
    According to your description, my understanding is that you got an error when you run SharePoint 2013 Search.
    Firstly, please make sure that all servers are online, and connecting to others.
    Please stop all search services on Manage services on server, then restart them. Please try to do as Amit said, compare the result.
    If this issue still exists, please repair SharePoint 2013 under Control Panel, then compare the result.
    Here is a similar post for you to take a look at:
    http://social.technet.microsoft.com/Forums/en-US/a67b0d0f-4f5a-4412-8f83-a57eaff4be45/sharepoint-search-host-controller-does-not-start?forum=sharepoin
    I hope this helps.
    Thanks,
    Wendy
    Wendy Li
    TechNet Community Support

  • Create SharePoint 2010 Search Service Application Using Powershell

    Hi Team,
    Could you please assist me in completing the search service application for
    two server using powershell. Both the servers will be running all the component
    Version SharePoint 2010
    # 1.Setting up some initial variables.
    write-host 1.Setting up some initial variables.
    $SSAName = "Search Service Application"
    $SVCAcct = "Domain\ServiceAccount"
    $SearchAppPoolName ="DefaultAppPool"
    $SSI = get-spenterprisesearchserviceinstance -local
    $err = $null
    $SSADBName="Search_AdminDB"
    $SSADBServer="DBServer"
    $host1="Server1"
    $host2="Server2"
    # Start Services search services for SSI
    write-host Start Services search services for SSI
    Start-SPEnterpriseSearchServiceInstance -Identity $SSI
    # 2.Create an Application Pool.
    write-host 2.Create an Application Pool.
    #$AppPool = new-SPServiceApplicationPool -name $SSAName"-AppPool" -account $SVCAcct
    $AppPool = Get-SPServiceApplicationPool -Identity $SearchAppPoolName -ErrorAction SilentlyContinue
    # 3.Create the SearchApplication and set it to a variable
    write-host 3.Create the SearchApplication and set it to a variable
    $SearchApp = New-SPEnterpriseSearchServiceApplication -DatabaseServer $SSADBServer -Name $SSAName -applicationpool $AppPool -databasename $SSADBName
    #4 Create search service application proxy
    write-host 4 Create search service application proxy
    $SSAProxy = new-spenterprisesearchserviceapplicationproxy -name $SSAName"ApplicationProxy" -Uri $SearchApp.Uri.AbsoluteURI
    # 5.Provision Search Admin Component.
    write-host 5.Provision Search Admin Component.
    set-SPenterprisesearchadministrationcomponent -searchapplication $SearchApp -searchserviceinstance $SSI
    # 6.Create a new Crawl Topology.
    write-host 6.Create a new Crawl Topology.
    $CrawlTopo = $SearchApp | New-SPEnterpriseSearchCrawlTopology
    New-SPEnterpriseSearchCrawlComponent -SearchTopology $newTopology -SearchServiceInstance $hostA
    Source:blog.MSDN Author- Russ Maxwell
    Thanks Basva

    Could you please assist me in completing the search service application for
    two server using powershell. Both the servers will be running all the component 
    Hi Basva,
    Do you want to provision two search service applications in single farm?
    Commonly, only one search service application is needed in a farm for Search function.
    Here are articles for detail information about how to provision search service application using powershell:
    http://blogs.msdn.com/b/jjameson/archive/2011/02/28/powershell-script-to-configure-search-in-sharepoint-server-2010.aspx
    http://blogs.msdn.com/b/russmax/archive/2009/10/20/sharepoint-2010-configuring-search-service-application-using-powershell.aspx
    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 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.

  • Search Service Application problems after upgrading from Foundation to Enterprise edition of SharePoint 2013

    Hi all. I have been searching for days for a solution to a problem I am having with SP2013 Enterprise edition.
    We recently upgraded from SP2013 Foundation to SP2013 Enterprise. After the upgrade, the search services are no longer working and we are receiving many application log entries indicating the following:
    Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (ea2019ef-bb9e-4efe-85ee-5d2307406f31).
    Reason: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
    Technical Support Details:
    System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
       at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
       at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)
    as well as:
    Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (ea2019ef-bb9e-4efe-85ee-5d2307406f31).
    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)
    I have tried to remove the search service application and recreate it, and even though the SharePoint Central Administration states that it was created successfully, I am still getting the same errors in the log. If I go to the Search Service Application
    Search Administration page, the "System Status" shows the following message:
    The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component '0359af35-0982-4ede-8838-b1d390e915bf' in search application 'Search Service Application' is in a good state and
    try again
    Additionally, under the "Search Application Topology" section, it states "Unable to retrieve topology component health states. This may be because the admin component is not up and running" which I assume is normal if the admin is not
    running.
    Does anyone know how I can resolve this problem? 
    Thanks!

    Hi Joaquin,
    According to your description, the error occurred when you re-created the Search Service Application.
    Based on the error message, I recommend to verify the things below:
       1. Check if the association between the Search Service Application proxy and the web application is configured.
    Please go to Central Administration > Application Management > Configured service application associations > Click Default to see if the Search Service application is checked.
       2. Change the app pool for the Search Service Application to SharePoint Web Services Default in the properties of the Search Service Application.
    Please go to Central Administration > Application Management > Manage service applications > Highlight the Search Service Application > Click Properties in the ribbon > Change
    the two app pool to SharePoint Web Services Default: App Pool For Search Admin Web Service and Application Pool for Search Query and Site Settings Web Service.
        3. Run PS command to check if the search admin timer job is enabled: Get-SPTimerJob
    job-application-server-admin-service | fl. If it is not enabled, use PS command to enabled it and then reset Internet Information Services: Enable-SPTimerJob job-application-server-admin-service.
    Best regards.
    Thanks
    Victoria Xia
    TechNet Community Support

  • How to create Search Service Application in SharePoint 2013

    When I am Creating Search Service Application through SharePoint Central Administration I am getting the error:
    Path of how I created It:
    Central Administration->Application Management->Manage Service Applications
    Here Click on New and Select Search Service Application
    How Should I create new search service application?
    As I want to create crawled Property and manage property for Search Center in SharePoint On Premises.

    Hi darsh,
    For creating a new search service application, you can refer to the blog:
    http://technet.microsoft.com/en-us/library/gg502597.aspx
    http://blogs.technet.com/b/praveenh/archive/2013/02/07/create-a-new-search-service-application-in-sharepoint-2013-using-powershell.aspx
    http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=378  
    For your issue , please refer to the article:
    http://praveensharepointknowledgebase.wordpress.com/2012/05/29/error-while-creating-search-service-application/ 
    Best Regards,
    Eric
    Eric Tao
    TechNet Community Support

Maybe you are looking for