+1-888-365-2779
Try Now
More in this section

Forums / Bugs & Issues / Trying to create a search index causing an error

Trying to create a search index causing an error

3 posts, 0 answered
  1. Andrew
    Andrew avatar
    202 posts
    Registered:
    05 Jun 2009
    06 Mar 2014
    Link to this post

    When clicking on the "create a search index" button i get an error:

     Server Error in '/' Application.

    No pipe registered with name 'ContentInboundPipe'!

    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 

    Exception Details: System.ArgumentException: No pipe registered with name 'ContentInboundPipe'!

    Source Error: 

    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

     

    Any idea, what this is, and how i can fix it?

  2. Svetoslav Manchev
    Svetoslav Manchev avatar
    735 posts
    Registered:
    06 Dec 2016
    10 Mar 2014
    Link to this post
    Hi Andrew,

    This error appears on Search index creation in case the 'Feeds & Notifications' module is deactivated. This is a bug and I have logged it in our Feedback portal.

    So you need to Activate/Install the 'Feeds & Notifications' module under:
    Administration > Modules & Services > (Feeds & Notification) Actions > Activate > Activate/Install

    I hope this information helps.

    Regards,
    Svetoslav Manchev
    Telerik
    Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Sitefinity CMS Ideas&Feedback Portal and vote to affect the priority of the items
  3. Andrew
    Andrew avatar
    202 posts
    Registered:
    05 Jun 2009
    15 Mar 2014 in reply to Svetoslav Manchev
    Link to this post

    Thank you.

    That fixed it.

3 posts, 0 answered