Search not working in SharePoint 2013 RTM

I recently setup SharePoint 2013 Development environment on a VM with complete farm install on a same machine. I configured setup using configuration wizard and added some documents to the root site. As soon as I searched it gave Some Error Occured message.

On checking error logs, I found that it gave message:

Ims::ExecuteError occured: System.ServiceModel.EndpointNotFoundException: There was no endpoint listening
at net.tcp://<machine name>/6A7919/QueryProcessingComponent1/ImsQueryInternal that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. Server stack trace: 
at System.ServiceModel.Channels.ConnectionUpgradeHelper.DecodeFramingFault(ClientFramingDecoder decoder, IConnection connection, Uri via, String contentType, TimeoutHelper& timeoutHelper) 

Then it had:

w3wp.exe: Query processing component net.tcp://<server ip address>/QueryProcessingComponent1/ImsQueryInternal changes its status to Failed.
w3wp.exe: All query processing components are in Failed status.

July 29th, 2013 6:42pm

Can you find more logs about why Query processing component changes its status to "failed"?

The log entry you post is from w3wp process, which act as a client to query the query processing component. This component is hosted by one of the NodeRunner.exe process, and it also write ULS log entry.

And you can also use tools such as windows resource monitor or process explorer to find if there is any abnormal resource consumption.

Free Windows Admin Tool Kit Click here and download it now
July 30th, 2013 1:20pm


I have come in this morning and the Search ( Query processor)  looks broken this I configured successfully a few weeks back. 

I have looked on the server logs and coincidently, there is is an issue in IIS with the app pool

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
 and APPID 
 to the user MYDOAMIN\SP_AppPoolSharePoint SID (S-1-5-21-1257006630-411654553-1540833222-8803) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

I know some of the guys were playing with running visual studio and on the dev server so I need to find out what they might have done .. Sigh

January 15th, 2014 5:40am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics