I tried searching for this in the forums, but apparently the search is broken. I have my dev dnn site on a single server, database and iis on the same server. And now im ready to move it into more of a production environment with the IIS server separate from the SQL server. I'm really close but i think my connection strings just need tweaked a bit. To make this even more challenging i was using SQL authentication to connect to the database and now i need to be using a domain account. Here are what my connection strings currently look like:

     <!-- Connection String for SQL Server 2000/2005 -->
    <add
      name="SiteSqlServer"
      connectionString="Server=servername;Database=dbname;Integrated Security=True;"
      providerName="System.Data.SqlClient" />

...

    <!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules -->
    <add key="SiteSqlServer" value="Server=servername;Database=dbname;Integrated Security=True;"/>

Things work if i go back to SQL authentication in the 2-tier setup, but we have security concerns with using SQL accounts and would like to use a domain account. With this configuration in the connection strings i get this error in the event logs:

Event code: 3005
Event message: An unhandled exception has occurred.

If anyone has any documentation on how to setup a 2-tier environment and use a domain account for the sql authentication that would be extremely helpful. I haven't had much luck looking through my dnn books or through google.

Ahh, that was the missing link. Thanks a bunch. For anyone else that comes across this you will also need to add whatever user you use in the identity for the app pool to the IIS_WPG group otherwise the app pool will crash.