When you try to connect Microsoft SQL Server with SQL-Toolkit plugin, the Active Console may display the error "Unable to complete login process due to delay in opening server connection". This article discusses the common issues and solutions.
General Troubleshooting
SQL-Toolkit initiates the connection from the Netprobe side to the SQL Server database, which can be on the local machine or remote server. Users should perform general checking which include:
- Connectivity issues (network, firewall, DNS issues)
- SQL Server is running and not overloaded
- SQL Client is compatible and up-to-date
Cluster Environment ("SQL Server Always On")
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.
Users should check that they are using Netprobe version GA6.2 and above (COL-11312), which includes an option to handle failover scenarios for MS SQL Server databases. Users should enable the MultiSubnetFailover option in SQL-Toolkit plugin configuration.
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:
HostRecordTTL Setting
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.
Comments
0 comments
Please sign in to leave a comment.