InfoPath Dev

I have installed the trial version of DBXL 2.4 and am working my way through the Getting Started material. Everything was going well until I got to Task 6: Configure SQL Mapping. I entered my connection string [Integrated Security=SSPI;Data Source=MOSS.litwareinc.com;Initial Catalog=DBXLTutorial;], tabbed out and clicked the Test Connection link and got the message that a connection was successfully established.

I clicked Insert Table or Column and then clicked on the Select Database Table icon and received the following error: "No schema could be derived with the current database connection string. Please update the connection string, save the document type, and try again."

I would appreciate any help you could give me in troubleshooting this error message. DBXL is installed on a single server along with Windows 2003 R2, SQL Server 2005, and MOSS 2007.

Thanks,
Stuart

Did you do a Save of your Document Type, including the connection string, before clicking the Test Connection button? 

Thanks for the reply. If I type in the connection string, then immediate click the Save button, I receive the following error:

InfoPath cannot complete this action, because of an error in the form's code. [and if I click the Show Details button it states...]
Object reference not set to an instance of an object.
   at AdminTool.Configuration.UpdateDatabaseSchemaDescription()
   at AdminTool.Configuration.btnSave_OnClick(DocActionEvent e)
   at Microsoft.Office.Interop.InfoPath.SemiTrust._ButtonEventSink_SinkHelper.OnClick(DocActionEvent pEvent)

Sorry I'm not able to interpret that error message --- any help would be appreciated.

I sugguest first checking that the Web Service URL at the bottom of the DBXL Admin tool matches the url from which you opened the form.   If it doesn't, open IE and navigate to the default.htm page from the correct url.  You can then reopen DBXL admin tool using the link on that page.  Also note that the url must be in the Local Intranet zone to have the necessary permissions to function correctly.

In the admin tool, here are the two URLs:

URL to Form Template: HTTP://moss.litwareinc.com/QdabraWebService/Forms/ID/192/template.xsn

Web Service URL: HTTP://moss.litwareinc.com/QdabraWebService/DbxlDocumentService.asmx

I assume these are correct? I've also added the site http://moss.litwareinc.com to my Local Intranet Zone, but I am still receiving the same errors as before.

Any other suggestions? Thanks again for your help.
Stuart

Hi Stuart,

To troubleshoot this please look at the permissions on the DBXLTutorial database. Can you check which users have permissions to that database? By default, DBXL writes to the QdabraDBXL and QdabraUtility databases, so you can check/compare those two databases (to see which users have access to it).

Let us know what you find and we can continue guiding you. Thanks.

Hi Ernesto, Thanks for the reply. All three databases (DBXLTutorial, QdabraDBXL, QdabraUtility) have these same 5 users: dbo, guest, INFORMATION_SCHEMA, NT AUTHORITY\NETWORK SERVICE, sys). Please let me know what other information would be helpful to troubleshoot this issue. Thanks, Stuart

Hi Stuart,

Ok, so the correct users exist. The next step is to verify the roles assigned to these users. The DBXL installer creates the QdabraDBXL and QdabraUtility databases, adds the users, and add roles to them. I assume you created the DBXLTutorial database manually and maybe added the users. The next step is checking the roles assigned to those users and compare to the other two databases.

Can you check this and let us know what you find? Thanks.

Hi Ernesto,
For two of the users (INFORMATION_SCHEMA and sys) there were no Owned Schema or Role Members. For the other three users, I have attached a picture (using the Options tab in this forum) that compares the information for the other three users by database. Let me know if this was the information you were looking for, or if there is additional information you need.
Thanks, Stuart

Thanks to Jim Cantwell at Qdabra, this problem is now resolved. For my development environment, I was using the pre-configured VHD of SharePoint 2007 from Microsoft which has the domain controller, SQL Server, and SharePoint all installed on the same VM. Accessing the IIS manager and changing the Identity property of the DBXL application pool from Predefined to Configurable (and using the admin login/password) resolved the problem.

Thanks again to Jim Cantwell and the Qdabra team for resolving this issue.

Stuart