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 ...Upgrade from 5.1.0 --> 5.1.1 failsUpgrade from 5.1.0 --> 5.1.1 fails
Previous
 
Next
New Post
7/29/2009 8:53 PM
 

Alex Shirley wrote
 

 Geoffrey Giordano wrote

 


As for the upgrade issue being in gemini, I don't know.  But the issue was discussed here and the resolution was to fetch the dll from the older package and let the upgrader reupgrade.  http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/107/threadid/315838/scope/posts/Default.aspx

 

Someone may correct me, but I think this is the wrong advice.
You need that dll installed in the servers GAC for DNN 5. This is different to DNN 4.
If you are running .NET 2.x you should have AJAX extensions installed on your server.
If you have .NET framework 3.5 SP1 running then AJAX comes bundled and I don't think you need this.
As future version of DNN 5 will require .NET framework 3.5 SP1 the obvious thing to do is get this up and running on your server. You then need to make sure you point to the correct web extension dll for 3.5 and delete that dll you copied across.

You are correct in that thedll should not be there... my system is running .net 3.5 w/Ajax... it had to do with the way I was doing the upgrade, the release.config file does not assume 3.5, is assumes 2.0 and then it 'auto upgrades' the config for 3.5 if detected.  The file needs to be there simply so that the upgrader can delete it.  by the end of the upgrade process, the file is gone.

BUT, even better, doing the upgrade the way you pointed out, you don't need to put up with this as the web.config gets properly merged.  So, moving forward, the point is moot (at least for me!).

I will open the ticket on support.dotnetnuke.com as you suggest.

Again, thanks a ton for the help.

Jeff

 
New Post
8/12/2009 9:48 AM
 

It doesn't matter if you have 3.5 framework installed on an Windows 2003 server.

I had the misfortune of deciding to install an upgrade on a module on my stie in the weeee hours of the morning and still can't work out which planet I must have been on to consider doing this because it ended up with my site breaking badly.

So i thought , let me go back to that upgrade I'd tried for some time earlier in the day.

Here is the summary of what I found -

3.5 framework may very well be installed on your windows 2003 server, and all the ajax information on the server, but IIS 6 does not recognise this in the property dropdowns if you try to see if the 3.5 framework is in fact installed.

I believe it is mainly a Win2k3 issue with IIS 6, where, if you use the dotnetnuke install zip instead of upgrade you will not get into this problem, or accept that you will have to copy those files across each time you do an upgrade on your win2k3 box.

When I do an new install of dnn it automatically applies the 3.5 framework, but when I do an upgrade, only with the install zip and not the source zip can i go through the procedure, so I don't believe that applying a 3.5 check will resolve this, as I had other new sites running 5.1.1 without issue. 

The site I upgraded from had a 5.01 build and although it failed on one of the sql scripts, managed to upgrade and log in and all seems fine.

What I also think is amazing is my dnn 3 modules (since this is a 3.2.2 upgrade over time) still run. These modules are around 3.5 > 4 years old without being updated, yet lasted through many upgrades. Not bad I think.

But that is my take on this for anyone who is on a windows 2003 server with .net 3.5 framework installed,and unable to see it in the properties tab of their IIS snap in.  Even trying to register the extension didn't work, but somehow it automatically is now running 3.5 framework when i checked the host settings and that error disappeared as soon as I dropped the appropriate dlls into the bin folder.

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.
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Upgrade from 5.1.0 --> 5.1.1 failsUpgrade from 5.1.0 --> 5.1.1 fails


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