Hi,

this is normally a problem with the database connection. Please check permissions for the AppPool user (in Windows 2k3/IIS 6 this is normally NETWORK SERVICE). Also check if the connection strings in the database are valid (and both strings are the same).

Best wishes
Michael

---

Starr,

there are two connection strings in the web.config file:

1) configuation :: connectionStrings, name = SiteSqlServer
2) configuration :: appSettings, key = SiteSqlServer

(actually there are two of these in each of the sections, but one of them is commented out depending on the SQL Server you use)

The first one is the one DNN uses, the second one is to support older ("legacy") modules. Both must connect to the same database on the SQL Server.

If you have something like "Integrated Security=True" in your connection string, make sure that the user "NT AUTHORITY\NETWORK SERVICE" has enough permissions on the database (for installing it should be dbowner, but you can use more granulated permissions later afaik, not sure which ones exactly at the moment). If there is something like "Persist Security Info=True;User ID=DNN_User;Password=xyzMy1stPWD" in the connection string, make sure that this user (in this case: DNN_User) has enough permissions.

Best wishes
Michael

---