-
It sounds like you missed the step of passing in the query string when setting up the data connection. Specify the query columns when setting up the data connection.
<query maxrows='2'><columns><column name='Client_x0020_Name'/><column name='Address'/><column ...
-
Great to hear it is working now. You should also be able to bring up the default page which has links to the Admin tool and other helpful information http://DP00035/QdabraWebService/default.htm
-
Documents is not a physical folder under QdabraWebService and is not browsable.
Have you corrected the database access error for the ASPNET account?
Does the eventlog show anything when accessing DAT ? http://DP00035/QdabraWebService/Forms/DAT/template.xsn
-
It looks like you are using IIS5 since you are using the ASPNET account. Is this installed on XP and have you reviewed the installation notes for XP?
Please check the web.config in the QdabraWebService folder and search for DocumentHandlerPath, and verify the url is http://dp00035/QdabraWebService/Documents/
-
When you install DBXL, the account used to create the databases is the user account you are logged on with. When the application is running, it connects using the application pool account, which unless you changed it is NETWORK SERVICE.
Setup will usually grant the NETWORK SERVICE account the db_datareader and db_datawriter role ...
-
When the error displays, but before you dismiss the dialog, verify you can display the http://<yourhostname>/QdabraWebService/default.htm
The eventlog error indicates you have a server or hostname named 'qdabra' that could not be found (http://img32.imageshack.us/img32/5230/33344365.png)
Did you resolve that issue? Is ...
-
I just noticed you have a separate site configured for DBXL. The KB article http://support.microsoft.com/default.aspx/kb/896861 will apply to the DBXL site as well as the SharePoint site.
-
On the server, are you able to browse in IE to the site you selected to install DBXL? If it fails to load, there is a known issue that is addressed in this KB article http://support.microsoft.com/kb/896861
-
That error is likely more associated with a save operation. Opening a document should not be doing a SharePoint operation, unless the dbxl submit data connection is set for execute on load.
-
Is DBXL indicating the file is in use or is it SharePoint? DBXL maintains its own locking mechanism separate from SharePoint. The InfoPath client will lock the form in DBXL and update the lock periodically while the form is open. There is a potential that the form is not getting unlocked by the InfoPath client.
Run the following ...