InfoPath Dev

I'm currently struggling with the installation of DBXL onto a newly installed server and cannot work out what the problem is.  I've been trying in vain to rectify the issue for the past couple of weeks and am now looking if anyone else can provide an insight into how to get it to work.

I'm running SQL Express 2008 on a Windows 2008 Server with IIS6 Management Compatibility on the web server.  I've also disabled shared memory in the configuration tool on SQL Server Express.

I'm able to get through the application setup, accepting all defaults except changing SQL Server location to be (local)\SQLEXPRESS.

Click finish and the install begins, gets to the bit where it says it's registering with .NET and then fails with Error 2869.

The event log for QDABRA gets to "Creating Qdabra database" then fails at the next step saying "Error initializing DBXL database.  The request failed with HTTP status 401: Unauthorized"

Any help gratefully received.

Hi -- one of the defaults is which account to run DBXL as -- the default is Network Service. You need to give that account permissions to your SQL server so that DBXL can create the necessary databases.

Thanks for the quick response.  Just reinstalling SQL Server at present, but I've tried running it under my credentials before as server/SQL administrator with the same result.  I'll set it all up again though and see if that does it.

A 401 would indicate a problem authenticating with the DBXL webservice not with the database. Is a hostheader defined for the site? 

One would be to access http://server/qdabrawebservice/default.htm before you click Finish on the tabbed setup dialog.  Verify you can authenticate with the page and check if it shows Local Intranet zone or Internet in the status bar.  It should show Local Intranet.

There is also a related KB that is sometimes an issue  http://support.microsoft.com/kb/896861.  This applies if your site uses a FQDN (e.g. mysite.domain.com) and uses the hosts file to map to the loopback address (127.0.0.1).

Hi Jim,

I went to the link that you mentioned in your post and received a :

HTTP Error 401.2 - Unauthorized

You are not authorized to view this page due to invalid authentication headers.

on both the server name and fully qualified server name.  It also shows up as Internet rather than Intranet site.

If I open Windows Explorer and navigate to Default.htm and click to Open the file, then it displays in IE without a hitch!

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.

Hi Jim,

I've done this and the site now shows up as being on the Local Intranet, but still refuses me access.  I assume that it's Windows Authentication I should be using within IIS, but I don't even get a challenge/response box.  Now sure if I've said this previously, but I'm able to navigate to the location using Windows Explorer and open the default.htm page without a hitch, so undoubtedly is something to do with the authentication within ISS.

I enabled TCP/IP within the SQL configuration tool and disabled all shared memory.  Now when I try to get to the qdabrawebservice application I now get:

HTTP Error 500.0 - Internal Server Error

The page cannot be displayed because an internal server error has occurred.

Hello,

We have been using DBXL v2.3 (x64) with the same server specifications, such as windows 2008 (x64), SQL 2008 workgroup (x64), and WSS 3.0 (x64).  We have been having the same issue from the beninning, but I could open DAT from the browser, http://servername/Qdabrawebservice/Forms/DAT/template.xml, I have started DBXL and have been using daily business, and we have more than 5000 documents now.  I am not sure what I am saying may be helphul, but If you can open the DAT, we usually don't need to access default site of DBXL in daily job though you may feel you are losing something from your payment if what you are using is licensed product like us.  But stil DBXL has been helping us to manage data and saving time.

Thanks for the response.  However, I can't even get to the stage where the application installs; it seems to fail each time when trying to initialise the database just after registering with the .NET framework.  Though I'd like to use the application and it would make life much easier for me, I can't do anything until I can prove it works within my specific environment.

Did you try to change database name, such as DBXL3 and DBXLSmaple3.  Our DBXL is using database name, DBXL6 because we have failed several times at installation.

No, I haven't tried that, but my installation doesn't get to the point of creating the databases.

After installing Microsoft SQL Server 2008 Service Pack 1, the process seems to be continuing further than previously.  The error I'm now getting says:

Error initializing DBXL Database.
Unable to connect to the remove server.

However, the SQL instance I'm trying to connect to is the same one as I'm using to install the application.

I've ensured the Browser service is running and that TCP/IP protocol is enabled.  I've temporarily disabled AV.  Any suggestions?

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 machinename\instancename.

Other things to check: 

Verify your logon account (not the service account) is a sysadmin on the SQL instance.  The service account will be granted necessary permissions to the database during install.

Open IE on the server and navigate to the website you are installing DBXL.  Make sure the site shows up in the Local Intranet zone.

I can open the SQLEXPRESS instance using SQL Management Studio set to Windows Authentication using the account I'm using for the install - which has sysadmin role on the SQL instance and is an administrator on the server.

Localhost shows up as being on Local Intranet, once I've manually created a suitable application pool and updated the Qdabra web service to use this in place of the default app pool.