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 ...Waht a joke, is it just meWaht a joke, is it just me
Previous
 
Next
New Post
6/20/2006 9:41 AM
 

Can I also tell you a little secret...   - some of us do have troubles installing dnn - I can't tell you how many frustrating hours I've had trying to work out what I did that was different to the last time and the last build - which stopped me from installing dnn.

A couple of examples - I use the Inventua Href Exchanger - and, beforehand I could actually add the code to the web.config file - before I installed.   Well, 4.3 doesn't do that... and do you know how many hours I spent working on it?

Another instance, I changed my sql setting - well, that just took me about 2 days to figure out - I swear if someone had been near me it would not have been good talking to me.

I've had to grow from my Windows 2000 server to my new Win2K server - and I am not going to tell you how long it took me to get DNN4 running - I didn't know that it needed to be in it's own pool - eg.. apsnet 1.1 and asnet 2.0 need separate pools - (well if they don't, they do on my computer) 

I didn't know that the permissions were slightly different.

I can also tell you, without saying who - that a core team member spent hours and hours trying to get DNN working with sql express.. Much of this is unchartered grounds and we are now working on providing some solid, easy to follow instructions that will help you identify where you might be going wrong.

Sometimes I think in the generousity of making DotNetNuke such a diverse application has been like a double edged sword.It is very clear that the amount of different installations people have from their laptop, work machines, intranet, extranet, dev evironment, win2k, win2k3, xp, xp pro, xp home, sql express, sql 2000, sql 2005, vs 2005 , vs 2003, remote access, non remote access, hosted, dedicated, mixed mode sql installations, local, ip based sql connections, full trust, medium trust, trusted connection = true, developer, newbie, experienced enough to be dangerous can make for testing times trying to install.  .... the list goes on and on and on. And we haven't even mentioned languages and people's method of interpretation.

The easiest installations I think I've experienced were DotNetNuke 2.1.2 (which was the fastest build I thought- but had issues with huge xml files) and 3.1.1 was great to install, and has been a really fast build, but you know the nature of us - we want the latest and greatest features and with that comes the learning experience that can wear even the toughest person down I'm sure.

I can only say that in spite of all the challenges, MOST people get them worked out and are really happy with the end result.  We all have our struggles. *sigh* I seem to find lots of them but no matter how much DotNetNuke frustrated me at times, I can't tell you loud enough - how great this product is.. and I'm always looking at different products you know - and in 3 years, still never been convinced by anything else to make the change, in spite of the challenges that I experience from time to time.

So please don't get too disheartened... we do have some new information on installation coming out in the near future and hopefully problems people are encounting will be reduced substantially.

Nina Meiers

 


Nina Meiers My Little Website
If it's on DNN, I fix, build, deploy, support,skin, host, design, consult, implement, integrate and done since 2003.
Who am I? Just a city chic, having a crack at organic berry farming.. and creating awesome websites.
 
New Post
6/20/2006 12:33 PM
 
sticcino wrote

i think i've just snapped with this product.... /*EDIT: version 4.3 */

i thought i knew what i was doing, but i guess not. Am i the only idiot out here or what, I can't believe so many people are having these issues on the installation with DNN.

I think the core team should sit down and re-evaluate the installation process anddig into the root cause of these of these issues on so many different systems, and also enhance the error system: "an error occurred" - when i received that, i knew exactly where to go to rectify the problem.

An the core team is going "well, it works on my system" - i'm a developer also, and that's what i tell my clients when my software doesn't work on there systems.

so since i couldn't upgrade successfully for the past day, lets try a "fresh" install from the dotnukte\website files.

so, i copy the website into my dev directory, compile no problem, copy it over to my working IIS directory, fire it up, wow... it does ist database installation no problem.

then i click to start the portal, starts crunching for a while, lone and behold it comes up, i log on, go to edit a module and......... no text on the menu entries for the modules.... (yes yes yes, it probably can't find the resource files.. wher are they suppose to go -- because if you look at the core code - it looks in the app_globalresources, but you can't copy that folder over to your virtual directory)

i even tried without a compiled site, and same problems.

has anyone ever installed this thing without an error.. is it possible??, christ. 

i've just wasted 2 days with this, i cannot believe something is this unstable, every installation/upgrade attempt i did, i literally received a different error message.

yes i read the installation notes, videos:

- .NET Framework 1.1 must be installed ( 1.0 no longer supported ) - should'nt that read .NET 2.0


also, i won't get into the wizard not working. 

Your frustration oozes, through your post. However you ahve missed a very important thing: What steps did you follow? You see, most replies you will receive will either assume you followed every step included in the installation documentation (the one from previous versions since the updated documents are not available, yet the install works in the same way)- so it must be your environment setup... OR  they will assume that you haven't done something right. So the best way to get help is to go into some detail about:

  1. What's your environment and
  2. What steps did you take to install DNN.

I know you will roll your eyes, but I have to say it. I make sure I follow the installations instructions everytime with a couple of handy handwritten checklists one for the install/upgrade process. Of course I backup my live sites before I do anything.


Do you know the truth when you hear it?
Néstor Sánchez
The Dúnadan Raptor -->Follow Me on Twitter Now!
 
New Post
6/20/2006 12:44 PM
 

I'm thinking that all the messages are a good signal of growth and addiction.  Even if it said "beta" we'd still download it, and others would still try to use it in production. 

It's the latest and greatest affliction - me included.  But I'm glad they released this, since I know what's to come and I can decide to roll with 4.0.3 or another version or wait for 4.3.1 for my sites coming online.  Before this was either hours spend scouring GEMINI - which has a ton of good info, or just skimming the blogs for details.

 
New Post
6/20/2006 12:55 PM
 

Perhaps the real issue with DNN, both on upgrades and new installs, is that the community is both extremely diverse and ill-defined.  DNN is, and always has been, a framework for developing a portal.  It's not a fully functioning content management system.  It's not for beginners, either beginners at web development or beginners at programming.  It takes work to complete the framework, and it takes work to get the framework to work

Is that the way it should be?  Heck if I know.  I now rarely use DNN for production use because it takes too long for me to get what I need working out of it.  The development path looks good, but it's not where I need it to be yet.  And it's not suitable for what appear to be the vast majority of people who post in the forums.

If you take a look at the other options out there, such as Community Server, they've taken an approach that is away from the developer framework concept and toward a content management system that's extensible.  Is that a better path?  Again, heck if I know.  It really depends on the user and their needs.

If you find DNN hard to install and configure, try something else.  All DNN cost you was some time, so it's not an expenditure you now have to make work.  No portal/framework/CMS/etc. is a one-size-fits-all solution.  Find the one in your size and move on.

Jeff

 
New Post
6/20/2006 5:02 PM
 

AMEN, AMEN, AMEN!  I have not been a user of open source products in the past and have been highly skeptical of them.  BUT, I had been reading lots of good stuff about DNN and it appeared to be the perfect solution for a client of mine.

Unfortunately, after several days of not being able to so much as install this thing I am starting to think I should have stuck with my initial reaction.  At least when a business releases a product there is somewhere to go for support, not just scouring forums for some mumbo jumbo, and "this worked for me" whims.

"new information on installation coming out in the near future" is also not what I need to hear when I have a client who wants results.  I am not feeling great about DNN right now and will be evaluating alternatives.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Waht a joke, is it just meWaht a joke, is it just me


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