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

HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...From SQL 2000 to SQL 2008 and 4.8.4 to 6.1From SQL 2000 to SQL 2008 and 4.8.4 to 6.1
Previous
 
Next
New Post
4/20/2012 5:48 AM
 
Jeff Sutton wrote:
Steven. I am in the same situation as you. May I ask how your upgrade went and if there were any issues?
Did you upgrade sql to 2008 while still at dnn 4.84?

 Jeff,

The upgrade from SQL Server 2000 to 2008 wasn't such a big deal. However, based on what I see in SQL Server Management Studio, when I imported my backed-up DNN database into SQL Server 2008, SSMS "sees" it as a 2000-level database. I don't know if that's going to present any issues coming up.

I attempted to upgrade 4.8.4 to the first upgrade level in the recommended upgrade path; that is, to 4.9.5 as recommended in the Suggested Upgrade Path wiki. As I said in my original post, I backed up SQL Server 2000 twice and copied my entire site to my own system. I use a hosted site, so setting up a test bed wasn't really possible. It was all or nothing. I suppose that could try to do it on my own workstation's copy of SQL Server 2008 and .NET 4.0 and IIS...but that would hardly be a complete test.

Anyway, I made another post about what happened to me after that first upgrade step: App_Browsers\OceanAppleWebKit.browser 

I followed that thread up with this one: Back to square one 

After that I wrote: Reversion back to 4.8.4 creates a small problem 

I have done nothing since then. In the "Reversion" thread I confused the issue a bit by saying that I'd first upgraded to 4.9.2 when in fact I'd upgraded to 4.9.5. That posed (for me) insurmountable problems so I reverted to 4.8.4. This was all done with a SQL Server 2008 DNN database since that upgrade had been performed by my web host. They also upgraded the site from ASP.NET 2.0 to 4.0 so I'm current as far as that goes.

But I've actually regressed a bit. My main use of DNN is for the Blog module. I had instituted the use of CAPTCHA for comments...but since reverting to 4.8.4, the captcha image no longer shows.  There's an "x" as if the image can't be found, and no one has been able to leave a comment on my blog since.

I suppose that I should have been keeping up with DNN upgrades as they came out so that I could deal more incrementally with the changes. But jumping from ASP.NET 2.0 to 4.0, SQL Server 2000 to 2008, AND DNN 4.8.4 to whatever...it's too much. I'm not enough of a web boffin (as The Reg puts it!) to handle things on my own....and while these forums are useful, sometimes the answers I get have no effect on what I want to do.

For instance, in the "Reversion" thread, Mr. Leupold said "If you upgrade your database, you need to use associated core files as well." OK, but what does "associated core files" mean? He went on to say, "I suggest upgrading to 4.9.5, which should not result in issues." But it sure did! That's why I wrote the additional threads ("Square One" and "Reversion").

I like the forums; but if one really has a sizable problem, getting bite-sized answers from even the top DNN gurus doesn't amount to much.

In the past I had problems with SQL Server 2000. I took a goodly amount of time to resolve the issue "by hand". I don't remember the exact steps, but it involved copying every DNN table into the same database using a different prefix (from "dnn_" to "nuke_" and, I believe, re-installing DNN from scratch and saying that I wanted the prefix to be "nuke". I'm sure I'm mixing up the timeline a bit, but I'm no stranger to SQL Server and I got DNN to work just dandy after a goodly amount of "hand work".

The upshot is, DNN 4.8.4 works except that my blog is less functional since the CAPTCHA images don't show up.

I don't know if this helps you. Perhaps you're more diligent/persistent/stubborn than I am and will successfully upgrade your DNN. I suppose that there's a way for mine to be successful, too, but I'll wager that it'll take devotion, study, additional boffinry, and lots and lots of time.

My sites aren't business sites and I don't really care if people visit them or not. The most popular things on my web site are the old WHAMCO radio ads I ripped from the original LPs. The originators of those wonderful spoof ads are both dead; but I imagine that they'd be pleased to know that new people discover them on my site on a regular basis: www.swerbach.com/whamco.

I'll take up the cudgels and try the upgrade again at a different date. I'll probably scan the forum more closely for upgrade tips. But I have no illusions about how easy it's going to be. I know that it can be a cast-iron SOB.

Thanks for reading this wandering screed. I like DNN; but, like a lot of web stuff, it takes lots of time to be a master.

Steve Erbach
Neenah, WI




 
New Post
4/20/2012 6:01 AM
 
cathal connolly wrote:
Steven/Jeff- you dont need to do each and every upgrade step - I often check the prerequisites and if needed apply them (i.e. migrate to the correct sql and .net versions) and then test a jump to a much later version and see if that works - some of the suggested upgrade paths were put in place to catch issues with 3rd party modules/configurations that were later fixed so they're not always necessary (i.e. I've upgraded from 3.3.0-4.9.5 in a single jump and 4.9.3-6.1.0 in a single jump with no issues in the past)

 Mr. Connolly,

I wish that it were that simple! I wrote a fairly detailed chronology in my reply to Jeff. As I said, I will eventually take up the fight again to do the upgrade to the latest DNN...but I have no doubt that it will be a long hard slog.

In future I will try to post small questions and I will try to keep at it and follow through with forum replies and such.

It does seem to me, though, that the sub-set of DNN sites, like mine, that are installed on commercial shared web hosts present additional problems in that the user (me) doesn't have total control over either the SQL Server or IIS or the web server. I don't have the wherewithal to have a dedicated host, nor do I need it. I'm not conducting a business.

Anyway, I want to upgrade to DNN 6. I'm not going to jump ship. I make my living writing .NET applications so DNN appeals to me for that reason alone.

Steve Erbach
Neenah, WI

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...From SQL 2000 to SQL 2008 and 4.8.4 to 6.1From SQL 2000 to SQL 2008 and 4.8.4 to 6.1


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