-
In Server Manager under the Roles, click Web Server (IIS), make sure all items under IIS6 Management Compatibility are installed.
-
MOSS 2007 and WSS v3 use a new local machine group WSS_WPG (similar to the IIS_WPG). You will need to make sure the Network Service account (or whatever account the DBXL App pool is using) is in the WSS_WPG group. After verifying that, do an iisreset and try accessing DBXL. If it gives the same error, check the Application and ...
-
You can workaround the rollback by adding a begin transaction/commit transaction to your query command or the stored procedure.
-
The DBXL setup wizard does not create an account. The username/password supplied in the wizard is for the webservice to connect to the SQL database and for the Windows account IIS should run the webservice. You should just use your normal machine logon credentials when connecting to the webservice.
-
Thanks for the post Bret. I'm sure it will come in handy for others.
Link to the user guide: http://www.infopathdev.com/files/folders/bulk_operations/entry31831.aspx
Link to Excel to XML download: ...
-
Make sure the domain account you are using for the webservice is added to the WSS_WPG group.
-
The error message indicates it is being installed to the default website (ID is 1). The WSS installation should be disabling the default website and creating a new site for WSS. Make sure that you select the WSS site when installing DBXL.
-
Please check the Application and Qdabra eventlogs for any additional information. And if you are running MOSS 2007 with a different account than DBXL, you will need to add that account to the WSS_WPG group.
-
Make sure you are using an upper-case K in Key="cn".
-
NOTE: The only supported url format for DBXL v2.1 and earlier is using the DocID as stated by Ernesto. The RefID usage is a new feature coming in DBXL v2.2.