Readysell MySQL is stuck in "Starting"

This could be a result of the corrupted tables in the database or some other issues which is causing the issue. It is best practice to review the event viewer and the checking for errors to see if the can helps to the find correct procedure and research for the properly solution for the issue. This information can allow you to find the database is damaged and is prevent certain function and service from running properly to operate the Readysell Server and Clients. This is fix doesn’t applied to this situation, please investigate the issue further and contact other staff members if required.

Applying the innodb_force_recovery to “My.” config file

Navigate to the my. config file in the Readysell Folder (e.g. C:\Readysell Computer Solutions\Readysell\MySQL) and open the file previously mentioned in notepad or a program which will allow you to alter and save modifications withing the text of the configuration file.

Insert the file following line (innodb_force_recovery=1) into the file as see in the screenshot.

Open

Save the changes in notepad with the additional line applied to the configuration file within the MySQL folder mention before (e.g. C:\Readysell Computer Solutions\Readysell\MySQL).

Once the saving of the file is completed, restart the server to allow the allow all service with the server be started again which includes the Readysell MySQL service. To restart the server. Click in the windows icon at the bottom left hand corner on the screen, left click on the Power Icon and then left click on the Restart. Ensure that the client is aware that your need to restart the server and they will need to close out of Readysell if they have any client still open during the situation.

Once the server has been restart back into windows and log back into the windows, check that the services (ReadysellMySQL, ReadysellServer and possibly the ReadysellTasks) are running. Also check the Client is working as well. It is also important to ensure that the Readysell task are running like the Buying group sync, Autowarehousing and Readysell Backups.

If successful, the Readysell MySQL should be running and you can proceed with starting the other services and Readysell Application. If it doesn’t start the service. please review the eventviewer and discuss with support team for further assistance in this matter.

Checking the database after it recovers in the “innodb_force_recovery” fix

Once the live database is up and running, run a standard heidi table check on the database before the client starts their readysell clients on the other workstation. This will ensure that the corruption/damage of the table is not going to further damage to the rest of the database.

Open the Heidi SQL application and log using the credentials applied when configuring teh Readysell on the server.

Within the heidi window, select the database which your need to review the tables for. Once highlighted, right click on the selected database and then select from teh list of option maintenance. Once the maintenance screen appears, select Check. this will start checking all the tables for any forms of corruption or damage which the operate will need to review once it completes. If the are any tables in the database have any obvious error, the heidi application will report to the operator. This check could be preformed while the client is in the Readysell System but if you or an operator have a occur that there is a corruption in the database, it is best practice to allow the check to be completed before modified the data even further. The check would also slow the performance of teh Readysell application down while teh check is being completed.

It is also recommended that the same check is to be completed the next day to ensure that the databas are not corrupted or damaged the next day. this will also confirmed that all tasks are completed successfully in Readysell.