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 ...Trouble with web.config (which passwords do I need)Trouble with web.config (which passwords do I need)
Previous
 
Next
New Post
4/27/2006 2:12 PM
 
flanakin wrote
Removing the SQL Server 2005 Express connection string is the same as "editing the conn string." The upgrade error you're referring to typically happens when the server can't talk to the database. This has been my experience, anyway. I got it on a recent install for a client in a hosting environment and it turned out to be an invalid username/password.


Is it better to use SQL authentication or local?  I setup two identical servers and took the same steps on both, and one installed and the other didn't.   Funny, it feels like walking on glass when setting up the newest DNN4, because you have to be so very careful when setting it up or you will be in for alot of hurt getting it to work. 
 
New Post
4/27/2006 2:32 PM
 
I'd suggest using SQL Server authn. But, that's how I've always done it, so of course I say that

The only problems I've had with DNN4 have been related to compiling and deploying .NET 2.0 or not doing a step correctly (i.e. wrong DB user/pwd). Besides that, I haven't had any issues. I'm not going to blame DNN for issues with .NET or when I do something wrong.

Michael Flanakin | Microsoft Consulting Services
www.michaelflanakin.com
 
New Post
4/27/2006 2:42 PM
 
flanakin wrote
I'd suggest using SQL Server authn. But, that's how I've always done it, so of course I say that

The only problems I've had with DNN4 have been related to compiling and deploying .NET 2.0 or not doing a step correctly (i.e. wrong DB user/pwd). Besides that, I haven't had any issues. I'm not going to blame DNN for issues with .NET or when I do something wrong.

Thanks for the advice on SQL authentication, this has been the way I have been doing it.  I am not really blaming DNN, I think its by far the best web portal out, and really even though the new 4.x version is more picky then the 3.x versions when setting up, it's still alot easier than setting up PHP Nuke or one of those PHP type portals.  Well, I got one server working, I just have to figure out what I did wrong on the second, I am about to wipe out all changes that I made on that install and start over from scratch.

Oh, any idea when DNN 4.1 will be out?
 
New Post
4/27/2006 4:28 PM
 
I promise you that setting DNN up will become successively easier. That's the one thing that's nice. You eventually realize that a lot of the issues are because of steps you might have missed or minor things you did wrong. This only comes with experience, tho, and it's hard for those new to DNN to understand it. Like I've always said, everyone has problems setting it up the first time. After doing it a few times, tho, you run into less and less problems.

I guess I'll be putting my money where my mouth is in a few hours. I need to setup an install for a client. It sounds easy enough, but we all know how issues creep up out of nowhere

Michael Flanakin | Microsoft Consulting Services
www.michaelflanakin.com
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Trouble with web.config (which passwords do I need)Trouble with web.config (which passwords do I need)


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