I need to install an instance of DotNetNuke as it's own website in IIS. Can this be done? I've followed the instructions available, adjusting for an actual website instead of a virtual web. After everything is said and done, I can an error 404 - Page cannot be found error in IE.
I've created a web.config file from the release.config file found in the "source" installation package. I've adjusted it to point to me SQL 2005 server (which resides on a seperate server). I verified the proper user name and password, along with ensuring the proper string is uncommented out.
The database and associated user account is correct.
I also verified file permissions and all applicable IIS settings referenced in the install guides, etc are setup properly. The only difference is that I am installing it as it's own website in IIS instead of as a Virtual Web. What am I missing? Here's a snippet of the web.config settings I am using. (names changed to protect the innocent of course).
-------------------------------------------------------------------------
<connectionStrings>
<!-- Connection String for SQL Server 2005 Express
<add name="SiteSqlServer" connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;" providerName="System.Data.SqlClient" />
-->
<!-- Connection String for SQL Server 2000/2005 -->
<add name="SiteSqlServer" connectionString="Server=dbserver;Database=dotnetnuke;uid=dnnadmin;pwd=testpassword;" providerName="System.Data.SqlClient" />
</connectionStrings>
<appSettings>
<!-- Connection String for SQL Server 2005 Express - kept for backwards compatability - legacy modules
<add key="SiteSqlServer" value="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;" />
-->
<!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules -->
<add key="SiteSqlServer" value="Server=dbserver;Database=dotnetnuke;uid=dnnadmin;pwd=testpassword;"/>