I have been trying to figure out this same thing. Same exact error here:

2022-2-10 T11:05:46::Upgrade::5691::MariaDB status: The system cannot open the file.

2022-2-10 T11:05:46::Upgrade::5696:: /c mysql_upgrade -ustratus -p******* -P3306
2022-2-10 T11:05:47::Upgrade::5700::Failed to upgrade mysql Incorrect function.

Hi,

Since I had a good backup and Dell really wasn't being as responsive as I would have liked them to be, I reverted, disabled all security products and tried again.  This time, I succeeded.

Thanks,

smboberHP

Same problem. Dell support is useless.

You think it's a security product problem? I only have Symantec AV and Redcloak installed.

Now, I can't even access the web portal (Even after reverting back) Strange.

might be this command:

2022-2-10 T11:05:46::Upgrade::5696:: /c mysql_upgrade -ustratus -p******* -P3306

notice that the -u is attached to stratus username?

Its common for mysql commands to have the username and password without any space between them after the switch.

If you are experiencing the upgrade fails with an error equal to the error by the original thread please contact support and open a case.  There is a workaround that has proven successful with other customers that will be addressed in a future build available for validation.   

If you get pushback from support, or they do not seem to be aware of the workaround message me your case#.

#IWork4Dell.  

I am able to comment that Dell does indeed have a document on how to resolve this exact issue.

Once I got the document, the steps worked for me.

You want to know what would have been better Dell? Just posting the data here. Here's the nonsense I had to deal with to get the document.

1) Call normal support, as we use the free version of Dell WMS. Support is useless. Won't start the conversation without a Service Tag. Give them a service tag.

2) Oops that tag belongs to ProSupport! You need to call them. No, they can't transfer you.

3) ProSupport wants a Service Tag. Oh, did you say this software was installed on a server? Then you need Enterprise Support.

4) Enterprise support wants a Service Tag. What if I happened to choose to not run Dell WMS on Dell Hardware? I would have been unable to proceed.

5) 2 hours later: Here's the process document.

6) Me: 4 hours later, having blocked all GPOs, I have finally upgraded from 3.3.1 to 3.6 (oh, we don't need to talk about how ANY of the 3.5.x upgrades never worked).

This has burned a full workday for me, not including the days back when 3.5.x came out. I'm not a fan.

I finally got PRD from 3.3.1 to 3.6 as well.  Before I began, I had to make 100% sure that there wasn't anything security related on the box.  Then, I had to go through this process to manually back up and upgrade the MariaDB prior to doing the 3.6 upgrade.  The instructions left a lot to be desired.  I added some of my notes.  In a couple of places.  Maybe they will help someone.

Dell Wyse Reference Documentation

Dell Wyse Management Suite upgrading MariaDB Manually

February 2022

Revision 1.0

MariaDB Manual upgrade steps from 3.3.1 to 3.6:

Reference for Default values:

TARGETDIR = “C:\Program Files\DELL\WMS”

Maria port : 3306

Step 1 : Backup

DB Backup before starting the upgrade:

• Command to take Backup of DB :

> TARGETDIR\MariaDB\bin\mysqldump.exe --routines -u -p -P -hlocalhost   > "TARGETDIR\MariaDB\bin\stratus.sql"

The above info his horrible.  There is a space missing after the -h and if you fill in the info with what you expect that you would put in there, then it will never work.

Here is what worked for me:

mysqldump.exe --routines -u PutYourDBUsernameHere -p PutTheNameOfYourDBHere -P 3306 -h localhost > "C:\Program Files\DELL\WMS\MariaDB\bin\stratus.sql"

• Stop ALL WMS Services.
  • Tomcat
  • Memcached
  • Mqtt
  • MongoDB
  • MariaDB

• Archive the old binaries:
  • Copy MariaDB from “TARGETDIR\MariaDB” to “TARGETDIR\Archive” folder and Delete  “TARGETDIR\MariaDB” folder
  • Copy SQL DB folder from “TARGETDIR\Database” to “TARGETDIR\Archive\Database” folder.

Step 2: Upgrade MariaDB

MySQL Upgrade steps:

• MariaDB Binary location: https://archive.mariadb.org/mariadb-10.6.5/winx64-packages/mariadb-10.6.5-winx64.zip
• Copy New MariaDB-10.6.5 Binaries to TARGETDIR\MariaDB folder.
• Rename the SQL log file - TARGETDIR\Database
• \SQL\ib_logfile0 to “ib_logfile0.old”
• Rename the SQL log file - TARGETDIR\Database\SQL\ib_logfile1 to “ib_logfile1.old”
• Start MySQL service.
• Run below command for MySQL Table migration.

>TARGETDIR\MariaDB\bin\ mysql_upgrade -u  -p -P --debug-check --debug-info

Again, the above info is bad.  Here is what worked:

mysql_upgrade.exe -u PutYourDBUsernameHere -p PutTheNameOfYourDBHere -P 3306 --debug-check --debug-info

• Check for “TARGETDIR\Database\SQL\”mysql_upgrade_info” file creation after running the above command successfully.

Step 3: Start All Services

• Stop ßThis should say Start ALL WMS Services.
  • MariaDB
  • MongoDB
  • memcahced
  • mqtt
  • Tomcat

Launch application and check for sanity.

Step 4: Upgrade to WMS 3.6

Optional Step

Rollback Steps for MySQL upgrade:

• Stop the MySQL service.
• Delete “TARGETDIR\MariaDB” folder
• Delete “TARGETDIR\Database\SQL” folder
• Copy the Old MariaDB folder from “TARGETDIR\Archive” to “TARGETDIR”
• Copy the Old SQL folder from “TARGETDIR\Archive\Database\SQL” to “TARGETDIR\Database”
• Start the MySQL service.
• Run below command to Restore Mysql DB:

Step1: Drop DB cmd:  >TARGETDIR\MariDB\bin\mysql.exe --verbose -u  -p  -P  -hlocalhost -e "DROP DATABASE "

Step2: CreateDB cmd:  >TARGETDIR\MariDB\bin\mysql.exe --verbose -u   -p   -P   -hlocalhost -e "CREATE DATABASE DEFAULT CHARACTER SET utf8 DEFAULT COLLATE utf8_unicode_ci”

Step3:  Restore cmd:  >TARGETDIR\MariDB\bin\mysql.exe --verbose -u  -p -P  -hlocalhost < " TARGETDIR \MariaDB\bin\stratus.sql"

Thanks for posting the document. I was debating doing it myself but I wanted to "cool down" after that support experience.

I have two things that may be helpful relating to the MySQL commands. I ran them as noted in the doc without issue, but here's what I had done:

mysqldump.exe --routines -u -p -P -hlocalhost   > "TARGETDIR\MariaDB\bin\stratus.sql"

1) Apparently the MysqlDBuser is "stratus". That makes sense given the filename they want you to use and reading the logs.

2) I don't recall or remember my initial Mongo/MySQL passwords. I reset them within the WMS frontend while it was still active. DB port is 3306.

I also didn't have any issues doing -u, -p, -P, -h with no space after the toggle. I thought that was odd, but read elsewhere it is okay to do that.

Thanks again for the post. I can't wait to be here again slamming my head against the wall on the next CVE update for WMS...

Thank you, I worked with dell since this came out and got nowhere. This is what fixed it.