Installation and setup

Uninstalling Qdabra's QueryBuilder InfoPath form tool

ErnestoM — Tue, 16 Sep 2008 17:28:25 GMT

Qdabra's Query Builder InfoPath form tool needs to run with full trust so that it can execute shell commands. To install this full trust tool on your local computer, we use InfoPath’s built-in support for URN based solutions. When the form is installed, InfoPath adds entries to your Windows registry. Unfortunately, due to a bug in InfoPath installer, sometimes uninstalling doesn’t work and the registry entries are not cleaned up correctly. In such cases, the result is that you can’t re-install the tool, since your machine will think that "The form is already installed on your computer". You might also find that you are unable to remove the form from the InfoPath cache when you run the command Infopath /cache clearall.

If you encounter this issue, try to remove the form using the Windows CleanUp Utility. In addition, you might need to manually clean up the registry. Do this at your own risk and backup your registry before proceeding. If the problem is happening with the QueryBuilder form, for example, search for "QueryBuilder" in the registry and you will find a key like this:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\InfoPath\SolutionsCatalog\urn:schemas-microsoft-com:office:infopath:Qdabra-Query-Builder:-myXSD-2008-02-19T23-06-28.

Remove this key manually and you will then be able to reinstall the form.

Note that this could happen with any installed form, not just the QueryBuilder form.

How To Increase Web Service Timeout to Allow Large Document Upload

ErnestoM — Fri, 04 Jul 2008 22:08:52 GMT

If you are having trouble uploading large documents to DBXL you might need to increase the web service timeout to allow the upload enough time to complete. This can be done on the client side with managed code, or on the server-side (which affects all Document Types) via an edit to the web.config file for the DBXL instance that is causing the problem.

Note that the web.config change noted below is intended to add the <httpRuntime> node into the system.web section, as this node does not already exist in web.config. Also note that this change is only a server-side timeout and Infopath will still timeout after 30 seconds unless you use code to set the timeout.

WebServiceAdapter2 wsAdapter = (WebServiceAdapter2)thisXDocument.DataAdapters["DataConnectionName"];
wsAdapter.Timeout = 60; // Increase to 60 seconds - Default is 30
wsAdapter.Query(); // Issue the query

JScript

var wsAdapter = XDocument.DataAdapters["DataConnectionName"];
wsAdapter.Timeout = 60; // Increase to 60 seconds - Default is 30
wsAdapter.Query(); // Issue the query

web.config change

Further reference

Installing DBXL on a Computer with Terminal Services Installed

ErnestoM — Wed, 02 Jul 2008 22:34:43 GMT

The following issues might arise when trying to install DBXL on a computer with Terminal Services installed:

1. If installing the web service to one machine and using the SQL instance on another machine, DBXL cannot add the user Domain\MachineName$ to the remote SQL instance. This error completely prevents the installation of DBXL with an error that states “Failed to connect to the SQL Server”.

If you encounter this error, please manually add this user to the SQL permissions.

2. Using any other user group besides “BUILTIN\Administrators” for the DBXL Admin permission gives an Access Denied error when trying to publish DAT.
3. After DBXL is installed, clicking on the Administration Tool link on the web page that is opened crashes InfoPath.

To manually install DAT when error 2 or 3 occurs, follow these steps:

a. Open the URL http://localhost/QdabraWebService/DbxlAdmin.asmx from the machine where DBXL is installed.
b. Select the PublishDATFormTemplate web method.
c. Input the file path to the DAT template to upload and then click Invoke.

Active Directory query fails on Windows XP

ErnestoM — Wed, 02 Jul 2008 22:14:16 GMT

If you install DBXL to Windows XP and you cannot query the Active Directory Web service (ADUserInfo.asmx) you will have to manually configure your machine’s ASPNET account. To verify that this is the problem, navigate to http://machine/QdabraWebService/ADUserInfo.asmx, click GetMyInfo and Invoke. If you don’t get XML you will need to follow the following configuration steps.

Navigate to http://support.microsoft.com/kb/329290/, download and install the Aspnet_setreg.exe package.
Open a command window by clicking on Start, selecting Run, and then typing cmd.
Run aspnet_setreg.exe -k:SOFTWARE\Qdabra\DBXL\identity -u:"yourdomainname\username" -p:"password" with the correct values for yourdomainname\username and password.
Click Start, then Run and enter regedt32.
Expand HKEY_LOCAL_MACHINE\Software\Qdabra\DBXL\identity\ASPNET_SETREG and right click on the key ASPNET_SETREG in left pane.
Add permissions to allow MACHINE\ASPNET to read the key where MACHINE is the name of your machine.
Click Start, then Run and type in InetMgr.
Expand the Web Sites and Default Web Site tree.
Right click on QdabraWebService and choose Open.
In the window that opens, right click web.config and choose Open With and select Notepad.
Search for “<identity” and replace everything that appears in between the angular brackets <identity impersonate=”false” /> with the following:
<identity impersonate="true" userName="registry:HKEY_LOCAL_MACHINE\SOFTWARE\ Qdabra\DBXL\identity\ASPNET_SETREG,userName" password="registry:HKEY_LOCAL_MACHINE\SOFTWARE\ Qdabra\DBXL\identity\ASPNET_SETREG,password" />
Note that there must be no spaces in the value for username and password.

Find the key called ActiveDirectoryPath and change its value from the default (ldap://DC=domain/) to the value that corresponds to your server. If you do not know the correct value, ask your administrator or use the LDAP Test Tool.

Save and close web.config.

How to configure a license in DBXL

ErnestoM — Wed, 02 Jul 2008 22:08:44 GMT

Before you can begin using DBXL, you must attach a license. Whether it a demo license or one you have purchased, the license will allow you a certain number of document types and documents. Follow these steps to configure the license.

a) Launch the DBXL Admin Tool (DAT).

1. Open Internet Explorer.
2. Enter http://<servername>/QdabraWebService/forms/DAT/template.xsn in address field, where <servername> is the site DBXL is installed.
3. Click Go. The File Download dialog should appear.
4. If prompted, click Open.

b) Navigate to the Licenses view in DAT

1. Click on the Configure Licenses icon on the left hand side of the DAT header. The Licensing view will load. If this is a new installation of DBXL, you might see the message No License Packs Installed, unless you have downloaded a version of DBXL v2.2 that comes with a Trial license pre-configured.

c) Configure a new license

1. In the Add License Pack table, click on Click here to attach a file under the License File column. Note that this field will only allow valid, base64-encoded binary data files.
2. In the Contact email column, enter the email associated with the License Pack you have selected in step 4.

3. Click on the Add License icon.
4. You will receive a dialog notification that says License Pack successfully added; click OK to dismiss it. A table called Installed License Packs will display, showing the Serial number of the license, and the name and contact email, as well as the allowed number of Document Types and Documents. Also note the expiration date of the license: you will need to attach another valid license before the expiration date so that you have continued use of DBXL.

5. Click on Catalog to return to the catalog view of the DAT.

Note that only members of DbxlAdmins are able to manage licensing.

DBXL v2.2 Getting Started

ErnestoM — Mon, 30 Jun 2008 22:32:06 GMT

For a fully formatted version of this document, please click the Download link above. Visual formatting has been toned down for html publishing.

This short, post-installation tutorial will guide you through some common tasks so that you can quickly begin using Qdabra Database Accelerator (DBXL). The following tasks will use the ExpenseReport form that ships with InfoPath 2007.

Task 1: Prepare Sample Form – Expense Report

1. Customize the Expense Report sample.

a. Start InfoPath and select Customize a Sample.
b. Select Sample – Expense Report.
c. Click on Design this form.

2. Publish to your local machine.

a. Select File > Publish. InfoPath will prompt you to save the form.
b. Enter c:\ExpenseReport-old.xsn, or any location on your local hard drive, and click Save.
c. In the first screen of the Publishing wizard, select the radio button for To a Network Location.
d. Click Next.
e. Enter a path to publish to. For the purposes of this document, we assume c:\ExpenseReport2.xsn.
f. Click Next twice, and then click Publish.
g. Click Close to close the wizard.

Task 2: Attach a License

Before you can begin using DBXL, you must attach a license. Note that DBXL comes with a Trial license, so these steps should not be necessary. However, you may follow these steps to add a license you have purchased. Note that only members of DbxlAdmins are able to manage licensing.

1. Launch the DBXL Admin Tool (DAT).

a. Open Internet Explorer.

• Note: Vista users need to run Internet Explorer as Administrator.
• You can run this process on a different machine, just make sure that http://<servername> is in the intranet or is set as an intranet site in the IE security settings.

b. Enter http://<servername>/QdabraWebService/forms/DAT/template.xsn in address field, where <servername> is the site DBXL is installed.
c. Click Go. The File Download dialog should appear.
d. If prompted, click Open.

2. Configure the DBXL License.

a. Click on the Configure Licenses icon on the left hand side of the DAT header. The Licensing view will load.

b. In the Add License Pack table, click on Click here to attach a file under the License File column. Note that this field will only allow valid, base64-encoded binary data files.
c. In the Contact email column, enter the email associated with the License Pack you have selected.

d. Click on the Add License icon.
e. You will receive a dialog notification that says License Pack successfully added; click OK to dismiss it.

A table called Installed License Packs will display, showing the Serial number of the license, and the name and contact email, as well as the allowed number of Document Types and Documents. Also shown is the expiration date of the license.

If the license allows for the use of the Active Directory Web Service (ADWS), a second table will display showing the license granting permission for ADWS.

f. Click on Catalog to return to the catalog view of the DAT.

Task 3: Verify Installation Succeeded

1. Create a new configuration in DAT.

a. In DAT, click on New Configuration.
b. Type ExpenseReport2 into the Name field. This is the Document Type name.
c. Under InfoPath Form Template, click on Click here to attach a file.
d. Enter c:\ExpenseReport2.xsn and click Insert. The DAT will attach the XSN file.
e. Click Save. The DAT will confirm the operation through a dialog box. Click OK to close it.
f. Click Catalog.

2. Verify that you can open the form.

a. In the ExpenseReport2 row click the InfoPath icon under Open. The form will open and you will be able to fill it out.

b. Close the form.

Note: We will test submit in an upcoming task.

Task 4: Add Active Directory Lookup to your Form

Active Directory includes a wealth of information about your company’s organization. This task will show you how to auto populate fields in your InfoPath form with the email address and full name of the currently logged on user.

1. Open your form template.

a. In InfoPath, click on File > Design a Form Template.
b. Click on On My Computer in the left task pane.
c. Enter the path where you stored the newly created form, which is C:\ExpenseReport2.xsn, and click Open. ExpenseReport2 will open in Design mode.

2. Add the Active Directory Data Connection to your form.

a. Click Tools from menu and select Data Connections.
b. Click Add.
c. Select the radio button to Create a New Connection to and Receive Data. Click Next.
d. Select the radio button for Web Service. Click Next.
e. Enter the URL of the service: http://<servername>/QdabraWebService/ADUserInfo.asmx. Click Next.
f. Select the operation (Web Method) named GetMyInfo. Click Next.
g. Click Next. There is no need to check the checkbox of Store a copy of the data in the form template.

h. Click Finish, making sure that the Automatically retrieve data when form is opened is checked, and then click Close.

3. Change the Email Address field to auto-populate.

a. Double click on the Employee E-mail Address field in the view.
b. In the Default Value section, click on the fx button to the right of the field.
c. Click Insert Field or Group.
d. Select the GetMyInfo (Secondary) data source from the dropdown
e. Expand myFields/dataFields/tns:GetMyInfoResponse/GetMyInfoResult/ADProp
f. Select the Value node.
g. Click Filter Data.
h. On the Filter Data dialog, click Add.
i. Select Key in the first drop down.
j. Leave the second dropdown as is equal to.
k. In the third dropdown, select the option Type text, then type mail. Notice that InfoPath adds double quotes after you type and tab out.

l. Click OK five times to close the dialogs

4. Change the Name field to auto-populate. Note that these will be very similar to Section 3 above.

a. Double click on the Name field in the view.
b. In the Default Value section, click on the fx button to the right of the field.
c. Click Insert Field or Group.
d. Select the GetMyInfo (Secondary) data source from the dropdown.
e. Expand myFields/dataFields/tns:GetMyInfoResponse/GetMyInfoResult/ADProp
f. Select the Value node.
g. Click Filter Data.
h. On the Filter Data dialog, click Add.
i. Select Key in the first drop down.
j. Leave the second dropdown as is equal to.
k. In the third dropdown select Type text, and then type the text cn. Notice that InfoPath adds double quotes after you type and tab out.
l. Click OK five times to close the dialogs.

5. Save the form back to DBXL and verify the results.

a. Select File > Save, and then close the form.
b. Switch back to DAT and click the icon in the Edit column for the ExpenseReport2 Document Type row.
c. Attach the updated InfoPath form and click Save. Click OK to dismiss the confirmation dialog.
d. Click Catalog, and then click the InfoPath icon under Open for the ExpenseReport2 Document Type row.
e. Verify that the fields are auto-populating correctly.

Task 5: Add Database Submit

1. Open your form template.

a. In InfoPath, click on File > Design a Form Template.
b. Click on On My Computer in the left task pane.
c. Enter the path where you stored the form, which in our example is C:\ExpenseReport2.xsn, and click Open. ExpenseReport2 will open in Design mode.

2. Configure a Submit button to use the DBXL web service. (If your form, like the ExpenseReport sample, already has Submit button, skip steps a and b.)

a. Click Controls in the task pane.
b. Click and drag a button control and drop it in your form’s view.
c. Double click the button to display properties.
d. Click on Submit Options.
e. Click dropdown and select Web Service from the dropdown.

3. Add the Qdabra DBXL Web Service to the form.

a. In the Submit Options dialog, click the Add button to add a data connection.
b. Type in the location of the Qdabra DBXL Web Service in the format http://<servername>/QdabraWebService/DbxlDocumentService.asmx.
c. Click Next. InfoPath will contact the server.
d. In the list of web method operations, choose the web method to use for submitting the form, which is called SubmitDocument.
e. Click Next.

4. Configure the parameters.

a. Ignore the first parameter, called tns:docTypeName. It will default to the DocType of the form.
b. Select the second parameter, named tns:xml.

i. Under Parameter options select the Entire form (XML document, including processing instructions) radio button.
ii. Check the Submit data as a string checkbox.

c. Select the tns:name parameter.

i. Select the radio button Field or Group in the Parameter options section.
ii. Click the button next to the Field or Group text box. The Select a Field or Group dialog will appear.
iii. Select the expenseReport/employee/name field and click OK.

d. Select the tns:author parameter

i. Select the radio button Field or Group in the Parameter options section
ii. Click the button next to the Field or Group text box. The Select a Field or Group dialog will appear.
iii. Select the expenseReport/employee/emailAddress node and click OK.

e. Select the tns:description parameter.

i. Select the radio button Field or Group in the Parameter options section
ii. Click the button next to the Field or Group text box. The Select a Field or Group dialog will appear.
iii. Select the expenseReport/purpose node and click OK.f. Click Next. Click Finish. Click OK. Click OK.

5. Save the updated form.

a. Click Save on the File menu.
b. Close the form.
c. Click Edit Configuration for ExpenseReport2 in DAT.
d. Attach the updated form and click Save.

6. Verify Submit works.

a. Click on the Document tab, and then click New.
b. Fill out the form including the Business Purpose, Employee Name, and Employee Email Address fields. When done, click the Submit button.
c. Click Refresh in DAT. The new document is added with the Name, Author, and Description data populated from the Document tab.

Task 6: Specify a Reference ID for your Form

1. Open the DBXL Administration Tool (DAT).
2. Click on the Edit button for the Document Type ExpenseReport2.
3. Change the Base Reference # under the Ref. ID table.

4. Click on Save. A dialog will confirm that the changes were saved. Click OK.
5. Click on Catalog.
6. Open a new form by clicking the Open icon for Document Type ExpenseReport2.
7. Fill out the form and submit it using the Submit button.
8. Click on the Edit button of the Document type ExpenseReport2 in DAT.
9. In the General tab, verify that Base Reference # has increased.
10. Click on the Documents tab, where you can check the Ref. ID number for each document submitted.

Task 7: Add “My Forms” Web Part to a SharePoint Web Page

SharePoint 2003

1. Add the new MyForms Web part to a page.

a. Open your local SharePoint site and click on Create in the top menu.
b. Under Web Pages click on Web Part Page.
c. Enter the Name of the web part page, select Full Page, Vertical in Choose a layout template, and click Create.
d. In the Web Part List click Filter, then select Web Parts in the Show dropdown.
e. Drag and drop MyFormsWebPart into the body of Web Part page placeholder area.

2. Configure the MyForms Web Part.

a. Click the small triangle at the top right of the MyFormsWebPart and select Modify Shared Web part.
b. Change the Web Service URL to point to the DbxlDocument Web Service for your DBXL installation (http://<server>/QdabraWebService/DbxlDocumentService.asmx).
c. Click Apply. This will create the link to your DBXL installation.
d. Select the Document Type for the Expense Report template you deployed to DBXL.
e. Uncheck Show only my documents and click OK.

SharePoint 2007

1. Add the new MyFormsWebPart to a page

a. Click on Site Actions and then click on Create.
b. Click on Web Part Page under Web Pages.
c. Enter the name of the new web part page.
d. Under Choose a Layout Template select Full Page, Vertical and then click the Create button.
e. Click Add a Web part.
f. Under the Miscellaneous category, select the checkbox for MyFormsWebPart and then click the Add button.

2. Configure the My Forms Web Part

a. In the MyFormsWebPart title bar click Edit and then click Modify Shared Web Part.
b. Change the Web Service URL to the correct URL for your instance of DBXL. Click Apply.
c. Select the Document Type for the Expense Report template you deployed to DBXL and uncheck Show Only My Documents. Click OK.
d. Click on Edit in the MyForms Web part and click Modify Shared web part.
e. Click on the + sign next to Appearance and change the value in the Title text box to Expense Report.
f. Scroll up to the Column Display Selector area and uncheck all the checkboxes for the columns you do not want to see. Change the ordering of the columns as desired and click OK when finished.

Task 8: Setup a button on SharePoint to open your form

These instructions are written for SharePoint 2007. The steps are similar for SharePoint 2003.

1. Navigate to the Expense Report web part page created in the previous task.
2. Click Site Actions, and then select Edit Page.
3. Click Add a Web part. Select Content Editor web part under the Miscellaneous category. Click the Add button.
4. Click the Edit button of the Content Editor Web Part and click Modify Shared Web Part.
5. Click the Source Editor button
6. Copy the following text and paste in the source editor window.

<script>
var strTemplate = "http://<server>/qdabrawebservice/Forms/expensereport2/template.xsn";
var strSaveLocation = "http://<server>/qdabrawebservice/Forms/expensereport2";

function CreateNewRequestForm()
{
    // Based on WPQ3combineDocuments()
    var objOpenXMLDoc = new ActiveXObject("SharePoint.OpenXMLDocuments.1");
    var bSuccess = false;
    bSuccess = objOpenXMLDoc.CreateNewDocument(strTemplate, strSaveLocation);
}

</script>
<input id="btnCreateExpenseReport" onclick="CreateNewRequestForm()" type="button"
value="Create ExpenseReport" name="btnCreateExpenseReport">

7. Modify the URLs in strTemplate and strSaveLocation by replacing <server> with the machine name DBXL is installed, and click the Save button.
8. Click the + sign next to Appearance and in the Chrome Type dropdown select None, and then click OK in the configuration pane.
9. Click on Exit Edit Mode, and then click on the Create ExpenseReport button you just added. Your form corresponding to this Expense Report Document type will open.

DBXL v2.2 Release Notes

ErnestoM — Mon, 30 Jun 2008 22:24:59 GMT

These Release Notes were last updated on September 16, 2008. For a fully formatted version of this document, please click the Download link above.

INSTALLATION

DBXL can only be installed on machines that are part of a domain

To install DBXL, your machine must be part of a domain. To verify, go to Start and right click My Computer and choose Properties. Select the Computer Name tab and click Change. Verify that your machine is part of a domain. Workgroups will not work. You may still choose to install DBXL on a non-domain machine but, as a result, parts of DBXL that deal with authentication (such as the AD service) will no longer work.

ASPNET must have permissions on the SQL database

When installing DBXL on a Windows XP Professional machine, ASPNET must have permissions on the SQL database in order to correctly configure and use the Qdabra sample forms.

Error message during installation when DBXL database contains a space

Installation of DBXL will fail when the database name entered contains a space. As a workaround, use a database that does not contain spaces in its name.

Page Not Found Error after installing DBXL

If attempting to access the DBXL Web Service ASMX pages after installing returns a Page Not Found error, and you have installed DBXL to a port other than 80, make sure that you have unblocked that port from the network’s firewall.

There is another situation in which this error may appear: when the website is configured to use multiple host names and IPs. The workaround is to temporarily remove all but the primary hostname and and IP, install DBXL and then restore the additional hostnames/IP addresses.

DBXL Installation Produces an HTTP Error 404

If you encounter an HTTP Error 404 during DBXL installation, please check that ASP.NET is enabled in the web service extensions of IIS manager. When setting up the server where DBXL is going to be installed, there is an option to allow ASP.NET applications under Windows Components Application Server. This needs to be installed in order for the software to install and run correctly.

DBXL Installation Produces an HTTP Error 405 on Windows XP Machine

Although this error could happen on any machine that is not correctly configured, the most likely situation is a Windows XP Pro machine that has just recently been configured to run the DBXL Web Service. The problem is caused when ASPNET has not been registered with IIS. This happens when .NET 2.0 is installed before IIS. To remedy this problem, run aspnet_regiis.exe -i found in C:\WINDOWS\Microsoft.NET\Framework\(Version)\.

The error message given during DBXL installation.

Install DBXL on the same site as SharePoint

If you have SharePoint installed, make sure to install Qdabra’s Database Accelerator on the same site that hosts the main SharePoint site (typically on port 80). It isn’t common for SharePoint sites to reside on ports other than 80 (except for the SharePoint Administration site and MySites).

Issues with Skype or other Applications which use ports 80 or 443

We have seen issues with DBXL installations where Skype or other applications, which use common communication ports, are installed and can conflict with Internet Information Server. Some applications may use ports 80 (http) or 443 (https) to communicate. If these are installed prior to IIS, then IIS does not have complete access to these ports. This can cause a 404 page when trying to access a hosted web page on the local server, and may also generate errors when starting a website.

To remedy, uninstall the application and verify that IIS is serving pages properly. Skype can be reinstalled if necessary and will choose a different port if IIS is already using the common ports.

SQL setup produces a red flag on environment check on IIS configuration

On IIS 7, users may find they are unable to install a web setup MSI on a Windows Vista machine without generating any useful error messages. The workaround is to:

1. Uninstall SQL
2. Go back to IIS setup, and add features as seen in screenshot below.

3. Reinstall SQL
4. Make sure there are no red flag on environment check.

Only the person that installed Qdabra DBXL can uninstall it

If you plan to use the Qdabra DBXL Web part to display files in your SharePoint Web pages, you will want to install the Qdabra DBXL Web Part. However, only the person that installed it can uninstall it. To allow anyone to uninstall, you will have to use a special command to run the installer:

1. Go to Start > Run.
2. Type cmd and press Enter.
3. Use the cd command (change directory) to navigate to the folder where you downloaded the Microsoft Installer (MSI) file for the Qdabra MyForms Web Part.
4. Type the following command and press enter: msiexec.exe /i "Qdabra MyForms Web Part.msi" allusers=1

DBXL will assume SSL port number when installing on a site with https

If you install DBXL on a website configured to use https but change the configuration to http later and reinstall, you will receive the error “Could not initialize the database.” When you configure the web site to use https it is storing the port number as 443. When you remove the server certificate from the default website and reconfigure it to use http, it is not removing the SSL port number from that default website. To prevent this problem, you will have to remove the port number manually:

1. Open Inetmgr.
2. Open the properties of the web site which was configured to use https.
3. Delete the SSL port number.
4. Click on the Apply and OK buttons.

Eventlog shows a SQL connection error using the Shared Memory Provider

During installation you might encounter an error that reads: The installation failed, and the rollback has been performed. --> Error initializing DBXL database. --> Cannot initialize database 'QdabraDBXL' on server '<servername>'. See eventlog for details. In Event Viewer, the details of this error read: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.
The workaround requires disabling the shared memory protocol for SQL Server using the configuration tool. This should only be seen when SQL server and DBXL are on the same machine. Please check this on any installation failures where the SQL connection cannot be established during setup.

Installing v2.2 simultaneously with v2.1

If DBXL v2.1 is already installed, you must create a new directory and choose it to install DBXL v2.2. Make sure to also specify different names for the databases DBXL will create during installation.

Upgrading DBXL produces blank Form Versions in DAT

After successfully upgrading from an earlier version of DBXL, you might see a blank Form Version in the catalog view of DAT. To fill this cell with the appropriate value, click to Edit the docType, and then save it again. This will refresh to docType in DBXL and generate the necessary information to fill the column.

PERMISSIONS

Using non-default values for permissions during install may prevent DAT installation

If, during install, you receive the error "Error publishing Admin Tool: Access Denied", publish DAT manually by logging in to the server and invoking the "PublishDATFormTemplate" Web method. This method is included in the DBXLAdmin web service, which can generally be found at http://servername/qdabrawebservice/DBXLAdmin.asmx.

Users must have Read permissions for the Document Type

The QueryDocuments web method requires Read permissions for the Document Type. If users have only Document Level Read permissions, the QueryDocuments web method will return Access Denied. This limitation will be addressed in a future version of Qdabra DBXL.
Changing document level permissions requires a reshred

If you add or change document level permissions for a configuration in DAT, the permissions will not be enforced for documents that were created previous to the permissions change. Reshredding documents is a required step to update existing documents.

L-Read DocType Level permissions aren't implemented

The L-Read checkbox seen in DAT's Permissions view is meant for future use. Please use L-Write if you wish you assign lock permission to a user.

DAT

Firefox is not supported

DBXL does not support opening and locking forms from Firefox. Please install Internet Explorer.

HTTPS: DAT will not open directly via HTTPS

After installing DBXL, the default web page should appear. If when clicking on the DAT link you do not see an Open button, please click Save and save the XSN to your desktop. You can then open DAT from your desktop by double clicking the saved file.

Do not include special characters in Document Type name

If the name of your DocType contains special characters (for example: !@#$%^&*) you may experience problems opening it. To workaround this limitation, please use a DocType name that does not include special characters.

Event Viewer Log Set To "Overwrite Events As Needed" and Maximum Log Size of 2048Kb

To preserve more error events in your event log, open eventvwr.exe (Start->Run->eventvwr.exe), right click on Qdabra and select Properties. Change the default settings as desired.

Solutions using 2007 OM will not work if opened directly from DAT

Because DAT is written using 2003 InfoPath OM, users will experience problems when publishing and opening forms created from 2007 OM unless they are marked as Full-Trust.

DATABASES

User encounters “Database not registered for use" error when calling QueryDB

Before you can begin using QueryDB, the database being queried needs to be added to the configuration/qdabra.dbxl/enumdb/databases node in web.config. The SQL server indicated during installation (where QdabraDBXL and QdabraSamples are located) is already configured, but any additional databases must be added individually, like this: <database alias="DB_Alias" name="SampleDB" server="default" />

SQL default database not set

After restarting SQL server service and/or IIS, you might encounter an error that reads "Shared Memory Provider, error: 0 - No process is on the other end of the pipe". Log into SQL Server under another admin login and check the properties under the usual login. If you find that the default database is not set, reset the default database and log back in under the usual account.

Changing the DBXL database connection string after installation

If you change the ConnectionString in the web.config to reference a different database after install, you must invoke the InitializeDatabase Web method of the DbxlAdmin.asmx page to create/update the database schema.

The InitializeDatabase Web method can be found in the DbxlAdmin Web Service (for example, http://localhost/QdabraWebService/DbxlAdmin.asmx?op=InitializeDatabase). Navigate to the Web method from the server and click on Invoke. You can also call the Web method by creating a blank InfoPath form and querying it, but you will have to have administrator privileges.

Shredding without a key returns error in database mapping

Mapping a form to a SQL database requires the existence of either a key column or an identity column. If the table does not have an identity column, and the user does not designate a column as the “key” column, DAT will return a validation error to the user. For more information on these scenarios, see the document called Shredding Without Key Returns Error in Database Mapping.

Mapping: DocIDs don't work if database column has Identity set to Yes

When you map the DBXL::DocID to a column in your database, make sure the column does not have Identity setting of "Yes". If so, SQL will try to automatically set the value and thus prevent the DBXL Web Service from setting it leading to an error. You should never map a value into an Identity column in the database, because the database takes care of populating this column.

DBXL does not support 'yes' and 'no' as boolean values

When shredding boolean values into a database, DBXL does not support 'yes' and 'no' as boolean values. When shredding into ‘bit’ types in the database, the DBXL mapping should be ‘Boolean’ and the XML being submitted should set the field to either ‘1’ or ‘true’ and ‘0’ or ‘false’.

Cannot delete documents when there is a mapping error

If a Document Type contains mapping errors, deleting a document in that Document Type will fail. Deleting the Document Type itself will also fail, because DAT attempts to delete all documents before deleting the Document Type. Please see the document called Can't delete when there are mapping errors for a workaround.

QFORM

qForm requires .NET Framework 2.0 or later

If you encounter the following error when opening a DBXL document, your machine does not have .NET Framework 2.0 installed.

Form template: http://<servername>/QdabraWebService/Forms/<DocTypeName>/template.xsn

InfoPath cannot open the selected form because of an error in the form's code.
The format of the file 'Qdabra.Common.dll' is invalid.
This scenario is most common when using InfoPath 2003 SP2.

Deleting Documents within qForm

When a user deletes a document within a qForm-based solution, the full assignment history is not deleted. This might result in qForm displaying a user in the Assigned To list in the Search taskpane, even though that user does not have documents assigned to them. Please see the document called Deleting Documents and Flow for a qForm.

Searching for a DocID does not work for newly saved documents

DBXL stores DocIDs in the XML of your form, but not on the initial save of the document. The first time you save the document, DBXL doesn't know the DocID because the form has not been stored in SQL yet. In this case, the XML will just contain "" for DocID.
When opening a document, DBXL always populates the DocID field, as it is needed for internal purposes, and it’s stored in the Processing Instruction. Subsequent saves of the document will save the DocID and allow it to be searched via the regular text search.If you want to search for a document, don't type the DocID into the search string. Instead, use metadata search.

Schema Changes in QdCatalogBase cause an Error Message

Making schema changes, such as renaming a node, when designing the QdCatalogBase form causes InfoPath to issue an error. This happens because InfoPath detects the built-in code that comes with the form, but it does not have the source code to update the references. However, you can safely click Ignore on this error. If you would like to stop the error message from displaying, create a new blank InfoPath Form Template project in Visual Studio and specify to use the QdCatalogBase.xsn file for the template.

SHAREPOINT

Web part doesn’t render after adding to SharePoint 2007 sub site page

If the Web part shows an error, it may be due to security trust settings on your SharePoint 2007 server. Go to the virtual directory on the server where SharePoint is installed and navigate to the bin directory where you will find Qdabra.Dbxl.Webparts.MyForms.dll. Open a cmd shell and run “gacutil –” on this dll to add it to the Global Assembly Cache so that SharePoint trusts it for sub sites.

Can't open forms when clicking on icon

If the form cannot be opened correctly from the SharePoint web part please make sure that the WebDAV extension is prohibited. You can do this by following the steps below

1. Go to the IIS Manager
2. Open the web service extension
3. Check if WebDav extension is prohibited
4. If it’s not prohibited, then prohibit it

Digitally Signing documents for use in DBXL

To track documents, DBXL inserts a processing instruction into the XML on submit, which includes a unique DocID. After initial insertion, the DocID is used to identify the document when it is resaved, deleted, or reshredded. As a result of this insertion, you cannot digitally sign a document before submitting it for the first time. To workaround this, please read the document called How to use Full Trust form templates in DBXL, which includes a tool that allows for a workaround.

NOTIFICATIONS

Notifications email is delivered into the Junk e-email folder

Outlook or other mail software may classify notification email as junk email. To avoid this, add sender to the “safe list” of your mail software. In the case of Outlook, follow these steps:

1. Right click on the email that was delivered to the Junk e-mail folder.
2. Choose Junk E-mail, click Add sender to Safe Senders List.

WEB SERVICES

QueryDB uses the credentials of the web service instead of those of the querying user

QueryDB currently only uses permissions that are defined on the SQL Server that it is querying. Because QueryDB web service acts as a liaison between the end user and the database, the database only receives requests from the web service. This means that any user accessing the web service has the same permissions as the user account (generally NETWORK SERVICE) that the web service is running as. Since most users have less permissions as the NETWORK SERVICE account, this is considered an Elevation of Privilege security hole. One way to reduce the risk is to create a new account for the web service to run as, and only allow that account access to query the DB. Qdabra will address this issue in a future release.

Using QueryDB with a dynamic SQL table

If your SQL table(s) have the potential to change (for instance, adding a new column), you should have QueryDB access a SQL view instead of directly accessing the table. This will allow the underlying table to change and small modifications to the view will prevent your InfoPath solution from breaking.

In addition, when building a query in Query Builder and using the query in GetColumnsXMLStrQuery, make sure to specify all of the columns you wish to retrieve. InfoPath attempts to derive the schema of the table; therefore, adding a column to the table will break the Data Connection in your form.

Active Directory query fails on Windows XP

If you install DBXL to Windows XP and you cannot query the Active Directory Web service (ADUserInfo.asmx) you will have to manually configure your machine’s ASPNET account. To verify that this is the problem, navigate to http://machine/QdabraWebService/ADUserInfo.asmx, click GetMyInfo and Invoke. If you don’t get XML you will need to follow the configuration steps detailed in this document.

Importing documents with their RefIDs intact

The ImportDocuments method allows the user to import documents with their RefID intact. To do this, a data connection to the service must be manually created, with the importExistingRefId parameter set to "true". The Document Type's "XPath to inject RefId to" field must be filled out with an appropriate XPath. Note that once the RefID XPath has been established, changing it will break previously submitted documents.

Cannot remove document types that contain resources

After using DbxlResource web service to create, configure and use a new xml resource, you will receive an error if you attempt to delete the Document Type Configuration for which you have created the Resource. Before deleting such a Document Type, you must first delete the resource itself using the DeleteResource operation in DbxlResource.

MISCELLANEOUS

Removing clutter from the Qdabra Event Log

To help form developers debug their form mappings, DBXL logs informational messages to the Qdabra Event Log when a node is not found in the XML. If you form includes optional sections, a node missing from the XML is common scenario so these messages will create unnecessary clutter. To stop these messages from being logged, set the logShredWarnings value in the web.config to false.

MyForm Webparts does not work with IPFS

MyForm Webparts is provided for backward compatibility only, and the best practice for new solutions is to use dataviews, since IPFS cannot open documents that reside outside of a form library.

Uninstalling Qdabra's Query Builder InfoPath form tool

Qdabra's Query Builder InfoPath form tool needs to run with full trust so that it can execute shell commands. To install this full trust tool on your local computer, we use InfoPath’s built-in support for URN based solutions. When the form is installed, InfoPath adds entries to your Windows registry. Unfortunately, due to a bug in InfoPath installer, sometimes uninstalling doesn’t work and the registry entries are not cleaned up correctly. Please see this document for help.

DBXL v2.2 Setup Instructions

ErnestoM — Mon, 30 Jun 2008 22:20:45 GMT

For a fully formatted version of this document, please click the Download link above. Visual formatting has been toned down for html publishing.

Pre-requisites for the Machine

Before installing Qdabra Database Accelerator Suite (DBXL), make sure that your environment meets the requirements needed for the scenario you are targeting.

Server Scenarios

Local Standalone – for developer debug and testing

Windows XP Professional or Windows Server 2003, or Windows Vista Business or Vista Ultimate
MSDE or SQL 2000 with SP4 or SQL EXPRESS, SQL COMPACT or SQL 2005
IIS 5.1 or IIS 6.0
.NET Framework 2.0

Domain Database – for teams that don’t use SharePoint

Windows XP Professional or Windows Server 2003, or Windows Vista Business or Vista Ultimate
MSDE or SQL 2000 with SP4 or SQL EXPRESS, SQL COMPACT or SQL 2005
IIS 5.1 or IIS 6.0
.NET Framework 2.0

If SQL server and DBXL are on separate servers, use SQL Authentication. To use Windows Authentication, you will need to:

Give the server machine account where the Web Service is installed sysadmin access to the SQL instance.
Run ASPNET under a domain account.

Domain SharePoint – for teams that use SharePoint

Same as Domain Database, except Windows XP/Vista, which do not host SharePoint
Windows SharePoint Services 2003 or 2007

Important considerations:

• The user who installs DBXL must have permission to create databases in SQL.
• When installing DBXL on a Windows XP Professional machine, ASPNET must have permissions on the SQL database in order to correctly configure and use the Qdabra sample forms.
• To use the SharePoint Web Part that ships with DBXL you must install the suite on the same machine as Windows SharePoint Services.
• To use a domain account for the Application Pool (which grants the Web Service the ability to access other resources on the network) make sure that account is added to IIS_WPG.
• There is a known bug in Vista WebDAV redirector for client machines accessing Web Services. Therefore, if you have users running Vista, you must install the DBXL WebDAV handler on the root of the server where DBXL is installed. Those steps are discussed below. When installing on a machine that also has SharePoint, we recommend setting up DBXL on a separate website from SharePoint (using a different port or host headers).

Client Scenarios

• Windows XP or Windows Vista
• Office 2003 or 2007
• InfoPath 2003 or 2007
• Outlook 2003 or 2007
• Internet Explorer 6.0 or higher (Firefox is not supported)
• Set http://<servername> as a local intranet site in Internet Explorer’s security settings if the site is not in the intranet.
• Domain authentication for users (such as VPN)

Pre-Installation Release Notes

Only the person that installed Qdabra DBXL can uninstall it

If you plan to use the Qdabra DBXL Web part to display files in your SharePoint Web pages, you will want to install the Qdabra DBXL Web Part. However, only the person that installed it can uninstall it. To allow anyone to uninstall, you will have to use a special command to run the installer:

1. Go to Start > Run.
2. Type cmd and press Enter.
3. Use the cd command (change directory) to navigate to the folder where you downloaded the Microsoft Installer (MSI) file for the Qdabra MyForms Web Part.
4. Type the following command and press enter: msiexec.exe /i "Qdabra MyForms Web Part.msi" allusers=1

DBXL will assume SSL port number when installing on a site with https

If you install DBXL on a website configured to use https but change the configuration to http later and reinstall, you will receive the error “Could not initialize the database.” When you configure the web site to use https it is storing the port number as 443. When you remove the server certificate from the default website and reconfigure it to use http, it is not removing the SSL port number from that default website. To prevent this problem, you will have to remove the port number manually:]

1. Open Inetmgr.
2. Open the properties of the web site which we configured to use https.
3. Delete the SSL port number.
4. Click on the Apply and OK buttons.

Installing v2.2 simultaneously with v2.1

If DBXL v2.1 is already installed, you must create a new directory and choose it to install DBXL v2.2. Make sure to also specify different names for the databases DBXL will create during installation.

Install the Qdabra Database Accelerator Web Service

1. Double-click on the installation msi file. If installing on Vista, run the installer as Administrator.
2. Click Next in the welcome screen.
3. After reviewing the End User License Agreement, select I Agree and click Next.
4. In the Installation Address screen, select the site for installation from the dropdown and enter the name for the Virtual Directory. Click Next.
5. In the Confirm Installation screen, click Next. You will see a bar indicating the progress of the installation.
6. The Log On tab allows you to indicate the account that will run DBXL:

a) Select between Predefined and Configurable account credentials, noting that if you select Configurable account credential you must provide an Account and password.
b) Click Next to proceed to the following tab.

7. In the SQL Server tab, you will indicate the database where DBXL will store all documents:

a) Enter the SQL Server name. For example, in the case of a SQL Express installation, this will be (LOCAL)\SQLEXPRESS.
b) Select the Authentication type used to access the SQL server from the dropdown

• If you select SQL Server Authentication, fill out the User name, Password and Confirm password fields.

c) Enter the Database where DBXL documents will be stored.
d) Click Next to proceed to the following tab.

8. In the Document Security tab, you can set up permissions for DBXL. For more information on Permissions, see the document titled Understanding DBXL Permissions:

a) Enter the DBXL Admin security group name. The members of this group can add document types and manage access permissions to DBXL document types
b) If you check Set Global User Permissions checkbox, the users in this group will have access to all the documents in the DBXL.
c) If you uncheck Set Global User Permissions checkbox, you will have to set permission on individual document types, since these Global Permissions will not be enforced.
d) Click Next to proceed to the following tab.

9. The Active Directory Service is used to obtain username and other Active Directory Information:

a) In LDAP Path textbox, the default value is populated from the system when a domain controller can be contacted.
b) Alternatively, enter the LDAP Path (for example: LDAP://DC=DomainName,DC=com) when domain controller is not in contact.
c) Click on Next to go to the following tab.

10. QueryDB will allow InfoPath forms to query the database tables to populate dropdown lists and other form fields.

a) Enter the default SQL Server name to which DBXL will connect.
b) Select the Authentication method from the dropdown list.

• If you select SQL Server Authentication, enter the User name, Password and then Confirm password.

c) Enter the Default database to be used for queries.
d) Click on the Test Connection button to test the values entered.
e) Click Next to proceed to the following tab.

11. The Samples tab lists the tables that the DBXL installer will create by default. You may change the name of the QdabraSamples database if you wish to rename it.
12. Click on Finish to continue the installation.
13. Click on Close in Installation Complete screen to complete the installation.

Install QdabraMyFormsWeb Part

To obtain this package, go to http://www.infopathdev.com/ and click Downloads, then click Qdabra Database Accelerator under Browse Files. You will see packages for SharePoint 2007 and for SharePoint 2003.

SharePoint 2003

1. Install the Web part:

a. Save the installation package to the server machine and double click to run.
b. Click on Run in the security warning window when it asks you to run or save the file.
c. Click on Run in the unknown publisher window.
d. Click on Next in the Qdabra MyForms Web part Setup window.
e. Click on Yes on the Qdabra MyForms Web part Setup window.
f. Click on OK to the message Installation was successfully completed.
g. After Web part is installed successfully click on Start > Run.
h. Enter cmd and click OK.
i. Enter iisreset in command prompt and click Enter.
j. Exit the Command Prompt after IIS is restarted successfully.

2. Add the DBXL My Forms Web part to the SharePoint Web Part Gallery:

a. Go to the local SharePoint site.
b. Click on Site Settings.
c. Click on Go to Site Administration.
d. Scroll down and click on the Manage Web Part Gallery link.
e. Click on New web part option.
f. Scroll down and select Qdabra.Dbxl.Webparts.Sharepoint.MyForms.MyFormsWebpart option
g. Scroll back up and click on the Populate Gallery button.

SharePoint 2007

1. Copy Web Part Binaries

a. Click on Start > Run.
b. Enter inetmgr in the Open dialog box and click OK.
c. Expand Machine name (Local Computer) and then expand Web Sites.
d. Go to SharePoint (80) and click on Open to go to the appropriate <GUID> directory
e. Create a directory with the name bin and copy Qdabra.Dbxl.WebParts.MyForms.dll and the config file of Qdabra.Dbxl.WebParts.MyForms.dll.config
f. Right click bin and choose Open. Keep this window open for step below.

2. Modify web.config:

a. Move one folder up and open web.config.
b. Add the Safe control line:
<SafeControl Assembly="Qdabra.Dbxl.WebParts.MyForms, Version=2.0.0.1, Culture=neutral, PublicKeyToken=3af9aaaa5e0e3242" Namespace="Qdabra.Dbxl.WebParts.MyForms" TypeName="*" Safe="True" />
c. Save web.config.

3. Add the webpart to the Global Assembly Cache for the local computer:

a. Select Run from the Windows Start menu.
b. Type cmd and click OK.
c. Type cd %windir%\assembly and press Enter.
d. Type start . and press Enter
e. Drag and drop the Qdabra.Dbxl.WebParts.MyForms.dll form the window opened in step 1f above to the new window.

4. Add the DBXL My Forms Web part to the SharePoint Web Part Gallery:

a. Open your SharePoint site by entering URL http://servername in Internet Explorer.
b. Click Site Actions at the top left of the page, select Site Settings, and select Modify All Site Settings.
c. Click Web Parts under Galleries column.
d. Click New.
e. Scroll down and check Qdabra.Dbxl.WebParts.MyForms.MyFormsWebPart.
f. Scroll back up and check Overwrite File if It Already Exists.
g. Click Populate Gallery.

Optional Components

Qdabra Database Accelerator automatically installs the following components. These installation steps are provided to help you manually install the tools later should you experience problems.

Install Qdabra WebDAV Root Protocol Handler

To workaround a bug in Windows Vista, you may have to install a special WebDAV protocol handler in the root Web site. This is because Windows Vista always queries the root Web site regardless of where your installation lives.

1. Open inetmgr.exe on your server
2. Expand the Web site where DBXL is installed
3. Right click on the QdabraWebService
4. Select open
5. Open the bin folder
6. Copy the Qdabra.Dbxl.WebDAV.dll from this folder
7. Return to Internet Information Services
8. Right click on the default Web site
9. Select open
10. Open the bin folder
11. Paste the Qdabra.Dbxl.WebDAV.dll into this folder
12. Click Start > Run and enter cmd.exe
13. Navigate to the bin folder where you copied Qdabra.Dbxl.WebDAV.dll
14. Add the dll to the Global Assembly Cache for the local computer
15. Open Control Panel and click on Administrative Tools
16. Double click Microsoft .NET Framework 2.0 Configuration
17. Expand My Computer and click on Assembly Cache
18. Click Add an Assembly to the Assembly Cache in the view.
19. In the dialog that pops up enter the path to the dll referenced in the above steps
20. Click OK

We recommend setting up DBXL on a separate Web site from SharePoint. If you are installing on a SharePoint site, you have to install a native ISAPI filter in place of the root WebDAV protocol handler. Follow these steps:

1. Click on Start > Run and enter inetmgr.exe
2. Right-click on the Web site and choose open
3. Navigate to the bin directory in the folder that opens
Note: if the bin directory does not exist, please create one
4. Copy the QdabraDBXLRootWebDAV.dll to the bin folder
5. Return to inetmgr and right click on the Web site, choose properties
6. Select the ISAPI Filters tab
7. Click Add
8. Enter QDAV for the name and browse to the QdabraDBXLRootWebDAV.dll file that you copied to the bin folder above.
9. Click OK
10. Select the newly added QDAV filter
11. Click on the up arrow to move it to the top of the list

Set-up the DBXL Administration Tool (DAT)

DAT is automatically set up during installation of DBXL. However, should you need to setup DAT manually, follow these steps.

1. Open the following URL in IE: http://<servername>/QdabraWebService/DbxlAdmin.asmx
2. Click on Publish DAT Form Template method.
3. Enter the path of the DAT-Template form, which is saved to the local drive. In a default installation, the path will be C:\Inetpub\wwwroot\QdabraWebService\install\DAT-template.xsn.
4. Call PublishDATFormTemplate method by clicking on Invoke button.