this is a bit of a tricky configuration, because the database is configured to use the windows account from the ASP.Net user, which is configured in IIS app pool to be a "virtual" account. if you are on your own server, the easiest option is using "network service" for the app pool and the sql server login.

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN

You have to open the Application Pools and not the Websites advanced configuration.  It is a own point over the SITES section.  Then select the application pool you used for your DNN site and right click, select the advanced settings.

I didn't read yet the post from Sebastian, but think he mean to add a seperate user name and password on your SQL Server security and bind them as a dbOwner to your database, for use as SQL Server Authentication for the both connection strings. 

Edited:

Now I read the post from Sebatian and no, you need to add the network service to your SQL Server with dboOwner permissions. 

Also you have to set the physical permissions for the folders and files in your DNN folder.  I hope you have read the install documentation you can get from this site.  There also a blog for beginners with a lot of resource links that can help you from Joe Brinkman.  I suggest first read, then start.

---

Regards

Matthias

DNN MVP

www.aarsys.de

Metro7 Skin

ShoutCastStats Module for DNN

Application pool user sould be the Network Service.  If not change it.

The database that is used is on a MS-SQL Server, so you must have installed MS-SQL Server (Express can be used) 2005 or 2008.  There are 2 authentication systems availible for the SQL Server - "Windows Authentication only" and "Mixed Windows and SQL Server Authentication".  If you have also installed the SQL Server authentication you can add own users with special SQL Server permissions to your SQL Server.  With SQL-Server Authentication you didn't need the integrated Connection for the application configuration, and you can spezify your connection string on the web.config (for DNN) with a unique User for the database connection.  This is szenarious is often used on Hosting systems i.e Plesk.

You have also to set permissions for your local files and folders on your DNN directory.  There is needed read permission for the IIS Annonymous user and full permissions for the user that is specify on your application pool. 

To learn how to start with DotNetNuke there are a good blog from Joe Brinkman with serveral links to resources to read and listen (video).

---

Regards

Matthias

DNN MVP

www.aarsys.de

Metro7 Skin

ShoutCastStats Module for DNN