Bug #74623 Quiet mode install fails to install manifest
Submitted: 29 Oct 2014 17:06 Modified: 14 Aug 2015 0:07
Reporter: George Thornton Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Installing Severity:S2 (Serious)
Version:5.6.21.1 OS:Windows
Assigned to: CPU Architecture:Any

[29 Oct 2014 17:06] George Thornton
Description:
After running the Community installer in quiet mode, the manifest has not been correctly installed. As a result of this the MySQLInstallerConsole.exe fails to run with the message:

Configuration file was not found. Please resinstall(sic) a MySQL Installer bundle.

If you look in the C:\ProgramData\MySQL\MySQL Installer for Windows folder you will see a file "NewManifest.zip". This contains the necessary files that allow the console to run, however it has not been unzipped.

How to repeat:
Start with community installer UNinstalled:

msiexec /x mysql-installer-community-5.6.21.1.msi /quiet

Then reinstall with a quiet install:

msiexec /i mysql-installer-community-5.6.21.1.msi /quiet

Then attempt to run the console:

MySQLInstallerConsole.exe

See the error message box that pops up. 

NOTE: If you run the community installer msi _without_ the /quiet option, then it will correctly unpack the manifest files and the console can run.

It is only when the /quiet option is used that the manifest is not unpacked and the console is then unable to run.

Suggested fix:
Ensure the quiet install performs all installation tasks correctly, including unpacking the manifest.
[29 Oct 2014 19:51] MySQL Verification Team
Thank you for the bug report. Are you able to provide the screenshot of the message error?. Thanks.
[30 Oct 2014 0:35] George Thornton
Error message from console after quiet install

Attachment: MySQLInstallerConsoleError.jpg (image/jpeg, text), 60.58 KiB.

[30 Oct 2014 13:13] MySQL Verification Team
Thank you for the steps and feedback.
Confirmed the issue at my end on Win7(64).

Thanks,
Umesh
[30 Oct 2014 13:14] MySQL Verification Team
Screenshot..

Attachment: 74623.png (image/png, text), 36.53 KiB.

[7 Jan 2015 13:13] Marcin Tomiak
Is there any workaround for this issue? I need to install MySQL silently and this bug stops me to do so. It would be great if some one would post workaround while this bug is not fixed.
[7 Jan 2015 13:33] Marcin Tomiak
Obviously the workaround is to unzip manually from command line NewManifest.zip to directory named Manifest.
[11 Feb 2015 23:17] Rogelio Navarro
Problem still present on 5.6.23.0
[25 Feb 2015 14:41] Gary Roussak
Bug still present as of 25th Feb 2014, albeit now in MySQL Installer version 5.6.23.0. Exactly the same error (with the same spelling typo) as reported by George Thornton. This is affecting me too. I need to create a silent install with Setup Factory and cannot do so.
[16 Mar 2015 14:37] Stephen Palmucci
Referring to comment posted 7-Jan: Obviously the workaround is to unzip manually from command line NewManifest.zip to directory named Manifest.

I'm attempting to use the /quiet installation in an effort to automate DB Server creation.
Questions:  
* Where does one obtain 'NewManifest.zip' if using the 'mysql-installer-commercial-5.6.23.0.msi'?
* Where would the directory 'Manifest' be located.
[28 Jul 2015 1:56] Jose Gabriel Valencia Ornelas
the manifest is applied correctly now in the first execution and is allowed
to call with the CONSOLEARGS, internally will call the MySQLInstallerConsole
<License> <args>
also is allowed to use the /qn from msiexec and call direclty the CLI without
launch de GUI first

ex. mysqlinstallerconsole.exe install
server;5.6.26;x64:*:type=config;openfirewall=true;generallog=true;binlog=true;
serverid=3366;enable_tcpip=true;port=3366;rootpasswd=root:type=user;username=u
ser;password=password;role=DBManager -silent
[14 Aug 2015 0:07] Philip Olson
Posted by developer:
 
Fixed as of the upcoming MySQL Installer 1.4.10 release, and here's the changelog entry:

Installing MySQL Installer in quiet mode would not correctly install the product
manifest (catalog). The quiet option now successfully downloads the
manifest.

Thank you for the bug report.