False ODBC Connect Service and Database down Errors in System Status

Document created by Christopher_Walsh Employee on Aug 7, 2014
Version 1Show Document
  • View in full screen mode

You may notice after a System Reboot or a recycling of services on one or all of your RA servers that you get persistent messages in the "Administration->System Status" page like below:

The ODBC Connect Service's current state is Stopped.
Database is down

This often times causes alarm that something serious may be wrong with the system.

This error seems to persist for a while after a recycling of services or a reboot in some cases, but should clear within a few hours or so if not right away.

Many clients see this on the weekends when Microsoft Update cause a system reboot.

The best thing to do is verify "NetQos Mysql51" service is started on all servers.

Also that after about 15 minutes after the system is rebooted that the RA data is still updating.

If you can verify both of the above, you will most likely just need to wait for the "System Status" messages to clear on their own.

 

 

This document was generated from the following discussion: False ODBC Connect Service and Database down Errors in System Status

Attachments

    Outcomes