Befor you do update a running DNN, you ave to backup the files, database, and the web.config.  Normaly in all DNN Zip files are a new web.config. There are a maschinekey, that have to change with the maschinekey from the old web.config.  Also you have insert in the new web.config the 2 connectionStrings for the Database, and make sure you have set the right databaseOwner i the web.config.

If you are using the old web.config file, the Updates not running completly, and your DNN Webpage can crash.

If you are looking in the manuals, there are this prcedure is be writen.   Is the web.config file missing i the new DNN zip folder you make it from the release.config.  Anytime on Update you have to make a new web.config file !!!!

If you forgot to use the existing mashinekeys from old web.config to new web.config, you will never more have access to the DNN.  The maschinekeys are the engription code for all passwords of the Database.

Regards

Matthias 

Hi Matthias, you wrote:

"Normaly in all DNN Zip files are a new web.config."

Yes there are two (development.config and release.config), but they are wisely not named web.config, so it is actually never overwritten. I've now heard from my host that some users just like me experience errors while upgrading, but according to them that is mostly due to timeouts in the processes of running scripts, installing new modules, etc.

So to rule out host/network problems, yesterday I've done some extensive testing LOCALLY and it shows that upgrading from a fresh DNN 455 works fine, while my actual doesn't work, so there must be something in there that DNN 460 doesn't like.

My next move is to gradually 'strip' my actual DNN 455 by removing modules and features one by one until the upgrade works. This won't be easy but to find out what it is is important for my client as they cannot upgrade if I just install the DNN 455 website and do nothing about it.

Another strategy could be to start with a fresh DNN 455, install what I need, clean the DB and then tie the web app to it, and then try to upgrade to DNN 460.

Anyways, I cannot blame the DNN core team, it must have been some external module or language package or maybe even VS.NET's 'code mangling' (I installed LinkImage for DNN 3 - used extensively, and OpenSearch for DNN 3/4 - not used yet but the idea is to use its role based search capability).

I hope for the best and maybe just cleaning the DNN 455 ans its related DB might do the trick...

I'll be back with more results shortly.

I Have the same problem upgrading from 4.5.5 to 4.6.0:

Server Error in '/' Application.

---

Index was outside the bounds of the array.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.IndexOutOfRangeException: Index was outside the bounds of the array.

Source Error:

Line 171:                        Response.Write("<h2>Upgrade Status Report</h2>")
Line 172:                        Response.Flush()
Line 173:                        Services.Upgrade.Upgrade.UpgradeDNN(strProviderPath, strDatabaseVersion.Replace(".", ""))
Line 174:
Line 175:                        'Install Resources

I've double checked all the settings in the web.config.. Is this a bug? and if so is it already added in gemini ? I also manualy ran the 04.06.00.SqlDataProvider... And added 4.6.0 to the version table...And everythings SEEMS to work ok... altough I don't think this is the way to go :)

It is going wrong on this line in the install.aspx:

Services.Upgrade.Upgrade.UpgradeDNN(strProviderPath, strDatabaseVersion.Replace(

".", ""))