none
Search service is not able to connect to the machine that hosts the administration component

    Question

  • I encounter the error above when trying to set up Sharepoint Server Search. I have tried both setting up search manually through Central admin (just selecting default for everything) as well as through Powershell (using this: http://stsadm.blogspot.com/2009/12/creating-sharepoint-2010-enterprise.html).
    I'm using the farm admin as Search account as well as account for Application pools, so I guess permissions should not be the issue.

    Creating new Search service application seems to be successful, but when going to Searchadministration after creation, then System status displays the error above. 
    Event log does add any info and just displays same error message ("SearchApi.cs throws exception:The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component 'db397ab0-d9b0-46c4-9077-dc8be62bf586' in search application 'TNS Enterprise Search Service Application' is in a good state and try again.").

    I have found this http://blog.fpweb.net/sharepoint-2010-server-search-troubleshooting/ stating that the solution is not to use MSDN version of Windows 2008, but does give any explanation why.

    Any ideas would be appriciated.

    Best regards
    Thomas
    Tuesday, March 09, 2010 9:43 AM

Answers

  • I have now solved my problem. The solution is as follows:

    Tried running Configuration wizard again and got this error:

    Failed to secure the Sharepoint resources.
    An exception of type System.ArgumentException was thrown. Additional exception information: Cannot apply security settings to resource HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\14.0\Registration\{90140000-110D-0000-1000-0000000FF1CE} as it does not exist.

    I then copied another reg key from same location (91140000-0011-0000-1000-0000000FF1CE) and gave it guid of the missing key.
    Re-ran the configuration wizard successfully and the search is now working!

    I did my initial install and farm config using Powershell script, so perhaps I missed that config was exiting with error (but the farm and sitecollection have been behaving correctly except the problem with search service, so did not notice that anything was wrong with initial config).

    Why the above reg key was missing on my system I have no idea about, but have now seen the same problem on several instances we have created – is it perhaps a special combination of Office versions and Sharepoint versions that does not work together?

    Hope this helps others with same issue.

     

    Best regards

    Thomas

    • Marked as answer by tnsprivat Tuesday, April 13, 2010 12:27 PM
    Tuesday, April 13, 2010 12:26 PM

All replies

  • Could you post the error? It doesn't appear here.

    Tuesday, March 09, 2010 6:20 PM
  • I get the error as descibed in the headline - sorry if that was unclear. On the Searchadministration page (searchadministration.aspx) under System status - Crawl Status it displays:
    "The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component 'bae8d161-c132-4570-aa0d-57baf6cf9d9b' in search application 'Search Service Application 1' is in a good state and try again." - same message is displayed in the log files.

    Under Search Application Topology (also on Searchadministration.aspx) it does seem to finish loading data - constantly displaying the "...loading" message.

    Best regards,
    Thomas
    Wednesday, March 10, 2010 8:33 AM
  • I've been having issues with search, as well, and some of them were solved by actually using an enterprise account where the farm account didn't work. Not sure why that would be, but it improved while still not solving the search issues completely.

    The article you quoted is such a direct hit for your error, though, I'd wonder if you have access to prod, ie non-msdn, Server 2008 media, it might be worth a try.
    Wednesday, March 10, 2010 7:39 PM
  • [Security/privacy note, do not send your server names or accounts on a public forum].

    I would suggest taking a look at the basic health of the administration component and network configuration using the following commands:

    In a command prompt, could you please run the following (each line is a separate command):
       sc qc sptimerv4
       sc qc osearch14

    This will show some information about the timer and search services. Are they using the same account?
    An interesting field is the account shown for the SERVICE_START_NAME field. Could you please then check some memberships for those accounts as follows (using the command prompt):
      net localgroup administrators
      net localgroup WSS_ADMIN_WPG
      net localgroup WSS_WPG

    In PowerShell, please type the following:
    Get-SPEnterpriseSearchServiceApplication | Get-SPEnterpriseSearchAdministrationComponent
    Is the 'Initialized' field set to 'True'?

    Click 'Start'>'Run...', then type inetmgr in the dialog that shows.

      Navigate to <MachineName> > Sites> SharePoint Web Services, then click 'View Applications'
      Check that the web service which path looks like '%ProgramFiles%\Microsoft Office Servers\14.0\WebServices\SearchAdmin' is online.

    Is there a firewall inbound rule enabled for SharePoint Web Services?

    Thanks,
    Firaz.

    Wednesday, March 10, 2010 11:58 PM
  • Also, did you run the prerequisite installer located in the same folder as setup.exe? If that was not run, issues might happen because the system will not be working properly.

    Thanks,
    Firaz.
    Thursday, March 11, 2010 1:10 AM
  • Hi Firaz,

    Checked services and groups. SPTimer14 and OSearch14 runs under same account. This account is member of administrators, WSS_ADMIN_WPG and WSS_WPG.

    When checking SPEnterpriseSearchAdministrationComponent it returns Initialized=false !

    I'm accessing everything locally for now, so don't expect any firewall issues is involved here.


    Thanks for your help so far. Any ideas why the Administration Component is not initialized, and how I can initialize it?


    Thanks,
    Thomas




    Thursday, March 11, 2010 9:24 AM
  •  Could you please check that 'Microsoft Chart Controls for Microsoft .Net Framework' is installed on your system? If it is missing, then please install it (http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=130f7986-bf49-4fe5-9ca8-910ae6ea442c).

     After that, as a verification step, please create a new Search Service application: using the 'Central Administration'>'Application Management'>'Manage Service Applications' page. Click on the Ribbon's 'New>Search Service Application' and fill in the necessary information.

     If Chart Controls is already installed, please do the following in PowerShell to try to track down the cause of the administration component initialization failure in the ULS logs:

    $level = "Unexpected"
    $logsPath = "$env:TMP\Uls$level.log"
    $time = Get-Date
    $time = $time.AddHours(-1)
    Merge-SPLogFile -Path $logsPath -overwrite -StartTime $time -Level $level
    "Merged ULS log file could be found on $logsPath"
    "Getting Search event with level '$level'"
    $ulsevents = Get-SPLogEvent -file $logsPath -MinimumLevel $level | Where-Object {$_.Area -like "component" -or $_.Message -like "*Microsoft.Office.Server.Search*"}
    $ulsevents


    Thanks,
    Firaz.

    Thursday, March 11, 2010 9:52 PM
  • Checked Microsoft Chart Controls - was already installed.

    Unexpected log returns:

    Timestamp   Area                      Category                  EventID  Level      Message                                                                               
    ---------   ----                      --------                  -------  -----      -------                                                                               
    07:57:56.80 SharePoint Server Search  Query Processor           0000     Unexpected Exception occurred while triggering query processor cache refresh for application ba...
    07:58:56.80 SharePoint Server Search  Query Processor           0000     Unexpected Exception occurred while triggering query processor cache refresh for application ba...
    07:59:56.80 SharePoint Server Search  Query Processor           0000     Unexpected Exception occurred while triggering query processor cache refresh for application ba...
    08:00:44.68 SharePoint Foundation     Timer                     6398     Critical   The Execute method of job definition Microsoft.Office.Server.Search.Administration.C...
    08:00:44.68 SharePoint Foundation     Timer                     72ae     Unexpected Exception stack trace:    at Microsoft.Office.Server.Search.Administration.SearchApi...
    08:00:56.80 SharePoint Server Search  Query Processor           0000     Unexpected Exception occurred while triggering query processor cache refresh for application ba...
    08:01:56.81 SharePoint Server Search  Query Processor           0000     Unexpected Exception occurred while triggering query processor cache refresh for application ba...
    08:02:56.81 SharePoint Server Search  Query Processor           0000     Unexpected Exception occurred while triggering query processor cache refresh for application ba...
    08:03:56.81 SharePoint Server Search  Query Processor           0000     Unexpected Exception occurred while triggering query processor cache refresh for application ba...
    08:04:56.81 SharePoint Server Search  Query Processor           0000     Unexpected Exception occurred while triggering query processor cache refresh for application ba...
    08:05:44.69 SharePoint Foundation     Timer                     6398     Critical   The Execute method of job definition Microsoft.Office.Server.Search.Administration.C...
    08:05:44.69 SharePoint Foundation     Timer                     72ae     Unexpected Exception stack trace:    at Microsoft.Office.Server.Search.Administration.SearchApi...
    08:05:56.81 SharePoint Server Search  Query Processor           0000     Unexpected Exception occurred while triggering query processor cache refresh for application ba...
    08:06:56.81 SharePoint Server Search  Query Processor           0000     Unexpected Exception occurred while triggering query processor cache refresh for application ba...
    08:07:56.81 SharePoint Server Search  Query Processor           0000     Unexpected Exception occurred while triggering query processor cache refresh for application ba...
    08:08:56.82 SharePoint Server Search  Query Processor           0000     Unexpected Exception occurred while triggering query processor cache refresh for application ba...
    08:09:56.82 SharePoint Server Search  Query Processor           0000     Unexpected Exception occurred while triggering query processor cache refresh for application ba...
    08:10:44.71 SharePoint Foundation     Timer                     6398     Critical   The Execute method of job definition Microsoft.Office.Server.Search.Administration.C...
    08:10:44.71 SharePoint Foundation     Timer                     72ae     Unexpected Exception stack trace:    at Microsoft.Office.Server.Search.Administration.SearchApi...
    08:10:56.82 SharePoint Server Search  Query Processor           0000     Unexpected Exception occurred while triggering query processor cache refresh for application ba...
    08:11:56.82 SharePoint Server Search  Query Processor           0000     Unexpected Exception occurred while triggering query processor cache refresh for application ba...
    08:12:56.82 SharePoint Server Search  Query Processor           0000     Unexpected Exception occurred while triggering query processor cache refresh for application ba...
    08:13:56.82 SharePoint Server Search  Query Processor           0000     Unexpected Exception occurred while triggering query processor cache refresh for application ba...
    08:14:56.83 SharePoint Server Search  Query Processor           0000     Unexpected Exception occurred while triggering query processor cache refresh for application ba...
    08:15:44.72 SharePoint Foundation     Timer                     6398     Critical   The Execute method of job definition Microsoft.Office.Server.Search.Administration.C...
    08:15:44.72 SharePoint Foundation     Timer                     72ae     Unexpected Exception stack trace:    at Microsoft.Office.Server.Search.Administration.SearchApi...
    08:15:56.83 SharePoint Server Search  Query Processor           0000     Unexpected Exception occurred while triggering query processor cache refresh for application ba...
    08:16:56.83 SharePoint Server Search  Query Processor           0000     Unexpected Exception occurred while triggering query processor cache refresh for application ba...
    08:17:56.83 SharePoint Server Search  Query Processor           0000     Unexpected Exception occurred while triggering query processor cache refresh for application ba...
    08:18:56.83 SharePoint Server Search  Query Processor           0000     Unexpected Exception occurred while triggering query processor cache refresh for application ba...
    08:19:56.83 SharePoint Server Search  Query Processor           0000     Unexpected Exception occurred while triggering query processor cache refresh for application ba...
    08:20:44.73 SharePoint Foundation     Timer                     6398     Critical   The Execute method of job definition Microsoft.Office.Server.Search.Administration.C...
    08:20:44.73 SharePoint Foundation     Timer                     72ae     Unexpected Exception stack trace:    at Microsoft.Office.Server.Search.Administration.SearchApi...
    08:20:56.83 SharePoint Server Search  Query Processor           0000     Unexpected Exception occurred while triggering query processor cache refresh for application ba...
    08:21:56.84 SharePoint Server Search  Query Processor           0000     Unexpected Exception occurred while triggering query processor cache refresh for application ba...
    08:22:56.84 SharePoint Server Search  Query Processor           0000     Unexpected Exception occurred while triggering query processor cache refresh for application ba...
    08:23:56.84 SharePoint Server Search  Query Processor           0000     Unexpected Exception occurred while triggering query processor cache refresh for application ba...
    08:24:56.84 SharePoint Server Search  Query Processor           0000     Unexpected Exception occurred while triggering query processor cache refresh for application ba...
    08:25:44.73 SharePoint Foundation     Timer                     6398     Critical   The Execute method of job definition Microsoft.Office.Server.Search.Administration.C...
    08:25:44.73 SharePoint Foundation     Timer                     72ae     Unexpected Exception stack trace:    at Microsoft.Office.Server.Search.Administration.SearchApi...
    08:25:56.84 SharePoint Server Search  Query Processor           0000     Unexpected Exception occurred while triggering query processor cache refresh for application ba...
    08:26:56.86 SharePoint Server Search  Query Processor           0000     Unexpected Exception occurred while triggering query processor cache refresh for application ba...
    08:27:56.86 SharePoint Server Search  Query Processor           0000     Unexpected Exception occurred while triggering query processor cache refresh for application ba...
    08:28:56.86 SharePoint Server Search  Query Processor           0000     Unexpected Exception occurred while triggering query processor cache refresh for application ba...
    08:29:56.86 SharePoint Server Search  Query Processor           0000     Unexpected Exception occurred while triggering query processor cache refresh for application ba...
    08:30:44.76 SharePoint Foundation     Timer                     6398     Critical   The Execute method of job definition Microsoft.Office.Server.Search.Administration.C...
    08:30:44.76 SharePoint Foundation     Timer                     72ae     Unexpected Exception stack trace:    at Microsoft.Office.Server.Search.Administration.SearchApi...
    08:30:56.87 SharePoint Server Search  Query Processor           0000     Unexpected Exception occurred while triggering query processor cache refresh for application ba...
    08:31:56.87 SharePoint Server Search  Query Processor           0000     Unexpected Exception occurred while triggering query processor cache refresh for application ba...
    08:32:56.87 SharePoint Server Search  Query Processor           0000     Unexpected Exception occurred while triggering query processor cache refresh for application ba...
    08:33:56.87 SharePoint Server Search  Query Processor           0000     Unexpected Exception occurred while triggering query processor cache refresh for application ba...
    08:34:56.87 SharePoint Server Search  Query Processor           0000     Unexpected Exception occurred while triggering query processor cache refresh for application ba...
    08:35:44.76 SharePoint Foundation     Timer                     6398     Critical   The Execute method of job definition Microsoft.Office.Server.Search.Administration.C...


    Any other ideas?

    Best regards,
    Thomas

    Friday, March 12, 2010 8:02 AM
  • Try to assign the administration component again using PowerShell, retrieve the search application names on your farm using Get-SPEnterpriseSearchServiceApplication | select name, then specify the one you want to try out in the first line of code below:


    # Retrieve the search application names on your farm using Get-SPEnterpriseSearchServiceApplication | select name
    $searchApp  = Get-SPEnterpriseSearchServiceApplication -Name "<Search Application Name>"
    Write-Host -ForegroundColor white Initializing the administration component
    $searchInstance = Get-SPEnterpriseSearchServiceInstance -Local
    $searchApp | Get-SPEnterpriseSearchAdministrationComponent | Set-SPEnterpriseSearchAdministrationComponent -SearchServiceInstance $searchInstance
    $admin = ($searchApp | Get-SPEnterpriseSearchAdministrationComponent)
    Write-Host -ForegroundColor white Waiting for the admin component to be initialized
    foreach($i in 1..120)
    {
      sleep 1;
      Write-Host -ForegroundColor white .
      if ($admin.Initialized)
      {
        break
      }
    }
      if ($admin.Initialized)
      {
        Write-Host -ForegroundColor Green "Administration component initialized properly"
      }
      else
      {
        Write-Host -ForegroundColor Red "Administration component failed to initialize after 2 mins"
      }
       

    At the end of the script, you should either see a success or a failure, if you see a success, perfect. If not, please rerun the code in the past post (Thursday, March 11, 2010 9:52 PM) again and paste the output.

    Thanks,
    Firaz.

    • Proposed as answer by Erkan C Friday, November 09, 2012 5:32 PM
    Monday, March 15, 2010 10:10 PM
  • Hi Firaz,

    Thought I had answered early last week, but just realized my reply was never posted...

    Anyway, I had already tried to initialize admin component using Powershell without success. Did it again with the following result in log file:

    Timestamp   Area                      Category                  EventID  Level      Message                                                                               
    ---------   ----                      --------                  -------  -----      -------                                                                               
    15:45:53.59 SharePoint Foundation     Timer                     6398     Critical   The Execute method of job definition Microsoft.Office.Server.Search.Administration.C...
    15:45:53.59 SharePoint Foundation     Timer                     72ae     Unexpected Exception stack trace:    at Microsoft.Office.Server.Search.Administration.SearchApi...
    15:45:54.73 SharePoint Foundation     Timer                     6398     Critical   The Execute method of job definition Microsoft.Office.Server.Search.Monitoring.Healt...
    15:45:54.73 SharePoint Foundation     Timer                     72ae     Unexpected Exception stack trace:    at System.Data.SqlClient.SqlConnection.OnError(SqlExceptio...
    15:50:53.93 SharePoint Foundation     Timer                     6398     Critical   The Execute method of job definition Microsoft.Office.Server.Search.Administration.C...
    15:50:53.93 SharePoint Foundation     Timer                     72ae     Unexpected Exception stack trace:    at Microsoft.Office.Server.Search.Administration.SearchApi...
    15:55:31.08 SharePoint Foundation     Timer                     6398     Critical   The Execute method of job definition Microsoft.Office.Server.Search.Administration.C...
    15:55:31.08 SharePoint Foundation     Timer                     72ae     Unexpected Exception stack trace:    at Microsoft.Office.Server.Search.Administration.SearchApi...
    16:00:31.21 SharePoint Foundation     Timer                     6398     Critical   The Execute method of job definition Microsoft.Office.Server.Search.Administration.C...
    16:00:31.21 SharePoint Foundation     Timer                     72ae     Unexpected Exception stack trace:    at Microsoft.Office.Server.Search.Administration.SearchApi...

     

     

    Best regards,

    Thomas

    Tuesday, March 23, 2010 3:05 PM
  • Thanks Thomas for the logs and for trying the operation out again.

    There is a SQL exception that could be interesting here:

    15:45:54.73 SharePoint Foundation     Timer                     72ae     Unexpected Exception stack trace:    at System.Data.SqlClient.SqlConnection.OnError(SqlExceptio...

    Do you see any login errors in the event log?

     

    Thanks,

    Firaz.

     

    Tuesday, March 23, 2010 9:46 PM
  • Don't see any specific login errors. The full details of the errors at that time are:

    03/23/2010 15:45:54.73  OWSTIMER.EXE (OSPSDEV21:0x1350)          0x1230 SharePoint Foundation          Database                       5586 Critical Unknown SQL Exception 2812 occurred. Additional error information from SQL Server is included below.  Could not find stored procedure 'dbo.Search_GetRecentStats'. 9baaee56-a84e-4b3c-ac0c-7d32d197188e
    03/23/2010 15:45:54.73  OWSTIMER.EXE (OSPSDEV21:0x1350)          0x1230 SharePoint Foundation          Timer                          6398 Critical The Execute method of job definition Microsoft.Office.Server.Search.Monitoring.HealthStatUpdateJobDefinition (ID 37335377-2885-40e6-aaef-f8cdcc58ba6e) threw an exception. More information is included below.  Could not find stored procedure 'dbo.Search_GetRecentStats'. 9baaee56-a84e-4b3c-ac0c-7d32d197188e
    03/23/2010 15:45:54.73  OWSTIMER.EXE (OSPSDEV21:0x1350)          0x1230 SharePoint Foundation          Timer                          72ae Unexpected Exception stack trace:    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)     at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)     at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)     at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()     at System.Data.SqlClient.SqlDataReader.get_MetaData()     at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)     at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean a... 9baaee56-a84e-4b3c-ac0c-7d32d197188e
    03/23/2010 15:45:54.73* OWSTIMER.EXE (OSPSDEV21:0x1350)          0x1230 SharePoint Foundation          Timer                          72ae Unexpected ...sync)     at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)     at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)     at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)     at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)     at Microsoft.SharePoint.Utilities.SqlSession.ExecuteReader(SqlCommand command, CommandBehavior behavior, SqlQueryData monitoringData, Boolean retryForDeadLock)     at Microsoft.SharePoint.Utilities.SqlSession.ExecuteReader(SqlCommand command, Boolean retryForDeadLock)     at Microsoft.SharePoint.... 9baaee56-a84e-4b3c-ac0c-7d32d197188e
    03/23/2010 15:45:54.73* OWSTIMER.EXE (OSPSDEV21:0x1350)          0x1230 SharePoint Foundation          Timer                          72ae Unexpected ...Utilities.SqlSession.ExecuteReader(SqlCommand command)     at Microsoft.Office.Server.Search.Monitoring.DataAccess.GetApplicationHealth(ILoggingProvider loggingDb, Guid sharedServiceApplicationId, Single& queriesPerMinute, Single& crawlDocsPerSecond)     at Microsoft.Office.Server.Search.Monitoring.TraceDiagnosticsProvider.UpdateServiceApplicationHealthStats()     at Microsoft.SharePoint.Administration.SPTimerJobInvokeInternal.Invoke(SPJobDefinition jd, Guid targetInstanceId, Boolean isTimerService, Int32& result) 9baaee56-a84e-4b3c-ac0c-7d32d197188e
    03/23/2010 15:50:53.93  OWSTIMER.EXE (OSPSDEV21:0x1350)          0x1088 SharePoint Foundation          Timer                          6398 Critical The Execute method of job definition Microsoft.Office.Server.Search.Administration.CrawlReportJobDefinition (ID 3772b371-2d1a-44f0-88ba-981d77b0d9ae) 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 '4c764d44-9d6f-4e6e-916e-6e0de0ef15ec' in search application 'Search Service Application 1' is in a good state and try again. d4cd0271-990c-42ba-8e77-e1931ef44483
    03/23/2010 15:50:53.93  OWSTIMER.EXE (OSPSDEV21:0x1350)          0x1088 SharePoint Foundation          Timer                          72ae Unexpected Exception stack trace:    at Microsoft.Office.Server.Search.Administration.SearchApi..ctor(SearchServiceApplication application)     at Microsoft.Office.Server.Search.Administration.SearchServiceApplication.get_SearchApi()     at Microsoft.Office.Server.Search.Administration.CrawlReportJobDefinition.ExecuteTimerJob()     at Microsoft.SharePoint.Administration.SPTimerJobInvokeInternal.Invoke(SPJobDefinition jd, Guid targetInstanceId, Boolean isTimerService, Int32& result) d4cd0271-990c-42ba-8e77-e1931ef44483
    03/23/2010 15:55:31.08  OWSTIMER.EXE (OSPSDEV21:0x1350)          0x13A8 SharePoint Foundation          Timer                          6398 Critical The Execute method of job definition Microsoft.Office.Server.Search.Administration.CrawlReportJobDefinition (ID 99b49ef2-9c84-4091-a63d-709a682b854f) 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 '5f8a6b32-4b6d-457c-bf34-78225662d3d5' in search application 'Search Service Application 1' is in a good state and try again. 2ce17047-2ead-454d-8842-59820ba51e9f
    03/23/2010 15:55:31.08  OWSTIMER.EXE (OSPSDEV21:0x1350)          0x13A8 SharePoint Foundation          Timer                          72ae Unexpected Exception stack trace:    at Microsoft.Office.Server.Search.Administration.SearchApi..ctor(SearchServiceApplication application)     at Microsoft.Office.Server.Search.Administration.SearchServiceApplication.get_SearchApi()     at Microsoft.Office.Server.Search.Administration.CrawlReportJobDefinition.ExecuteTimerJob()     at Microsoft.SharePoint.Administration.SPTimerJobInvokeInternal.Invoke(SPJobDefinition jd, Guid targetInstanceId, Boolean isTimerService, Int32& result) 2ce17047-2ead-454d-8842-59820ba51e9f0

    The first problem seems to be that stored procedure 'dbo.Search_GetRecentStats' does not exist.

     

    Thanks,

    Thomas

    Wednesday, March 24, 2010 8:42 AM
  • Let's have a look at the full call stack for the exception from SearchApi, could you please run the following in PowerShell:

    Get-SPLogEvent -Minimumlevel Monitorable | ?{$_.eventid -eq '72ae' -and $_.message -like "*Microsoft.Office.Server.Search.Administration.SearchApi*"}|select -Last 1 | fl

    Also, please check the event log for errors related to Search, PLEASE NOTE THAT THIS WILL PROBABLY CONTAIN DETAILED INFORMATION THAT WILL NOT BE SUITABLE TO SHARE ON A PUBLIC FORUM. Please run the following in PowerShell:

    Get-EventLog Application  | Where {$_.Source -like "Microsoft-SharePoint Products-*Search*"} | Select Source,TimeGenerated,Index,InstanceId,Message,Category -Last 5 | fl

    Thanks,

    Firaz.

     

    Thursday, March 25, 2010 12:14 AM
  • Hi Firaz,

    Full call stack from latest SearchApi exception:


    Timestamp    : 25-03-2010 10:35:47
    Continuation : False
    Process      : OWSTIMER.EXE (0x0690)
    ThreadID     : 5028
    Area         : SharePoint Foundation
    Category     : Timer
    EventID      : 72ae
    Level        : Unexpected
    Message      : Exception stack trace:    at Microsoft.Office.Server.Search.Administration.SearchApi..ctor(SearchServiceApplication application)     at Microsoft.Office.Server.Search.Administration.SearchApi.CreateSearchApi(SearchServiceApplication application
                   )     at Microsoft.Office.Server.Search.Administration.SearchServiceApplication.get_SearchApi()     at Microsoft.Office.Server.Search.Administration.CrawlReportJobDefinition.ExecuteTimerJob()     at Microsoft.SharePoint.Administration.SPTimerJo
                   bInvokeInternal.Invoke(SPJobDefinition jd, Guid targetInstanceId, Boolean isTimerService, Int32& result)
    Correlation  : c5329271-6ba9-43c4-9911-6cb4ae2a97e0
    Context      : {}

    When running the second command for getting errors related to search, I'm getting this back:

    Source        : Microsoft-SharePoint Products-SharePoint Server Search
    TimeGenerated : 23-03-2010 15:43:49
    Index         : 5019
    InstanceId    : 1
    Message       : The description for Event ID '1' in Source 'Microsoft-SharePoint Products-SharePoint Server Search' cannot be found.  The local computer may not have the necessary registry information or message DLL files to display the message, or you may no
                    t have permission to access them.  The following information is part of the event:''
    Category      : (136)

    The current user is farm admin and member of local administrators, so what is missing in order to succesfully run this?

    I'm off on vacation for a week, so can't provide more detail about the error before getting back. But I would like to thank you, Firaz, for your help so far. The help and instructions are very clear and precise, so I really appreciate your effort to help solve this problem.

    Best regards,

    Thomas

     

    Thursday, March 25, 2010 9:48 AM
  • Let's have a look at the version of 'Windows Identity Foundation' that is installed by the prerequisites tool, please do the following using windows explorer:

    • Supposing your operating system is installed on c:, navigate to C:\Windows\assembly\
    • Right-click on Microsoft.IdentityModel, click 'Properties'
    • In the 'Properties' dialog, click on the 'Version' tab and check the file version, it should be something like 6.1.7600.XYZ. Could you please post it here?

     

    Thanks,

    Firaz.

     

     

    Friday, April 02, 2010 10:31 PM
  • Version of Microsoft.IdentiyModel is 6.1.7600.114.

    -Thomas

    Tuesday, April 06, 2010 8:01 AM
  • What is the version that you are using of the product? you might be hitting a compatibility issue with WIF.

    In the Control Panel> 'Programs' > 'Programs and Features', please check the version of 'Microsoft SharePoint Server 2010'. (Right click on the column names, then select 'More...', and select 'version' from the dialog that shows). It should look like 14.0.4xyz.10yz.

    Thanks,

    Firaz

     

    Wednesday, April 07, 2010 12:59 AM
  • We are running 14.0.4730.1010.

    Thanks,

    Thomas

     

    Wednesday, April 07, 2010 7:59 AM
  • Check Spence's post on app pool misconfigurations and see if that helps (I've had similar issues with this service and others and if I'm remembering correctly (though I may be thinking of something else) this helped).

    http://www.harbar.net/archive/2009/12/16/application-pool-mis-configuration-in-sharepoint-2010.aspx


    Gary Lapointe, Blog: http://stsadm.blogspot.com/, Twitter: http://twitter.com/glapointe

    Friday, April 09, 2010 12:49 AM
  • I have now solved my problem. The solution is as follows:

    Tried running Configuration wizard again and got this error:

    Failed to secure the Sharepoint resources.
    An exception of type System.ArgumentException was thrown. Additional exception information: Cannot apply security settings to resource HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\14.0\Registration\{90140000-110D-0000-1000-0000000FF1CE} as it does not exist.

    I then copied another reg key from same location (91140000-0011-0000-1000-0000000FF1CE) and gave it guid of the missing key.
    Re-ran the configuration wizard successfully and the search is now working!

    I did my initial install and farm config using Powershell script, so perhaps I missed that config was exiting with error (but the farm and sitecollection have been behaving correctly except the problem with search service, so did not notice that anything was wrong with initial config).

    Why the above reg key was missing on my system I have no idea about, but have now seen the same problem on several instances we have created – is it perhaps a special combination of Office versions and Sharepoint versions that does not work together?

    Hope this helps others with same issue.

     

    Best regards

    Thomas

    • Marked as answer by tnsprivat Tuesday, April 13, 2010 12:27 PM
    Tuesday, April 13, 2010 12:26 PM
  • Thomas, i am facing same issue with search service. could you explain, did you rebuild the server or just ran the configuration wizard.

    Regards

    Raj

    Wednesday, April 14, 2010 8:04 AM
  • I made sure the missing registry key was present and then just ran the configuration wizard. Rebuilding the server was not necessary.

    -Thomas

    Wednesday, April 14, 2010 10:45 AM
  • how did you got to know about the missing registry key... i re-run the configuration wizard however no success..

    Logs give these errors:-

    Office Server                  Unified Logging Service        2159 Critical Event 8081 (Office Server) of severity 'Error' occurred 3 more time(s) and was suppressed in the event log 


    Web Content Management         Publishing Cache               7362 Warning Object Cache: The super user account utilized by the cache is not configured. This can increase the number of cache misses, which causes the page requests to consume unneccesary system resources.  To configure the account use the following command 'stsadm -o setproperty -propertyname portalsuperuseraccount -propertyvalue account -url webappurl'. The account should be any account that has Full Control access to the SharePoint databases but is not an application pool account.  Additional Data:  Current default super user account: SHAREPOINT\system 8d90d13c-4184-41bf-84b0-1f3bf26c52c6


    Office Server                  State Service                  8081 Critical Microsoft SharePoint Server State Service could not find a State Service Application Proxy associated with the current web application (http://win-dste3fskrur:1234/AdminReports/Search administration reports/QueryLatencyTrend.aspx). 85be8266-f0ea-4de8-898a-e6560f8029b9


    SharePoint Foundation          Topology                       887x       Unexpected Can not access configuration database registry key: System.Security.SecurityException: Requested registry access is not allowed.     at Microsoft.Win32.RegistryKey.OpenSubKey(String name, Boolean writable)     at Microsoft.SharePoint.Administration.SPConfigurationDatabase.get_RegistryConnectionString()  The Zone of the assembly that failed was:  MyComputer 


    SharePoint Foundation          Runtime                        tkau  Unexpected Microsoft.Office.Server.Search.Internal.UI.SearchApplicationNotSelectedException: The specified page could not be displayed because the application ID is missing or invalid. You can attempt to browse to this page from  <a href="/_admin/ServiceApplications.aspx" target="_blank">Manage Service Applications</a>.    at Microsoft.Office.Server.Search.Internal.UI.SearchAdministration.OnLoad(EventArgs e)     at System.Web.UI.Control.LoadRecursive()     at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) e6244c35-b95c-4604-9315-6b5c535efcce

     

    Any ideas...............

    Wednesday, April 14, 2010 11:58 AM
  • Hi,

    We are also running into the error "The search service is not able to connect to the machine that hosts the administration component."

    However, we are able to re-run the Config Wizard successfully and it does not ask for any missing registry key.

    Any suggestions?

     

    Regards,

    Vinay

    Friday, April 16, 2010 6:19 AM
  • We also run into this problem.

    Has anybody a working solution?

    • Proposed as answer by Joshuarn Tuesday, June 22, 2010 6:20 PM
    Thursday, May 27, 2010 8:36 PM
  • Hi Firaz,

    I run the script and got the following result:

    PS C:\> c:\scr.ps1
    Initializing the administration component
    Get-SPEnterpriseSearchAdministrationComponent : databaseConnectionString
    At C:\scr.ps1:5 char:59
    + $searchApp | Get-SPEnterpriseSearchAdministrationComponent <<<<  | Set-SPEnterpriseSearchAdministrationComponent -SearchServiceInstance $searchInstance
        + CategoryInfo          : InvalidData: (Microsoft.Offic...rationComponent:GetSearchAdministrationComponent) [Get-SPEnterpris...rationComponent], ArgumentException
        + FullyQualifiedErrorId : Microsoft.Office.Server.Search.Cmdlet.GetSearchAdministrationComponent
    
    Get-SPEnterpriseSearchAdministrationComponent : databaseConnectionString
    At C:\scr.ps1:6 char:69
    + $admin = ($searchApp | Get-SPEnterpriseSearchAdministrationComponent <<<< )
        + CategoryInfo          : InvalidData: (Microsoft.Offic...rationComponent:GetSearchAdministrationComponent) [Get-SPEnterpris...rationComponent], ArgumentException
        + FullyQualifiedErrorId : Microsoft.Office.Server.Search.Cmdlet.GetSearchAdministrationComponent
    
    Waiting for the admin component to be initialized
    .
    .
    .
    .
    .
    Administration component failed to initialize after 2 mins
    PS C:\> 
    PS C:\> Get-SPEnterpriseSearchServiceInstance -Local
    
    TypeName    : SharePoint Server Search
    Description   : Index content and serve search queries
    Id       : 8f617773-5a61-4c9b-84d4-1da93049d675
    Server     : SPServer Name=TEST_WS01_SP
    Service     : SearchService Name=OSearch14
    Role      : None
    QueryComponents :
    CrawlComponents :
    AdminComponents :
    Status     : Online
    
    PS C:\>
    where to find a solution of the problem?
    Thursday, July 29, 2010 7:48 AM
  • "The search service is not able to connect to the machine that hosts the administration component" --- error is as a result of one of the services accounts not having access to the search_db's review your service accounts and ensure that the search service account has permissions. If not you can add the permissions directly on the database level and it should take care of it.

     

    Leonard Mwangi -- e Tek Global Inc.

    www.etekglobalinc.com

    • Proposed as answer by lmundia Thursday, August 05, 2010 9:30 PM
    Thursday, August 05, 2010 9:30 PM
  •  I agree with Leonard. I have given my App Pool Id (Intranet\SPFastSearch) for FAST SSA enough permission to access FASTAdminSearchDatabase and the problem got resolved. It is nothing to do with license it seems.

     

    Thanks

    Sugata

    Sunday, August 29, 2010 4:56 PM
  • Try modifying the application pool your search service uses in the Manager Service Applications page in Central Administration. Just click on Search Service Application in the list, and click "Properties" from the ribbon above. Then change your app pool. I switched mine from SharePoint Web Services Default to SharePoint Web Services System and it started working. The issue is definitely related to identity, not licensing as several of the other posters have also pointed out.
    • Proposed as answer by Nick KellettMVP Wednesday, September 01, 2010 6:07 PM
    Wednesday, September 01, 2010 6:07 PM
  • Ended up fixing this issue by changing the "SharePoint Server Search 14" service to use our domain search service account, for some reason it was running under our content application pool account.
    • Proposed as answer by JodyVS Tuesday, December 14, 2010 10:25 PM
    Friday, December 10, 2010 7:22 PM
  • "Ended up fixing this issue by changing the "SharePoint Server Search 14" service to use our domain search service account, for some reason it was running under our content application pool account."

    This is what fixed me as well. Just swapped out the account to the appropriate one, restarted the service, it took a few minutes, but the error went away.

    Tuesday, December 14, 2010 10:26 PM
  • I re-ran the SharePoint Config. Wizard. Then this problem resolved .

    Regards,

    Devi Prasad M


    Thanks, Devi Prasad M
    • Proposed as answer by Devi Prasad M Monday, December 20, 2010 1:45 PM
    Monday, December 20, 2010 1:45 PM
  • I was able to fix this issue on our farm.  Below are a couple of the errors from the logs that matched up with the error displaying at the top of the Search Administration page where the System Status and Crawl History were supposed to display.

    • The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component 'e3ca8cd5-5fa1-4a36-bea8-e45fce5ff951' in search application 'INT Search Service Application' is in a good state and try again.               

    On the Search Admin page the error at the top was reporting an issue with the administration component, but in the “Topology” section below that message the “Administration Component” showed online, however the “Crawl Component 0” showed Not Responding.    I reviewed the SP logs that were depressing, but not much help.  Next I clicked the Modify button on the page and tried to change and save, which did no good.   I also tried to delete that Non-Responding component, but it complained that I needed at least one, so again going to the Modify page, I decided to try to create a second Crawl Component.  That succeeded, and then the System Status began to light up again.  Finally, I deleted the Non-Responding Crawl Component 0.

    Another thing I did that may or may not have had an impact was to browse to a test site that housed a Search Center, though I think this was a coincidence.


    /bac

    Friday, June 08, 2012 8:35 PM