InfoPath Dev

At what appears to be the 90% mark of the installation process, the setup app throws an access denied error. When I click OK, it seems to finish the process but when I attempt to access either the Forms or the QdabraWebService virtual directories I am challenged for authentication. I enter the local administrator account info (which has NTFS permissions to the directories and is a member of the IIS_WPG group) but it doesn't let me in. Heres some detail on the error:

Event ID 2000
Source: Database Accelerator
Description: Error publishing Admin tool: Access denied.

The root website that the app was installed to doesn't have this access issue. I can browse to it, but the Qdabra virtual directories don't let me in. I have gone as far as to change the settings on each virtual directory to match the working root site, but this doesn't solve anything. Something isn't "taking" like it should, so I'm hoping someone has experienced this and found a way to resolve it.

The Web Server has .Net 2.0 installed and registered with IIS. All necessary permission changes have been made; we are using domain accounts for App Pool identity and Anonymous Access account and SQL Authentication (user is a sysadmin on the SQL box). Am I missing something? Here's what our environment looks like:

MOSS 2007 Server
SQL Server (2005 Enterprise)
IIS Web Server <-Installing Qdabra DBXL here

Thanks in advance!

 -Steve

Hey Steve.

This is either a IIS issue or a database issue and probably revolves around permissions.

You are installing DBXL on the same site as SharePoint?

Using an Admin Account and using the local SQL 2005?

Go to the Event Log on the server and send me the text from the errors for the Qdabra Log.

That is usually the first step.

Check to see if a QdabraDBXL database has been created.

Do you have an application pool for the QdabraWebService in IIS?

There should not be a permissions problem with the QdabraWebService directory so I am thinking this is an IIS issue.

Is the site https?

There is a known issue with the website selection dialog that may be causing problems for you.  If you have multiple sites with similar names, 'FOO', 'FOOBAR' 'FOOBAR SSP' you may click on 'FOO' in the dropdown, but 'FOOBAR' gets selected.   You can get around this by using the cursor keys to select the correct site.

Thats what I'm thinking Clay Fox. We opted not to install this on our MOSS Server and are trying to use our Dot Net Development server instead. 

We are using an admin account locally and on SQL Server during the install process.

With a little work, we were able to get the DBXL and Samples databases created on the SQL box.

The application pool created by the install runs as a local admin which is also a member of the IIS_WPG group.

Honestly, I see absolutely no reason why this thing shouldn't work. As far as we can tell, everything has permission to do what it is being asked to do. Yet when accessing the virtual dir, I am challanged for auth and use admin credentials (the same ones being used for the app pool). It gives me 3 shots and fails with an HTTP 401.2 error.

These machines are all members of AD and use host header names. Why would the parent dir work just fine, but the child virtual dir's not let us in? Heres the Qdabra Event Log entry thrown during install (same as above):

Event Type: Error
Event Source: Database Accelerator
Event Category: None
Event ID: 2000
Date:  5/5/2008
Time:  5:04:28 PM
User:  N/A
Computer: APPDEV
Description:
Error publishing Admin tool: Access denied

Jim - We are not using simliar names in our install process. we blow the failed attempts away each time to prevent this sort of thing. and of course, issreset just in case.

Are you using Windows Authentication or SQL Authentication for the database connection?

Is the local admin account being used for the app pool a domain account? 

app pool id is a domain account and we use sql auth

DBXL does not support anonymous access.  The installer should be disabling anonymous access on the QdabraWebService folder installation.

The installer did disable anon access. Among the many things I have been testing, I gave using anon access (using a domain admin account) a shot, but to no avail. I then reset it to require windows auth.

Any more ideas? I can't seem to come up with anything from MS that does me any good on the IIS side..

Hey Steve.

Do you have a fresh IIS environment you can install it in?

It sounds like there is some issue with IIS. The installer usually works without issue for most people, especially on a typical server setup.  Is this a 64bit OS? We do not support that in the current release.

You could try creating an alternative site in IIS and installing the webservices there.  If you are going to be using browser based forms that would be an issue but otherwise would not cause a problem and would at least allow you to do some testing and you could get it figured out for production later.

This environment is totally fresh. The DBXL product was the first web app setup on the box (an X86 version of the OS). I have created multiple sites for this app to be installed on, and none of them function any differently.

When you install and get the error, leave the error message displayed so it does not rollback.

Then open the default.htm page IE (e.g. http://servername/QdabraWebService/default.htm)

Does this page display?  You should be prompted for credentials, but it should display in IE. 

I've tried that. No matter what credentails I use I will not let me in.

If you remove anonymous access from the root of the website and use integrated windows authentication, does the root page display?  Since this is a new IIS website, it should show the 'Under Construction' page.

I was able to get a hybrid version of the Active Directory web service up and running. I think a big help was making sure that the app pool ran as Network service rather than a domain account added to the IIS_WPG group.

I will wait to make any changes to my installation until the next release of the app. Please toss any ideas my way, though, as we might hit the nail on the head...

Thanks guys!