S0002: Caught exception ensuring SharePoint form library - InfoPath Dev
in

InfoPath Dev

S0002: Caught exception ensuring SharePoint form library

Last post 09-10-2012 09:40 PM by AyaSuz. 2 replies.
Page 1 of 1 (3 items)
Sort Posts: Previous Next
  • 09-10-2012 12:09 AM

    • AyaSuz
    • Not Ranked
    • Joined on 09-09-2012
    • Posts 5

    S0002: Caught exception ensuring SharePoint form library

    Hello,

     

    I’m encountering a problem while integrating DBXL with Sharepoint.

     

    1) First, I created a basic InfoPath form (using InfoPath 2010)

     

    2) Then I mapped the form to our SQL server 2012 database in DAT. By opening and filling a form directly from DAT it works perfectly. Data are inserted in the SQL server 2012.

     

    3) Now I wanted to integrate DXBL with Sharepoint. I published my form (let say template.xsn) into Sharepoint (let say http://servername/FormLibrary/Forms/AllItems.aspx). Then I followed the instructions in the “DBXLIntegration with SharePoint.pdf” document.

     

    In the Sharepoint tab, I inserted the url where the template.xsn has been published, I selected “Object Model” in the Method column and checked “Publish Library and XSN”. By clicking the save button, I’m getting the following error in the event log:

     

     

     

     An error occurred while setting up a SharePoint collection mapping with the adminstrative tool. This could be a user error. In case it is a system problem, error details have been logged. SharePoint URL:http://servername /sites/FormLibrary Exception:System.ApplicationException: A web exception occurred attempting to read the UDC file http://servername /sites/DataConnection/Main_Submit.udcx for template http://servername /sites/FormLibrary: System.Net.WebException: The remote server returned an error: (401) Unauthorized.   at System.Net.WebClient.DownloadDataInternal(Uri address, WebRequest& request)   at System.Net.WebClient.DownloadData(Uri address)   at Qdabra.Dbxl.Implementation.Util.TemplateTool.EnsureDocTypeNameBinding(XmlDocument manifestFile, XmlNamespaceManager nsMgr, String docTypeName, String uncabbedFolder, String listUrl, ICredentials ssoCredentials) ---> System.Net.WebException: The remote server returned an error: (401) Unauthorized.   at System.Net.WebClient.DownloadDataInternal(Uri address, WebRequest& request)   at System.Net.WebClient.DownloadData(Uri address)   at Qdabra.Dbxl.Implementation.Util.TemplateTool.EnsureDocTypeNameBinding(XmlDocument manifestFile, XmlNamespaceManager nsMgr, String docTypeName, String uncabbedFolder, String listUrl, ICredentials ssoCredentials)   --- End of inner exception stack trace ---   at Qdabra.Dbxl.Implementation.Util.TemplateTool.EnsureDocTypeNameBinding(XmlDocument manifestFile, XmlNamespaceManager nsMgr, String docTypeName, String uncabbedFolder, String listUrl, ICredentials ssoCredentials)   at Qdabra.Dbxl.Implementation.Util.TemplateTool.ProcessTemplateForSharePoint(String listUrl, Boolean browserEnable, String docTypeName, ICredentials ssoCredentials, String uniqueUrnToken, String& urn)   at Qdabra.Dbxl.Implementation.ServiceImplementation.SharePointXsnTemplateProvider.GetTemplate(String sharePointListUrl, ICredentials ssoCredentials, String uniqueUrnToken, String& urn)   at Qdabra.Dbxl.Domain.SharePointMethod.EnsureFormLibraryAndPublishXsn(String qdabraWebServiceUrl, DbxlSharePointListMap mapping, ICredentials ssoCredentials, DbxlDocumentTypeProperties docTypeProperties, ISharePointXsnTemplateProvider templateProvider, WindowsIdentity userIdentity)   at Qdabra.Dbxl.SharePoint12.SharePointObjectModel.EnsureFormLibrary(String qdabraWebServiceUrl, DbxlSharePointListMap mapping, DbxlDocumentType docType, ISharePointXsnTemplateProvider templateProvider, WindowsIdentity userIdentity)   at Qdabra.Dbxl.Implementation.ServiceImplementation.UpdateSharePointListMappings(DocumentTypeInfo docTypeInfo, DbxlDocumentType docType, Session session) Stack Trace:   at Qdabra.Dbxl.Implementation.Util.TemplateTool.EnsureDocTypeNameBinding(XmlDocument manifestFile, XmlNamespaceManager nsMgr, String docTypeName, String uncabbedFolder, String listUrl, ICredentials ssoCredentials)   at Qdabra.Dbxl.Implementation.Util.TemplateTool.ProcessTemplateForSharePoint(String listUrl, Boolean browserEnable, String docTypeName, ICredentials ssoCredentials, String uniqueUrnToken, String& urn)   at Qdabra.Dbxl.Implementation.ServiceImplementation.SharePointXsnTemplateProvider.GetTemplate(String sharePointListUrl, ICredentials ssoCredentials, String uniqueUrnToken, String& urn)   at Qdabra.Dbxl.Domain.SharePointMethod.EnsureFormLibraryAndPublishXsn(String qdabraWebServiceUrl, DbxlSharePointListMap mapping, ICredentials ssoCredentials, DbxlDocumentTypeProperties docTypeProperties, ISharePointXsnTemplateProvider templateProvider, WindowsIdentity userIdentity)   at Qdabra.Dbxl.SharePoint12.SharePointObjectModel.EnsureFormLibrary(String qdabraWebServiceUrl, DbxlSharePointListMap mapping, DbxlDocumentType docType, ISharePointXsnTemplateProvider templateProvider, WindowsIdentity userIdentity)   at Qdabra.Dbxl.Implementation.ServiceImplementation.UpdateSharePointListMappings(DocumentTypeInfo docTypeInfo, DbxlDocumentType docType, Session session) encountered a critical error and needs attention.  User: myusernameUrl: /QdabraWebService/DbxlDocumentService.asmx 

     

     

    Configuration:

    Qdabra DBXL Standalone Edition is installed in the Sharepoint server.

    InfoPath 2010

    SQL Server 2012

    Sharepoint 2010

     

    Can you please advice regarding this error?

    It seems that it is related to a permission error...

    The identity of the DBXL application tool is set to "NetworkService" (default) and the Qdabra DBXL Standalone Edition service is logging on as a "Local System account".

     

    Thank you very much in advance for your support.

      

     

  • 09-10-2012 04:38 AM In reply to

    Re: S0002: Caught exception ensuring SharePoint form library

    Hi, and thanks for contacting us.

    What's the identity of the SharePoint - 80 app pool?

    We recommend that DBXL be installed on the SharePoint - 80 site, and using the same identity.

    Ernesto Machado
    Qdabra® Software/ InfoPathDev.com
    The InfoPath Experts – Streamline data gathering to turn process into knowledge.™


  • 09-10-2012 09:40 PM In reply to

    • AyaSuz
    • Not Ranked
    • Joined on 09-09-2012
    • Posts 5

    Re: S0002: Caught exception ensuring SharePoint form library

    Hi Ernesto,

    Thank you very much for your quick reply.

    DBXL is installed on the Sharepoint - 80 site and I changed the identity so it is using the same as the Sharepoint 80 app pool.

    It is working now!!

    Thank you so much for your quick support!

     Aya

Page 1 of 1 (3 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.