Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Setting up DNN on a VMWare Windows 2003 SP2 Image Setting up DNN on a VMWare Windows 2003 SP2 Image
Previous
 
Next
New Post
9/27/2007 9:23 PM
 

If not first succeed, try try and keep trying until you hit the magic button. All the previous posts give you the order of things. If you do them and you know you got it right, then start thinking out of the box a bit. My install finally worked when I went into the control panel \ add remove and told .Net Framework 2.0 to repair itself.

After it completed, then the system started giving me DNN install messages and before I was only getting browser errors such as not website found etc.

I upgraded my framework to 2 when I added SQL Server 2005. I'm sure this had something to do with it.

Anyways, go back to the fundamentals. Make sure you've completed the basic steps to install then start checking what is not working by testing the diff parts. For example, check to make sure no spelling errors in the login you setup in the database and the one you are sending in the connection script. You might also test that the browser opens any local webpage. Test the browser by creating a dummy page and surf to it under your default web   http://localhost  Either create using simple html markers or quickly grab one from the web to test it.  Named it default.htm etc... Make sure the documents permission has the setting for that document in your IIS web host. You'll need default.aspx for the DNN install but at least you can start eliminating stuff and if you can load the page - that proves the browser part is working.  Keep thinking of those main steps to install and what can go wrong. Also, check that the folder premissions are set throughout all the folders and files under your virtual website. For me in Windows Server 2003 that was using the Network Service. Applying this permission to the root folder as I read did not set those permissions deeper in. I had to manually push it down. Actually, one of my later DNN install errors was that the \config folder needed permissions which is when I push it to all the DNN folders using the advanced button under the security settings.

Anyways, If not at first, keep whacking on it till you get it.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Setting up DNN on a VMWare Windows 2003 SP2 Image Setting up DNN on a VMWare Windows 2003 SP2 Image


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out