System Health Check

MyQ performs registered checks which can return error messages and their level of severity, these can be viewed in System Health Check. The errors concern database health, disk space availability, PIN length settings, time zone configuration, etc.

Every error message is logged in the MyQ main log.

When the error message has a Critical severity, the related MyQ service is stopped, and the administrator gets an email notification about it.

To access the system health check overview, log in as admin to MyQ and go to MyQ> System Health Check or click on the system health check button on the top-right side of the window.

Click Run to trigger the System health check Task schedule to perform a check.

Click Show hidden to view any hidden checks on the list.

Click Scheduled task to open the System Health Check task in Task Scheduler, where you can view and modify it.

Error codes and their severity are listed in the table below.

Error Code	Severity	Description	Troubleshooting Steps
101	High	Main database health issues	Run database consistency checks. Verify connectivity and restart services after ensuring sufficient disk space. Complete a database back-up and restore.
102	High	Log database health issues	Check log database and clear outdated logs using scheduled tasks. Complete a database back-up and restore.
103	Medium	PIN length needs adjustment	Adjust PIN policies to enforce a higher minimum character count, learn more here.
104	High	Disk space warning	Perform disk cleanup tasks and consider expanding storage or migrating data folders.
105	Critical	Disk space critical	Immediately free up disk space or expand storage. Verify shared drive accessibility in clustered environments.
106	High	Time zone misconfiguration	Synchronize time zones across servers and update configuration files to match the OS settings.
107	Medium	Queue errors	Review queue configurations and test printer connectivity using standard network diagnostic tools.
108	Medium	Obsolete terminal version	Deploy updated terminal packages and adjust device-specific settings to modern protocols.
109	High	HTTP server unresponsive	Restart HTTP services and verify firewall exceptions for critical ports. Confirm network settings, particularly IP/hostname. Check that system performance is higher than the minimum system requirements.
110	High	HTTP timeout	Inspect web server logs for conflicts and disable non-essential modules.
111	High	Terminal package unresponsive	Restart terminal services or reinstall terminal software if issues persist. Check that system performance is higher than the minimum system requirements.
112	High	Services not running	Restart affected services and confirm service account permissions align with system requirements.
113	Medium	Service account mismatch	Reconfigure services to use appropriate system or domain accounts with necessary privileges.
114	Medium	Default database password	Change default database credentials and update configuration files accordingly.
115	Medium	Default admin password	Reset administrator passwords and enable multi-factor authentication for enhanced security.
116	High	Sites have not been replicated for more than 30 days	Verify replication settings in MyQ Web UI. Check network connectivity between Central and unreported Sites. Restart replication services.
117	Medium	Email duplicates found	Confirm `AllowEmailAddressDuplicity` in `config.ini`. Audit user email fields for duplicates.
118	High	Database page size 8 KB (may impact performance)	Create full database backup. Restore database with 16 KB page size. Monitor performance post-restore.
119	Medium	Connection secret keys expired/near expiry	Identify expiring keys. Generate new keys and update API configurations. Restart affected services.
120	Medium/High	CA certificate expiring (Medium) or expired (High)	Check and replace expiring or expired certificates.
121	Medium/High	Server certificate expiring (Medium) or expired (High)	Check and replace expiring or expired certificates.