InfoPath Dev

Hi,

We ordered qRules from qDabra last week and I was trying to create a form in SharePoint 2013 environment using InfoPath 2013, similar to the form in "qRules Submit to SharePoint List User Guide" PDF. I'm getting below error when I try to create a web service data connection. I enter https://server/_vti_bin/lists.asmx?WSDL for the Web Service click Next, it prompts me for credentials twice, and then it throws below error. The web service URL is opening fine from the browser.

"The file is not a valid XML file. Not enough storage is available to process this command."

Can anyone help? 

Thanks,

RM

 

 

Can you create a data connection to the lists service in a form without qRules in it? You are selecting SOAP for the type of connection?

No, I cannot create web service data connection without qRules either. I'm selecting To Other Locations > To Web Service.

When I try to add a project with WSDL in SOAPUI using the lists.asmx url, it asks for authentication, and when I enter the credentials, I get below error. "Error loading [https://servername/site/_vti_bin/lists.asmx?wsdl]: org.apache.xmlbeans.XmlException: org.apache.xmlbeans.XmlException: error: Unexpected end of file after null" I even tried with port 443 like "https://servername:443/site/_vti_bin/lists.asmx?wsdl" url, but got the same error. We are using Claims Authentication. Will this cause any issues and require additional configuration?

Ah, yes, sorry, forgot this was a submit connection. I've created submit connections to the lists web service on servers using claims auth - so I don't think it is claims auth that is the root of the issue. Do you have access to the SharePoint server? Maybe try adding the data connection and check the logs & the IIS logs?

I have access to the servers. I checked SharePoint logs, but didn't see any obvious error, everything looks Medium when this happens. IIS logs have lots of HTTP status codes, like 200, 207, 401, 405, 414 for the site and the web service I'm using. Can't tell which one is relevant. I know 401 is access denied, but it's there for many things. I was googling for possible claims issues with InfoPath and I found a few articles, like below, talking about some configuration needed to make the web services work in InfoPath for Claims web applications. Do you still think it's not Claims issue? http://www.c-sharpcorner.com/UploadFile/Roji.Joy/how-to-enable-sso-for-web-services-used-in-infopath-form-in/ http://blogs.technet.com/b/rajbugga/archive/2013/08/07/infopath-over-claims-authentication-sharepoint-2010-amp-2013.aspx http://suehernandez.wordpress.com/2013/10/11/sharepoint-2013-infopath-claims-getuserprofilebyname/ Thanks,

Oh, I should have been more clear - it could very well be a server configuration issue - but I have, in the past, used SharePoint web services in InfoPath with servers using claims. So, there is a way to do it - I'm just not sure what server configuration changes you may need to make.

It looks like I need to have the web service data connection already added to the form before configuring it for Claims, based on the articles above. I can't even add the data connection, so you might be right that the issue is not the Claims.