Okay, I've removed all folders & files from App_Code\XML & navigated to the home page, & now I get this error page:

Server Error in '/' Application.

---

Parser Error

Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately. 

Parser Error Message: Could not load type 'DotNetNuke.Common.Global'.

Source Error: 

Line 1: <%@ Application Inherits="DotNetNuke.Common.Global" Language="VB" %>

Source File: /global.asax    Line: 1 

---

Version Information: Microsoft .NET Framework Version:2.0.50727.3607; ASP.NET Version:2.0.50727.3082


Do I need to do something else too?

I thought I had installed all modules, but I have no App_Code\Chat folder, so maybe not.

Thanks for your assistance.

Yes, .Net 3.5 SP1.

The error occurs about as early as one can in the start up of the DNN application so it's cause has got to be very simple and fundamental. Please check the following:

1. When you removed the code for the XML module, did you only remove those files in the App_Code\XML directory? There should still be an App_Code folder in the website root containing the following two files: AssemblyInfo.vb and Global.asax.vb.

2. From what DNN version did you upgrade? I'm a bit concerned about you step 3: "I renamed web.config to something else, renamed release.config to web.config, & copied the two SQL connection related settings & the machinekey setting from the old web.config into the new one, replacing the default settings in that file". Note that when upgrading from versions 4.6.2 and later, you should not manually modify the old web.config file or transfer settings from the old web.config to the new web.config. Simply leave the existing web.config file in place, unchanged, and the DNN installer will make any necessary changes to it as part of the upgrade. The upgrade package does not contain a web.config file of it's own so that the existing web.config will not be accidently overwritten when uploading the new package. As it appears that the upgrade process was never trigged, you may be able to restore your original web.config to the site root and try the upgrade again.

3. If you had upgraded from a DNN version earlier than 4.9.5, the recommended upgrade path is to upgrade first to 4.9.5 then to either 5.4.1 directly or with an intemediate step to 5.2.3 then to 5.4.1. You may also want to wait for DNN version 5.4.2 which fixes several install issues in 5.4.1. It should be released in the next week or two at the most.

4. Prior to unzipping the 5.4.1 upgrade package - had you first (if using Windows native zip extraction) right clicked on the zip package, selected "Properties" from the context menu, then clicked on the "Unblock" button. A Windows security update a while back (last summer?)  blocks certain files (including some vb files) from being extracted from remotely downloaded zip archives. If that was not done, some of the files of the upgrade package might not have overwritten the existing files.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner