locked
Search not working in SharePoint 2013 RTM RRS feed

  • Question

  • 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::Execute–Error 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.

    Monday, July 29, 2013 3:42 PM

Answers

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

    • Marked as answer by Qiao Wei Thursday, August 8, 2013 3:12 PM
    Tuesday, July 30, 2013 10:20 AM

All replies

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

    • Marked as answer by Qiao Wei Thursday, August 8, 2013 3:12 PM
    Tuesday, July 30, 2013 10:20 AM
  • Hi 

    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 
    {61738644-F196-11D0-9953-00C04FD919C1}
     and APPID 
    {61738644-F196-11D0-9953-00C04FD919C1}
     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

    Wednesday, January 15, 2014 10:36 AM
  • How do you troubleshoot this issue?

    "There was no endpoint listening at"


    Friday, August 22, 2014 10:53 AM
  • I also faced the same issue, resetting the index helped me to resolve the issue.
    • Proposed as answer by PawanS Thursday, August 25, 2016 9:38 AM
    Thursday, August 25, 2016 9:37 AM