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 ...Why is the install so damn hard???Why is the install so damn hard???
Previous
 
Next
New Post
4/24/2006 10:50 PM
 

Honestly.. this is sad... compared to DNN 3.0 , DNN 4.XX is terrible..

I am getting the same bloody

"DotNetNuke Upgrade Error

The Assembly Version ( [ASSEMBLYVERSION] ) does not match the Database Version ( [DATABASEVERSION] )

ERROR: Could not connect to database.

An attempt to attach an auto-named database for file h:\inetpub\wwwroot\dnn\App_Data\Database.mdf failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share. "

I searched for the DDN_template error with no clear answer... Can anyone help... I don't understand why this has to be so insane for the install... ALSO why is the DNN 3.0 and 4.xx manual combined? Just adds confusion!

 

Running winxp, sql express 2005, vs 2005 express...

 
New Post
4/25/2006 3:12 AM
 
    Yup .. manual is confusing being joined like that ...
I am a first time user just trying to get a simple "hello world" install going on an XP machine and it's tough for me.


 
New Post
4/25/2006 10:42 AM
 
90% of the time, these errors are from people not setting up the environment correctly. All we can really say is, "What steps did you follow?" Your best guidance is to follow the install/upgrade docs. If you find problems with any particular steps, let us know. I'm not saying there isn't room for improvement in this area, but we need support in order to provide a better install/upgrade experience. If you're interested, let us know. We're always looking for good ideas and ways to improve what we have, but without bodies to apply those changes, we're kind of in a rut.

As far as combined DNN3/4 docs, we did that for our own benefit. It's hard enough managing two separate code-bases. Imagine writing your application for two different platforms. It's just not an easy thing to manage. Then, on top of that, documenting two separate releases, knowing that one of those will be useless in the future, is just a waste of time. However, if anyone would like to volunteer to donate separate 3.x and 4.x docs, we'll be more than happy to review them for inclusion.

Michael Flanakin | Microsoft Consulting Services
www.michaelflanakin.com
 
New Post
4/25/2006 12:40 PM
 

Well all I can say is that their are 10x as many complaints about the DNN 4.X install as they were with 3.X

I followed your directions to the T, 5 times and keep getting the same error...

I am not the only one getting, this, a lot of people are... In fact  I think you guys need to have a video showing the installation because its getting me no where...

I was able to install DNN 3.0 with no problems, this is a nightmare... If the directions were trully that simple then why are people having so many problems? What is the point of having a combined 3.X and 4.X manual?

I guess time to ditch this and go back to PHP and apache, DNN 4.0 is just too complex and troublsome for its own good.. :(

 
New Post
4/25/2006 4:29 PM
 
You're probably missing a step or have something wrong. The last time I got this error was because I had the wrong connection string. I'd suggest you check that first. Don't just look at it, tho. Ensure the user/password combination works when you manually login to SQL Server and also test the exact connection string from another application. This will ensure it's valid.

As far as creating a video, we look forward to you providing one to us Like I said before, suggestions or appreciated, but actions speak louder than words. We're a volunteer force and people use DNN because of its feature set, so of course this is where we focus our efforts. If someone would like to submit documentation, we'd be happy to validate/post it. Again, I'm not saying that there aren't problems with the documentation or even the application. I'm simply saying that without help in resolving these issues, it's hard to get the docs updated. People expect bug fixes and enhancements, but docs are just a nice to have when you're getting setup. Once you're setup, nobody cares about docs.

Again, the reason for a combined install doc is for our benefit in managing them. Nobody likes to update docs, especially not two sets of docs that are 90% identical, if not more.

If you think Apache/PHP are better than DNN, you're in a league of your own. That's just my opinion, tho. Apache has got to be one of the hardest to configure applications I've ever managed. Luckily, like DNN, once it's setup, you don't have to worry about it.

I've provided a few suggestions, but sometimes it takes a good deal of initiative to track down problems and get them fixed. If you find out exactly where you went wrong, let us know and we can attempt to better the docs for that. Without this explanation, we can't change anything, and the docs stay as they are - with or without falacies. Like I said, more often than not, install/upgrade problems are because of missed or misinterpreted steps. Of course the docs can be better, but we need your input and corrections in order to do this.

Michael Flanakin | Microsoft Consulting Services
www.michaelflanakin.com
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Why is the install so damn hard???Why is the install so damn hard???


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