The Ultimate Guide to High Availability with MariaDB

MariaDB installation problem on 12CPU 48GB server

You are viewing an old version of this question. View the current version here.

Hi,

I am setting up a Windows 2016 server with MariaDB to see if it is a viable option to switch to MariaDB. The server is a Dell T5500 2x SixCore X5670 2.93GHz, 3x16GB, drive 0 = 400GB SSD, drive 1 = 3TB HDD.

The installation goes like a charm, right till the end ("copying new files", then "running mariadb-install-db.exe"), and then it suddenly starts to rollback, saying "MariaDB 11.4 (x64) Setup Wizard ended prematurely" because of "an error".

It is ful linstall MariaDB v11.4.2 winx64, set up without remote acces for root, and with UTF8. Lowering the pool size to 4096MB or raising the Page size to 64KB make no difference.

The Windows Event Log shows a few events, of which these are the most informational: - Product: MariaDB 11.4 (x64) -- Installation failed. - Windows Installer installed the product. Product Name: MariaDB 11.4 (x64). Product Version: 11.4.2.0. Product Language: 1033. Manufacturer: MariaDB orporation Ab. Installation succes or error status: 1603.

When I lookup info about error 1603 of an installer, the following possible causes are mentioned:

  • Windows Installer is attempting to install an app that is already installed on your PC.
  • The folder that you are trying to install the Windows Installer package to is encrypted.
  • The drive that contains the folder that you are trying to install the Windows Installer package to is accessed as a substitute drive.
  • The SYSTEM account does not have Full Control permissions on the folder that you are trying to install the Windows Installer package to. You notice the error message because the Windows Installer service uses the SYSTEM account to install software.

None of these causes apply.... I checked. No encrypted folder, no existing installation of MariaDB, no SUBST, and full access for the SYSTEM account. I also tried installing in a different (custom) directory on the SSD, making sure SYSTEM had all rights there, but symptoms are exactly the same.

Could it be that it is due to the 12 cores? If so, how could I assign less cores to MariaDB? Or does anyone have some kind of clue?

Thanks a lot in advance! Silvan Kuipers

Answer

SOLVED.

On Win2016 the max version is 10.7.2. I now used a 10.6.xx and it works just fine. Let's test drive it, and see if it is a good replacement.

Have a nice day :-)

Comments

Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.