-
It sounds as if you trying to open DAT on both servers from the same workstation. That would be the only explanation as to why the SharePoint 2007 exhibits the same problem without having done anything.
At what point in the tutorial does the problem appear? And do you have InfoPath 2007/2010 installed side-by-side?
-
The ThreadAbortException indicates a timeout occurred. You will need to edit the web.config in the QdabraWebService folder to add an entry in the <system.web> section:
<httpRuntime executionTimeout="3600"/>
the 3600 is in seconds, so this would be 60 minutes. You can set as needed to prevent the ...
-
A workaround that may work for you is to click OK to the error, then go to IIS Administration and create the virtual directory. The QdabraWebService folder should have been created under the website, right-click and click and select 'Properties'. Then click 'Create' and OK. Then switch back to the installer and ...
-
This is probably unrelated, but based on the attached PDF, you do not have a primary key defined on the table. You have CORNO marked as the Key in mapping, so the table will need to be updated to define the primary key.
Can you attach the content of the xml which is failing ?
-
The first step would be to verify the SQL connection from the server to the database. Using the same logon as you are installing DBXL, open SQL Management studio on the server and verify the connection to the sql instance. If SQL is on the same server, try using (LOCAL) or (LOCAL)\instancename, or MACHINENAME ...
-
FYI...
Here's a method of handling invalid numeric values in case you have form fields that are string type but need to be treated as numeric values.
my:ID[string(number(.))!='NaN']
Valid numeric values will get saved and an invalid numeric value is saved as NULL.
-
Can you generate sql scripts for the database tables, including foreign keys, indexes etc and email them to support(at)qdabra.com? This will allow us to identify the exact scenario that might cause the issue you are seeing.
Also, please include the version of SQL Server are you using.
Thanks,
Jim
-
Logon locally on the server, launch IE and navigate to http://qwssp.akaiwdemo.com/qWSSP/DbxlAdmin.asmx
Does the page display properly?
And if you ping qwssp.akaiwdemo.com, does the IP address resolve as the local machine IP address or is it mapped through a firewall?
-
For the server side submit, you will want the data connection to use the internal url and not the public url. Are you using an Alternate Access Mapping for the external users?
-
The site url will need to resolve as Local Intranet for authentication to work correctly during setup. Please add the site url to your local intranet in IE (http://servername) then retry accessing the link again in IE.