First Download the DotNetNuke software. If you’re not doing any development aside from skins and such, grab the Install Package. This doesn’t mean you won’t be able to install modules. The other ones are more for developing.
IIS 7 Settings For DotNetNuke
Install IIS 7 if you haven’t enabled it. You can do this through Vista’s Control Panel under programs and features. On the left hand side your see something that says Turn Windows Features On Or Off. In the next dialog box, make sure you have these items checked. They aren’t all necessary but, you should have IIS Management Console, and ASP.NET which will enable a couple of other checkboxes. Also, a couple of items under Commone Http Features.
Create Database in Microsoft SQL Server 2008
right-click databases and select NEW DATABASE
Under General, Type in a the name of the database as whatever you want (typically DotNetNuke) but, remember what it is because, you’ll need it later.
Click on the button to the right of the Owner to browse for an owner. The options available will depend on whether or not you used the Native Windows Authentication mode or SQL Server and Windows Authentication mode. Basically, with Windows Authentication mode you’ll be using the credentials of the Windows Server Box you are using as opposed to using a separate list of SQL Server users kept within the SQL Server database.
Under the main category of OPTIONS on the left, I chose the compatibility level to coincide with SQL Server 2005. I’m not sure effect it would have if any to choose compatibility with SQL Server 2008 but, DotNetNuke 5 should be coming out reasonably soon so, that should support it. Anyway, like I said, this is just the quick and dirty version.
I left the rest of the options as default. These instructions are more for a local development stand-point but, so I can’t guarantee security. Talk with your host to ensure that there aren’t any giant holes saying “HACK ME PLEASE 
”
Now the most important road block I think most people will run into including myself is all about permissions to files and directories including being inaccessible or non-writable and/or bad credentials to your SQL Database usually having to do with mispellings or targeting the wrong user with the wrong permissions.
SQL Server 2008
If you’re having problems connecting to the SQL Database DOUBLE and TRIPLE check these settings if you’re having problems and make sure you’re calling the right DATABASE NAME. If the SQL Server is on the same machine as the web server then the SQL Server name should be LOCALHOST. Also, you might see “Login failed for user ‘NT AUTHORITY\NETWORK SERVICE’. Make sure to right click on your database and goto properties > permissions > View server permissions. Look for ‘NT AUTHORITY\NETWORK SERVICE’ in the Logins or roles area. If you’re having problems and are troubleshooting permissions. Grant all of them to ‘NT AUTHORITY\NETWORK SERVICE’ but, remember to go back and change them when you figure out the culprit.
Now a little detail for the issues with permissions to files and folder. I recieved a number of errors such as “Access to the path Compression.config’ is denied” or some other file wasn’t writable. I’ve seen some on the net on other forums saying to move these files from the config directory to the root. Sure, you might get some random concoction to work like I tried to do on math tests in school but, the reality is, it should work if you’ve setup permissions properly. You should be able to install IIS 7, create an SQL Database, throw the files in your web root, set permissions on the database and navigate to the fully qualified domain name such as http://localhost/ or http://www.whateveryourdomainnameis.com/ to start the installer. You may get an error dealing with the NETWORK SERVICE on the actual permissions of the root folder which is different than the credentials of the database.
Also, under default application pool, your .NET Framework should be at least in the 2.0 or above. And your Default Website should be using that default application pool by default or you’ll have to right click on it to add the pool.
Under Default Document in the IIS Manager. Make sure you move the Default.aspx to the top to speed up performance, otherwise it will check for all of those other files first.
Ok everyone, like I said quick and dirty. Well as quick as quick can be when dealing with computers but, I hope this helps. I couldn’t find any good articles for my problems so, I wrote this. I can’t stress enough, permissions are savior to this whole installation. Also, just to make sure these aren’t causing the problem, try re-starting your computer and/or restarting the IIS server and SQL Server. I know in MySQL you have to reload privileges and whether it’s documented or not with Microsoft’s SQL Servers, it’s always good to try. I’m sure we’ve all had to “power cycle” something over the phone on tech support. =8o] It does work sometimes.
Hopefully I saved you 30-50$ on a book. If you have any questions, feel free to comment or shoot us a message. You can always call us and talk to a real live person too. That’s a rare these days eh. LOL go figure. I’m sure we could save you more on design and development as well. When you need it, we’ll be there. If you build it, we will come. ;o)
