Yes, the path list did show that MySQL would be installed on C:BSOD2600 wrote: 1) The MySQL silent installer doesn't give an option on where its installed so it defaults to %ProgramFiles%. I'm not aware of any workaround. On the last page of the Cacti installer it should've listed the paths to review.
Here's the error log from the initial startup:BSOD2600 wrote: 2) can you share more details about the specific error which prevented MySQL from starting? C:\ProgramData\MySQL\MySQL Server 5.6\data\*.err should contain the details. The my.ini was dynamically created by the MySQL installer apparently based off your system resources. I suspect the innodb_buffer_pool_size was dynamically configured. For example on my test Win2K8R2x64 VM with 2GB, the installer set innodb_buffer_pool_size=238M.
Code: Select all
2014-06-02 14:57:36 15696 [Note] Plugin 'FEDERATED' is disabled.
2014-06-02 14:57:36 4eec InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2014-06-02 14:57:36 15696 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-06-02 14:57:36 15696 [Note] InnoDB: The InnoDB memory heap is disabled
2014-06-02 14:57:36 15696 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-06-02 14:57:36 15696 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-06-02 14:57:36 15696 [Note] InnoDB: Not using CPU crc32 instructions
2014-06-02 14:57:36 15696 [Note] InnoDB: Initializing buffer pool, size = 3.0G
InnoDB: VirtualAlloc(181403648 bytes) failed; Windows error 8
2014-06-02 14:57:36 15696 [ERROR] InnoDB: Cannot allocate memory for the buffer pool
2014-06-02 14:57:36 15696 [ERROR] Plugin 'InnoDB' init function returned error.
2014-06-02 14:57:36 15696 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2014-06-02 14:57:36 15696 [ERROR] Unknown/unsupported storage engine: INNODB
2014-06-02 14:57:36 15696 [ERROR] Aborting