Microsoft SQL Server databases can be configured as a cluster. This provides a high-availability database environment for SQL Server clients. For example, if database node01 fails, the SQL Server clients connected to node01 are routed to the next active database node.
Older Netprobe versions did not provide support for MS SQL Server database cluster. The SQL-Toolkit plugin may return error "Unable to complete login process due to delay in opening server connection" when its target database node01 fails or is offline.
Users should check that the Netprobe has been upgraded to version GA6.2 and above which includes the fix COL-11312. The SQL-Toolkit plugin had since added the MultiSubnetFailover option for MS SQL Server database. The option should be enabled to handle database failover scenarios.
Workaround on older Netprobe versions
One workaround suggested in the Microsoft website is to reconfigure the database cluster's HostRecordTTL so that clients can reconnect quickly to the next available node:
By default, clients cache cluster DNS records for 20 minutes. By reducing HostRecordTTL, the Time to Live (TTL), for the cached record, legacy clients may reconnect more quickly. However, reducing the HostRecordTTL setting may also result in increased traffic to the DNS servers.