While playing around with the beta preview builds, a problem with the search service application was discovered and here is a description and fix for it:

Applies to “SharePoint 2013 PREVIEW build”

Problem Description:

Search Topology fails to complete provisioning.
When you navigate to the Search Administration page to view the Topology In the UI under the Search Application Topology, you will see the following Error Message

Search Application Topology
Unable to retrieve topology component health states. This may be because the admin component is not up and running.

Symptoms:

Error Message: The Search Topology Fails to complete Provisioning /initialize successfully

The Following events may accompany this error:
Event Log Errors: Application Server Administration job failed for service instanceMicrosoft.Office.Server.Search.Administration.SearchServiceInstance
Reason:Failed to connect to system manager. SystemManagerLocations: net.tcp://../AdminComponent1/Management

Technical Support Details: System.InvalidOperationException: Failed to connect to system manager. SystemManagerLocations: net.tcp://../AdminComponent1/Management —> System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at net.tcp://../AdminComponent1/Management/NodeController that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.

Unified Logging System Events (ULS):

Services 00000 Unexpected Unexpected exception in node activator: System.IO.FileLoadException: A procedure imported by ‘Microsoft.Ceres.SearchCore.FastServer.Managed.dll’ could not be loaded. File name: ‘Microsoft.Ceres.SearchCore.FastServer.Managed.dll’ at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean forIntrospection) at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) at System.AppDomain.Load(String assemblyString) at Microsoft.Ceres.CoreServices.Node.TypeBinding.TypeInfo.LoadType() at Microsoft.Ceres.CoreServices.Node.TypeBinding.TypeRegistry.<GetByAttribute>d__d.MoveNext() at Microsoft.Ceres.CoreServices.Node.NodeActivator.InitializeDynamicComponents(ITypeRegistry typeRegistry) at Microsoft.Ceres.CoreServices.Node.NodeActivator.ActivateNode(IDictionary`2 configuration)

08-03-2012 13:25:07.63 NodeRunnerAdmin1-8dec8342-599f- (0x16E0) 0x1720 Search Unified Logging Service 8wsw High Now terminating ULS (NodeRunnerAdmin1-8dec8342-599f-40f1-a064-a8d01fd5b8b5, Microsoft.Ceres.Diagnostics.Native.dll)

08-03-2012 13:25:07.63 NodeRunnerAdmin1-8dec8342-599f- (0x16E0) 0x1720 Search SQM auk9 Medium SQM: LastUpload=2039062Ms; Now=2046781Ms; FileCount=0; TotalBytes=0

08-03-2012 13:25:14.58 hostcontrollerservice.exe (0x11D0) 0x1098 Search Search HostController ad5eq Medium HostController:Restarting node AdminComponent1 on system marked for automatic startup – threadId: 18

Resolution:

Install these fixes:

· KB 2567680 in addition to KB 2554876, KB 2708075, KB 2472264

and as recommended in the Install SharePoint 2013 Preview across multiple servers for a three-tier farm documentation on TechNet.

Maybe a reboot of the server should be done after installing the fixes and then everything is fine and search is back working again