I decided to take the plunge and upgrade to the latest version.  Unfortunately I received exactly the same errors as my failed upgrade to 5.4.1 - I think!!

 I say I think, for some reason or other I failed to correctly copy the screen output of the log file - I defintely saw 1 SQL error (probably 05.03.00) and both the errors on install of Message & Taxonomy.  I've scouted around but see no evidence of this information being written out to a logfile.  Am I missing something?

In my event log, I get one error on the install 'Cannot create a file when that file already exists' ....  at DotNetNuke.Services.Upgrade.Upgrade.UpgradeToVersion_530()  - which pretty matches my experience upgrading to 5.4.1

I'm not seeing any errors in the application itself.

I could roll back the upgrade again! and wait for another new version of DNN, but my confidence level of ever upgrading this DNN installation is low.

Can I fix this problem or at least understand the potential implications?

I did upgrade using my default language, Spanish - but felt fairly confident as the previous problem was reported as fixed in this release.

Any help or advice would be extremely welcome.

Well, yes.  But I've done that, rolling back the upgrade that failed from 5.2.2 to 5.4.1.  

Trying again to upgrade from 5.2.2 to 5.4.2 has failed with the same error as the previous upgrade (all documentation suggests that the problem was solved).

Are you really suggesting that I should roll this one back, try it again and it will work?  An if it doesn't ... take a Robert the Bruce approach?  That doesn't sound too probable to me.

Do you think I should rollback, wait for the next release and give that a try?

Hello;
Can you retry 1 more time and post the UI output and also the SQL log output from the failed SQL script?
You can find the SQLDataProvider scripts here: <drive letter>\<web folder>\Providers\DataProviders\SqlDataProvider.
.
There are an increasing number of reports of failures in 5.3.x SQLDataProvider with Messaging and/or Taxonomy install failures which we have not seen in internal testing and we'd love to get a proper reproduction case so we can fix the issue.

If you, or anyone reading this thread, has a code fix they would like to submit we would gladly accept it!

---

Ken Grierson
DotNetNuke Corporation
Test Lead