Skip to main content

SharePoint 2013 - "No lists or libraries with InfoPath content types can be found"

I ran into a snag the other day after publishing an InfoPath form (as a Content Type) to one my SharePoint 2013 sites.  I was able to successfully publish the form to the Form Templates library.  Next step was adding the form to the page using the InfoPath Form Web Part.

Problem

When attempting to configure the Web Part I ran into this:
The message clearly states that "No lists or libraries with InfoPath content types can be found."

Solution

Please check the following depending on how you published the InfoPath form within your environment.

When publishing InfoPath form as a Content Type:
  1. See that the InfoPath form is being published to the same site as where the page with InfoPath Web Part is.
  2. Make sure that the Library (Form Templates) where the form is being published to has Content Types enabled.
  3. Enable Content Types on the Form Library where the form is submitted to (I'm assuming you are using a Forms Library other than the one in Step 2 for this).
  4. The form Content Type added to the Library where forms are submitted.

When publishing InfoPath form without a Content Type:
  1. See that the InfoPath form is being published to the same site as where the page with InfoPath Web Part is.
  2. Make sure that the Library you're publishing to is a Forms Library.


Comments

  1. Very Useful information Thank you!!
    TWB_ pioneered the offshore creation of technology content which was hitherto created by companies either internally or with ‘consultants’ hired by companies from vendors. TWB_

    changed that by creating domain depth that mirrored the customer’s own technology capability with deep SME teams for a variety of industries including Information Technology,

    Defence& Aerospace, Engineering, Life Sciences. TWB_ Creates, Automates, Repurposes and Publishes Content.


    ReplyDelete

Post a Comment

Popular posts from this blog

SharePoint Server Search - Error Starting

Problem I recently ran into this snag at a client site while setting up the Search Service Application.  I was able to create the service application without a problem however when I attempted to start the SharePoint Server Search service (Manage services on server page) I kept getting Error Starting . After taking a peak at the logs I found the following: An attempt to start/stop instance of service SharePoint Server Search on server did not succeed. Re-run the action via UI or command line on the specified server. Additional information is below. Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) I double/triple checked the permissions and made sure that my Farm Administrator account was a member of WSS_WPG and WSS_ADMIN_WPG groups, and that those groups had full control permissions to the C:\Windows\Tasks and C:\Windows\Temp folders. Resolution I nearly lost hope when I remembered my old lost friend called STSADM.EXE. Just like in the old da...

SharePoint 2013 - Creating and Applying Composed Looks (PowerShell)

If you are a SharePoint administrator looking to quickly apply some basic branding to a site-collection in your SharePoint 2013 environment then you've come to the right spot. Before we begin I assume you have a basic understanding of what Composed Looks are, and perhaps you spent some time playing around with this concept in SharePoint 2013. If not, then don't worry.  Here is a basic primer: Composed Look is basically a package which contains elements used for controlling the overall look and feel of a SharePoint site.  This includes but not limited to Colors, Fonts, Background Image, CSS files, and Master Page files. Once created, Composed Look can be packaged by using the Design Manager feature, or we can use PowerShell to apply it across one or multiple site collections. NOTE: In this post we will be focusing on creating a composed look from an .spcolor file then using PowerShell to apply the design to a site-site collection of our choice.  We wil...

SharePoint 2013 - Can't access the site externally in Internet Explorer ("Page cannot be displayed")

Synopsis Before we start talking about the problem let's understand the setup here.  We have a SharePoint 2013 intranet site that is also configured for access outside of the corporate network.  Employees use the same URL to visit the site both internally and externally via standard ports (80 and 443). Internal URL: http://sharepoint.domain.com Public URL: https://sharepoint.domain.com The site URL has been added to the Local Intranet zone in Internet Explorer for passing domain credentials. Alternate Access Mappings have been configured in such a way that if a user requests the site over HTTP they are automatically re-directed to HTTPS. Internal URL Zone Public URL for Zone https://sharepoint.domain.com Default https://sharepoint.domain.com http://sharepoint.domain.com Default https://sharepoint.domain.com Web application has been configured to use Kerberos protocol for authenticating incom...