InfoSol Help Desk

Occasionally, IBE when connected to a non-local Microsoft SQL Server Repository, loses connection, for whatever reason, and becomes a stupid shell of what it once was. resulting in missed schedules, expired jobs and just plain inconvenience until someone logs in, notices they are <username (2)> instead of themselves.

I created a Batch program to be run every 2 hours to look in the LOGS folder for the current IBSERVICE log and finds the string (if existing) "LOST_DB_CONNECTION".

Upon finding it, the file will stop the IBEServer.exe service, rename the log, move it to the ERRORFINDING subfolder, restart the IBEServer.exe service and notify the Admin Group of the found issue to review at a later time.

Since these issues may occur in the wee hours of the night, this file will save the headache of waking up to missed schedules and scrambling to resolve the issue.

Enhancement request, is to create a daemon that runs in the background of the service, changing the log for this issue and gracefully restarting the service to re-gain the lost connection. After 5 (or x) successive restarts within 5 minutes, the service should remain down and support notified to correct the underlying issue.