On the install wizard, it gives the warning:
The Auto option has been disabled as the DotNetNuke Application cannot connect to a valid SQL Server database. You can continue to use either of the other two Wizard options and configure the Database settings at the appropriate Wizard step.

On the SQL step, it gives the following, without any message following the "Message:"

Connection Error(s):
Index #: 0
Source: .Net SqlClient Data Provider
Class: 14
Number: 229
Message:

The app is configured to use windows auth. It runs in it's own separate app pool with it's own service account and security group.

I have created a .UDL file on that server and it connects successfully. I have compare the connection string that it created to the connection in web.config, and it looks fine.

What could it be? How can I test this?

Full version of SQL Server.

Is there anyone on the forums familar with this error message & numbers on an install using windows auth?
Connection Error(s):
Index #: 0
Source: .Net SqlClient Data Provider
Class: 14
Number: 229
Message:

_____________________

Chris,
Prior to starting the installation wizard, I updated my web.config's connection strings, so in the wizard all the fields are correctly pre-filled:

• SQL Server 2005/2008 Database
• Correct Server Name
• Correct Database Name
• Integrated Security is checked, as it should be.
• Run as db Owner is checked. (Just in case, I have also tried unchecking it and no change in the Connection Error message)
• Not using an Object Qualifier.

I suspect that it has more to do with the windows auth. In our environment, we rarely use it, but we are using it for DNN.

So, here is an overview of the windows auth set up, hope this helps if you can spot a missing step:

• App uses Windows Auth (Integrated Security = True) for database connection.
• App will use 1 service account for install and upgrades only, due to enhanced permissions needed.
• App will use a second service account for primary use by staff and general public.
• Have created the new app pools for each account (so that switching permissions & recycling app pool does not affect users of other apps).
• Created new service accounts, assigned them to respective security groups and app pools.
• App is using the new app pool.
• On the Security Tab, gave the service account Full Control.
• Confirmed that it is propagated down to all the folders and files.
• The security group has been added to the iis_wpg group, Reset IIS.

Thanks.