FunkyBlue

I got it. It was the MYSQL cnf file. It sayd for version 8.0 to put in a line in [mqsqld], but says if you're using 5.62 (or other version) to put in two other lines. I didn't put those lines in because the instructions don't specify they need to be used for 8.0 and make it look like you don't need it. Added those two line in, reloaded mysql, installing now.

Nevermind. I added an erauser account, re-ran the script, no longer gives me password wrong. Now just back to Database not configured properly again.

Ok, I think I may have found one issue. You know when they say "It's DNS"? That may be part of it. I manually added the host into my DNS server and changed the user to erauser. then it came back and said user had the wrong password instead of straight failed. I put my created user back in (esetdb) and failed again. Should I create the erauser as a user in MYSQL before running it?

Let me get back there and try this again. I even tried copying each switch individually to avoid blank or unneeded characters. I'll update after I have regained consciousness from beating my head into this wall.

I went back through with a whole new Ubuntu 20 VM. Followed everything to the letter. Everything looks good, replies back with the correct responses, go to install the server, "Database not configured properly". I went back over the installation instructions, verified I was using the instructions for Ubuntu 20, ODBC 8.0, and MySQL 8. I have tried several permutations of the install script, including a new MYSQL user with root privileges and remote access to the system. I have a ticket in now, but this has been frustrating far beyond belief. I may have to wait until my new servers come in to upgrade to VMWare 6.7 and then use the VM Appliance...

You know what, I have set up several Ubuntu servers that run internal and public facing webservers, drive imaging, business process management, human resources, and equipment inventory. All virtual, all running either 16.04 or 18.04. I have enough Linux skills to get all of those running with no issues. I have run into many systems where that wasn't so, but it was because the instructions have been terrible. Devs sometimes forget that everyone may have a different definition of what "standard prerequisites" means. One install of a process management system forgot to include 3-4 pieces of software that are not preinstalled on a new install of Ubuntu, and of those, 1 needed a repository added to download it. None of this was mentioned in the installs and it took me reading the logs, googling the module it was missing, and trying the install again and again until I finished it. The OP is not wrong with these instructions. They are not structured right. The server install information comes before the pre-reqs, for one thing. A user paying for and installing this software shouldn't need sysadmin god-level training to install this. For crying out loud, we shouldn't have to read between the lined about what version of a software piece is compatible. Don't tell us what we can't use. Instead of saying "Version 1, 2, 5, 6 are incompatible", just pick a compatible version and tell us "install version 4" and then provide the details on how to do that particular piece. I'm in the same spot right now. Error 1698 running ODBC 5.3 after 8.0 didn't work on MySQL 5.72, which I thought was listed as compatible, but now see where it needs to be a particular version of 8.0. Again, pick a version, tell the user what exactly they should use to make your software work, and then give them directions based on that. Split it up, if you need to. "If you're using MySQL on Linux, go here:" and give them pertinent info based on their distro. Don't give us "step-by-step" instructions that start in the middle, send us backwards, and then don't give you the right information so that you have to start over after you google your error and find out you've been using the "wrong version" the whole time. I have waded through some terrible instructions for open source software, and taken it with a bit of humor since it was a free license I'm working with and it most likely came from someone in their home working on it in their spare time. But this is one of the larger and more highly rated AV vendors out there and this level of installation documentation is not about having "l33t Linux Skeellz". Also, if I was going to paste my install script in a public forum, I wouldn't put the passwords I was using to install it. I would put them in as "password". Security thing. Kind of important. Now, that being said, I'm wiping this VM and starting over again with the "compatible versions" and see if I have more luck.