FMS will not startup due to mysqld.exe crashing.
In the FMS logs you will see the following error:
2016-03-02 11:03:23.912 INFO [STDIN/mysqld] com.quest.nitro.db.EmbeddedDatabaseManager - STDIN/mysqld:2016-03-02 11:03:23 32c InnoDB: Error: page 2 log sequence number 837207949069
2016-03-02 11:03:23.912 INFO [STDIN/mysqld] com.quest.nitro.db.EmbeddedDatabaseManager - STDIN/mysqld:InnoDB: is in the future! Current system log sequence number 837174587357.
2016-03-02 11:03:23.912 INFO [STDIN/mysqld] com.quest.nitro.db.EmbeddedDatabaseManager - STDIN/mysqld:InnoDB: Your database may be corrupt or you may have copied the InnoDB
2016-03-02 11:03:23.912 INFO [STDIN/mysqld] com.quest.nitro.db.EmbeddedDatabaseManager - STDIN/mysqld:InnoDB: tablespace but not the InnoDB log files. See
2016-03-02 11:03:23.912 INFO [STDIN/mysqld] com.quest.nitro.db.EmbeddedDatabaseManager - STDIN/mysqld:InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
2016-03-02 11:03:23.912 INFO [STDIN/mysqld] com.quest.nitro.db.EmbeddedDatabaseManager - STDIN/mysqld:InnoDB: for more information.
2016-03-02 11:03:24.380 INFO [STDIN/mysqld] com.quest.nitro.db.EmbeddedDatabaseManager - STDIN/mysqld:2016-03-02 11:03:23 316:03:24 UTC - mysqld got exception 0x80000003 ;
2016-03-02 11:03:24.380 INFO [STDIN/mysqld] com.quest.nitro.db.EmbeddedDatabaseManager - STDIN/mysqld:This could be because you hit a bug. It is also possible that this binary
2016-03-02 11:03:24.380 INFO [STDIN/mysqld] com.quest.nitro.db.EmbeddedDatabaseManager - STDIN/mysqld:or one of the libraries it was linked against is corrupt, improperly built,
2016-03-02 11:03:24.380 INFO [STDIN/mysqld] com.quest.nitro.db.EmbeddedDatabaseManager - STDIN/mysqld:or misconfigured. This error can also be caused by malfunctioning hardware.
2016-03-02 11:03:24.380 INFO [STDIN/mysqld] com.quest.nitro.db.EmbeddedDatabaseManager - STDIN/mysqld:We will try our best to scrape up some info that will hopefully help
2016-03-02 11:03:24.380 INFO [STDIN/mysqld] com.quest.nitro.db.EmbeddedDatabaseManager - STDIN/mysqld:diagnose the problem, but since we have already crashed,
2016-03-02 11:03:24.380 INFO [STDIN/mysqld] com.quest.nitro.db.EmbeddedDatabaseManager - STDIN/mysqld:something is definitely wrong and this may fail.
2016-03-02 11:03:24.380 INFO [STDIN/mysqld] com.quest.nitro.db.EmbeddedDatabaseManager - STDIN/mysqld: