• Delete ALL of the contents (files AND child folders) of the root install folder - often httpdocs or wwwroot or public_html or maybe a child folder such as dotnetnuke depending on the hosting provider.
• Delete the entire MS SQL Server database - it is NOT sufficient to delete just the tables within the database. Then create a new, empty database.

You may need the help of your hosting provider for one or both of those operations if you do not have sufficient permissions.

Before reattempting a DotNetNuke install be certain that the asp.net worker process account (IIS Identity account) has been granted full permissions (including modify) on the root install folder and that those permissions have propagated to all  child folders. Many hosting providers do not allow their customers to set permissions on the root install folder so you may need their support help to do so.

Good luck and don't give up - although installing DotNetNuke the first time can sometimes be a challenge you will find it worth the effort once you are up and running. It also helps to have a hosting provider which understands DotNetNuke and even better if they provide an automatic install of the latest stable version.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner

William,

I am up and running and so far so good. Thank you for your input and encouragement. I am set up better than I was because I did a custom install and set it up the way I wanted it.

God Bless,

Mark