Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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 ...Why is DOTNETNUKE so hard to install?Why is DOTNETNUKE so hard to install?
Previous
 
Next
New Post
1/5/2006 4:19 PM
 
Jerry McHugh

www.queacct.com
Joined: 4/22/2005
Posts: 9

Sorry guys

The install routine is cumbersome, a black box and is the most prohibitive obstacle for DotNetNuke

I have been working on an install to a hosting site for over 30 hours. I understnad the rights issues, etc. but it seems I'm always left in limbo somewhere

Isn't there a simple install?

In the guise of asp.net, why can't I use a sample database to upload, upload the ASP modules and run?. Perhaps a simple install flag? 

I don't need to upgrade, etc..

BTW I found a number of things which may be of value to other issues and want to issue a paper on my efforst when I can successfully install

Thanks

 
 
New Post
1/5/2006 10:13 PM
 
Timothy Durkin

Joined: 1/4/2006
Posts: 11
I reckon that I could probably help you get it working. I need to know exactly what errors you get and what you did to get them in order to figure out what's going wrong. Take a look at my post "Installation Error. Can't get it to work. Help?" and look at my most recent replies. If you still can't understand what's going on, I'll help you out.
 
New Post
1/28/2006 11:09 AM
 
werwer werwerwe

Joined: 12/16/2003
Posts: 1

Spot on.. the sentence that the install is very cumbersome... I ecpierence exactly the same problems as a lot of people scattered over this forum, I concluded from reading many postings here.

What all my fellow "crap I can't get this to work within 24 hours of straight troubleshooting" have done is this, and they fail misetably.

Like the others, I went for the install package, on windows 2003 server, ASP2.0 and I did all the stuff in the documents, yet.. firing install.aspx or even browsing to the default.aspx gives an error. I'm not even going to bother to state what errors, as they are the same as the other postings. It's like nothing was found, nothing get's executed.

I run a bunch of forums internally, and some externally. This one just kills me.

Even people commenting on this forum : A lotta (dumb) people create a directory dotnetnuke and point their installs to it...They then vaguely advise to do it under the root, while all the documents say you have to create avirtual diretory.

So, this posting is not to get help, but to invite other people who suffer exactly from this :

Found DotNetnuke, meet the requirements ASP.net20, sqlserver 2005, IIS60, NTFS permissions, webconfig file carefully edited, etc., etc.

ready to browse for the first time... anxious.. nothing happens...just page 404. nothing found. even /install/install.aspx does "nothing"

to register on this forum and join this thread to show we're not the only ones. As I am finishing typing this ,my collegues have given up too. We don't quit easily!

 
 
New Post
1/28/2006 11:50 PM
 
Paul Davis

Paul Davis's Avatar

www.phdavis.com
Joined: 4/26/2004
Posts: 616

I can understand your frustration and some of the problem is with DNN but not all of it.

Reading through all of the issues and problems from here and on the ASP.net site it really boiles down to never having installed a web application before and knowing very little about databases and how they work with IIS.

The root cause of 90% of the problems people are posting here are because thet expect it to work just like installing a desktop application and have never worked with a real asp application that is installed remotely.  They don't know about IIS permissions or windows security other than what they might have read from the DNN install documentation when they finally bothered to read it.  Have never had to connect to a database with an application before installing DNN. Or never had to work with an application that uses the web.config file and don't understand anything about what it is or does. 

I think you have to have at least a basic understanding of these things or you are going to have a problem installing any web application.  With the release of DNN 4.x.x it seems to have gotten worse because there are now people trying to install from the source code who have never even seen Visual Studio let alone compiled code in it. 

When I install DNN it takes about ten minutes.  8 minutes of that is FTPing the files to the server.  The documentation referes to installing in C:\DotNetNuke and then creating a virtual directory in IIS.  This is for the first few times while you are getting to know DNN.  Once you know how DNN is structured you can put it anywhere you want too. 

If it's taking you 30 hours to install DNN and you get frustrated and give up, that is saying much more about your general IIS knowledge thanit is about DNN's install procedures.

Should there be an easy to use / install version of DNN that requires absoultly zero knowledge of IIS and SQL server?  Sure!  That would be a great thing for DNN as a whole I think.  It's an open source project and there is currently a core sub-project for the DNN installer that seems to be looking for team members.

Paul Davis
 
New Post
10/13/2007 7:18 AM
 
DogstarPhotography

Joined: 10/11/2007
Posts: 4

Adeian wrote

They don't know about IIS permissions or windows security other than what they might have read from the DNN install documentation when they finally bothered to read it. 

I'm sorry but this just annoys me, it's all very well syaing that, but perhaps if the 'install documentation' were actually listed somewhere it might help, even saying that there is install documentation on the download page or as a sticky on the Install It forum would help. Thos of us installing for the first time need extra help even if we are somewhat familiar with IIS.

An attitude of 'RTFM noob!' doesn't help anybody.
 
 Page 1 of 2
12Next 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Why is DOTNETNUKE so hard to install?Why is DOTNETNUKE so hard to install?


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