-
Browser forms have a default connection timeout that can be set in Central Administration. The default on a new SharePoint installation is ten seconds.
InfoPath full-client forms have a default timeout of 30 seconds. It requires code to change the timeout, or you can use Qdabra qRules.
-
In Central Administration, go into General Application Settings/Configure InfoPath Form Services and make sure you have 'Authenticate to data sources' enabled, and also cross-domain access if the data connection is different than the site where your form lives.
-
On the SharePoint 2010 server, you will need to go into Manage Trust under General/Security and make sure the certificate authority that issued your certificate is trusted.
-
Can you double check that script code? The if(XDocument.IsNew) doesn't have a curly brace '{' and I would expect it to look more like this:
var oRows2;
var oSampleRow2;
function XDocument::OnLoad(eventObj)
{
oRows2 = XDocument.DOM.selectNodes("/my:myFields/my:StepFour/my:s4Table");
oSampleRow2 = oRows2.nextNode();
...
-
Based on your description, it appears to be more of a network performance issue. If the same data connections being called on your machine perform signficantly faster, I suggest starting with comparing the user's network configuration and computer specs to yours. If the machines are hard-wired to the network, I suggest ...
-
The cause of the 405 "Method not allowed" with SharePoint mapping is likely that having WebDAV role installed on the server. Removing the WebDAV role from the server should fix the SharePoint HTTP 405 errors. There are known issues with SharePoint servers having the WebDAV role installed.
-
Please email us your SharePoint and DBXL web.config files.
Thanks,
Jim
-
We have recently seen another user with the 405 'Method Not Allowed' error on saving a SharePoint mapping. The workaround until we determine the root cause is to pre-create the SharePoint library using the SharePoint UI and then add the SharePoint mapping in DBXL.
-
The first item to check is that the QdabraWebService virtual directory still shows up under the website. Then check that the DBXL application pool is set correctly (it should be DbxlAppPool{siteid}).
-
Did you update the SSO application definition to grant authenticated users access?
How was it previously configured under anonymous access?