I must be doing something consistently wrong. When I upgraded to 4.6.2, I hade to put the old web.config file back to get anything working.

Same thing again with the upgrade to 4.7

I followed the instructions that came with the upgrade package, and copied over all the localization settings.

Then I restarted IIS. No go, a page full of errors instead of the upgrade script. Having already learned my lesson last time, I copied the old web.config file back - and voila - the upgrade script ran fine.

Anyone have any idea why this is consistently happening?

 

There's obviously something else you need to transfer.

• Database settings
• File upload settings
• FCK Editor settings
• httphandlers
• objectQualifier="" settings
• Machine keys
• Some modules add their bits to the file as well

To be safe, I never try to transfer my old bits to the new web.config. It is always a simpler matter to transfer any changes from the new web.config file to the old one.

I use Winmerge or PSPad to look for changes with each DNN upgrade. Both are freely available.

Regards,
Rob

As mentioned you should be merging the elements, I have a guide at http://www.mitchelsellers.com that tells you the sections you should be concerned about.

I also use Vault's diff tool to identify the changes from one version to the next.

---

-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.


Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services