|
Question: Why does Foxhound "lock up" and become unresponsive?
Answer:
One reason may be that a database monitor session is repeatedly trying to connect to a target
database that is not available. In this case the workaround is to switch to
the Monitor tab of the Foxhound menu, and click on the Cancel button to stop Foxhound
from repeatedly trying to connect to that database.
Another workaround is to kill the Foxhound dbsrv16.exe task and then restart Foxhound in "safe mode";
see Help - Introduction - Safe Mode Startup.
|