SQL Enterprise Job Manager connects frequently to managed SQL Server instances to ensure they are available and responsive. If the SQL instance becomes unreachable for any reason an alert will be raised to let operators know that an availability problem may have arisen.

Below you can find some possible workarounds:

• First, attempt to connect to the SQL Server instance by means other than SQL Enterprise Job Manager.
• If the connection fails, take note of any error message, which may in some cases explain what the issue is. If the message is not helpful or if the connection simply times out, verify whether the host Windows server is available through a ping test or by attempting to connect via remote desktop.
• If the server is not responsive, it may be necessary to troubleshoot further to determine whether it is a network issue or whether the server is offline or unresponsive. When the server is verified to be back online and reachable, check to make sure that the SQL Server services are started for any and all hosted SQL Server instances.
• If the SQL Server instance or Windows server was offline and the downtime was sudden or unexpected, SQL Server may need to run recovery for its hosted databases before the instance will be fully available again. Recovery is the process by which completed database transactions are recovered and incomplete transactions are rolled back, bringing the system back into a consistent state. This may complete quickly or it could take an extended period of time, so pay close attention to the status of the databases on this instance until they are all accessible again.
• If the server is online and this message appears to be in error, it could be that network or security issues are preventing SQL Enterprise Job Manager from making a connection. Ensure that SQL Enterprise Job Manager is connecting to the SQL Server with credentials that have the right to connect to the target server.