Hi, I wanted to upgrade my DotNetNuke version of 4.9.2 to 5.2.0. It was going well and the update was completed, but when i went back to my frontpage, there was an error which said "Search Enchanted". I hope that you can help me with making this error go away, because i have to update my DNN quite quick. Thanks in advance. (Sorry if my English is that great, I'm not from an English speaking country)

Could you perhaps attach a screen shot? Also, if you can look inside of your database at the EventLog table, you may see some additional information.

Hi, sorry for late react, but here is a link of the screenshot of the error that I get.

http://img138.imageshack.us/img138/6061/fout.jpg

From the DotNetNuke site: System requirements have changed in DotNetNuke 5.2.0. DotNetNuke requires SQL Server 2005 or above and .NET 3.5 SP1. Please upgrade SQL Server and .NET before installing or upgrading to DotNetNuke 5.2.0.


If you look carefully at the bottom of the image, you will see that your site is using ASP.NET 2.0x.  You will need to upgrade ASP.NET.

Allright, thanks.
I think this can be very usefull.
I will go after it immediatly.
I will keep you informed.

Thanks in advance

Hello, here I am again,

Just spoke to my project leader and he said, that we have ASP.NET version 3.5 (Not SP1) but our runtime still runs on version 2.
i don't know if that is the real program, but we did this before, but we lost our file where we wrote all our steps on.
When we updated it before, we didn't have to update ASP.NET.
The real problem is, that we don't know what we did back than, because it was right before the Christmas holidays.
Do you know what might be an other sollution?

Thanks in advance

I think that you will need to:

• Get ASP.NET 3.5 with SP1 installed on your web server
• Adjust IIS settings for your website to use it

Then I would see if that solves the problem.

The problem isn't the IIS or the framework installed on the server. It is probably correct BUT the problem is when DNN upgrades from DNN4 to DNN5 then your best procedure is to manually replace the web.config with the new DNN5 release.config. Extract the DB connections values and machine validating values from you old web.config then save release.config as web.config and you problem is most likely gone away.