Hi Ken,
I'm not sure my schedule is going to allow a retry as I'm going to have to scratch and re-install the implementation.   I can tell with 100% certainty that there were three errors reported in the UI output, two of them were package file taxonomy & package file messaging - the third error was, I think identical to my previous upgrade attempt - (I recall the "bowl of petunias" moment).

The only log file that contains anything is 05.04.00.log, which contains the following:-

System.Data.SqlClient.SqlException: The ALTER TABLE statement conflicted with the 
FOREIGN KEY constraint "FK_PortalLocalization_Portals". 
The conflict occurred in database "mydatabase", table "dbo.Portals", column 'PortalID'.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, 
BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at DotNetNuke.Data.SqlDataProvider.ExecuteADOScript(String SQL)
   at DotNetNuke.Data.SqlDataProvider.ExecuteScript(String Script, Boolean UseTransactions)



/* Add Foreign Key to PortalLocalization Table */
/***********************************************/

IF NOT EXISTS (SELECT * FROM dbo.sysobjects WHERE id = object_id(N'FK_PortalLocalization_Portals') AND 
OBJECTPROPERTY(id, N'IsForeignKey') = 1)
	BEGIN
		/* add key and cascade delete rule */
		ALTER TABLE dbo.PortalLocalization 
			ADD CONSTRAINT FK_PortalLocalization_Portals 
				FOREIGN KEY ( PortalID ) REFERENCES dbo.Portals ( PortalID ) ON DELETE  CASCADE 
	END	

The only error logged on site was:-

AssemblyVersion: 5.4.2
PortalID: -1
PortalName: 
UserID: -1
UserName: 
ActiveTabID: -1
ActiveTabName: 
RawURL: /Install/Install.aspx?mode=upgrade
AbsoluteURL: /Install/Install.aspx
AbsoluteURLReferrer: 
UserAgent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.55 Safari/533.4
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 240ed1b1-8194-474c-b034-1b028b6360f4
InnerException: Cannot create a file when that file already exists. 
FileName: 
FileLineNumber: 0
FileColumnNumber: 0
Method: System.IO.__Error.WinIOError
StackTrace: 
Message: System.IO.IOException: Cannot create a file when that file already exists. at System.IO.__Error.WinIOError
(Int32 errorCode, String maybeFullPath) at System.IO.__Error.WinIOError() at System.IO.File.Move
(String sourceFileName, String destFileName)
 at DotNetNuke.Services.Upgrade.Upgrade.UpgradeToVersion_530() at 
DotNetNuke.Services.Upgrade.Upgrade.UpgradeApplication(Version version, Boolean writeFeedback)
Source: 
Nombre del Servidor: WEBD14

Which reinforces my feeling that the UI 'log' was identical to the previous upgrade attempt.

All the above looks to be the exact same error as on the last upgrade and again related to the 'localization options' - I read the release notes for 5.4.2, it identified my previous problem and clearly said fixed!

I'm happy to make a complete backup of the site and database available to you if that would help diagnosis.

Is there anyway I can fix this, without the 'scratch all and start again' approach, or Sebastian's, try, try again.  

Perhaps I should hold off for 5.4.3?

What about a basic 'DNN core healthcheck'?

My site seems fine too.  I'm just concerned that I'm never going to be able to upgrade and the longer I leave it, the bigger the headache to rebuild.

It would be nice to have a little advice from the team on this.

I encountered this error when upgrading to 5.4.1. It is related to portals that have non en-US localizations. From 5.4.x, you will find on top of the Admin->Site Settings page a combobox under "Select Language". If your default localization is en-US, you will see the usual settings. But change to another language and you will see that DNN has done a bad job in creating the basic settings for the localization - the basic address referred to the portal 0 and the page name contained the copyright notice if my memory serves me well. When you correct the basic settings, your site will work again.

I met the problem again when I created a new website with 2 languages. I do not remember if that was under 5.4.1 or 5.4.2, but I will do some testing today.

After the update, go immediately to Admin->Site Settings, change to the new language settings, - new in 5.4.x - and correct the mess that you find there. It's a nice new feature once the basic settings are entered correctly.

---

____________________________________
The one-eyed in the land of the blind.