Connection Timeout Expired. Alot.

This happens randomly multiple times a week, to random users, at random times. Clicking OK close the program, they log back in and carry on. I have contacted support about this before and we increased all values to the maximum to avoid this error, yet many versions later it persists. The VM that Sage runs on has TONS of spare HDD space, RAM, and CPU cycles trying to combat this. Not sure what else to try, any guidance would be greatly appreciated.

  • This could also by caused a brief network interruption or possibly a DNS issue. One suggestion is on the login window at the top where it has the SQL Server name (server name\sage100con), is to change the name of the server to the IP address of the server. So for example, MYSERVER\SAGE100CON would be 192.168.1.1\SAGE100CON. Would need to do this on each affected workstation. You should only have to do this once as Sage will remember the server IP for the next login.

  • Unfortunately, the same error popped up yet again, this time in the inventory module. Any other suggestions, anyone?

  • Was anything ever a definite fix for this issue?
    We just got the same popup.

  • Error: "Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement," when connecting to Database Administration for Sage 100 Contractor

    Created on 04-20-2017 | Last modified on 02-15-2021

    Summary

    Error: "Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement," when connecting to Database Administration for Sage 100 Contractor
    The users are complaining of a timeout with handshake error at times.
    The error reads "Failed to connect to the specified SQL server" in the title bar.

    Disclaimer

    Network Warning
    This solution requires advanced knowledge of your network. Contact your system administrator for assistance. Modifying Windows security incorrectly can severely affect system operations. Sage is not responsible for operation issues caused by incorrectly modifying your Windows security. Always create a backup of your data before proceeding with advanced solutions.
    Support

    Sage Customer Support does not provide assistance for issues related to third party products or enhancements, hardware, report customizations, state or federal tax-related questions, or specific accounting questions. Please contact your Sage business partner, network administrator, or accountant for assistance. Please review this document for additional information on the scope of Sage Customer Support Services.

    Cause

    It is taking too long to connect to the SQL server before the set timeout period expires. This can be caused by a number of issues. Usually related to network settings.

    1. Workstation network settings incorrect - the DNS Server entry on the workstation is incorrect.

    2. Network DNS Server tables incorrect - Entries for the local network incorrect on the DNS server. This would generally only apply to customers with large in-house networks.

    3. Physical network issues.

    Other Common causes:

    The “Connection Timeout expired” error commonly occurs in the following cases

    1. An instance of the SQL Server Database Engine is not running.
    2. The SQL Server Browser service is not running.
    3. The TCP/IP is disabled.
    4. The server name was typed incorrectly.
    5. There are network problems.
    6. The TCP/IP port for the Database Engine instance is blocked by a firewall.
    7. The client and server are not configured to use the same network protocol.
    8. The Sage 100 Contractor SQL Server instance is damaged and needs repair.

    Resolution

    This issue requires advanced knowledge of networking. The network settings for the workstation should be verified to be correct and the physical network should be verified to be in good working order. This should be done by a local IT person or person with knowledge of networking within a Windows environment.

    Work Around - Only When Other Causes have been eliminated

    This work around may cause the timeout errors to stop but may not correct the root cause of the issue.

    1. Open Database Administration
    2. Select Advanced Settings, Advanced SQL Server Settings
    3. On the right, where it shows Server connection timeout (in seconds), increase the value.
    4. Click Save Changes

    Note: The maximum timeout setting is 60 seconds. The default setting is 15 seconds.

    If the Sage 100 Contractor SQL Server instance is damaged perform the following steps:

    1. From the server machine, open Windows Control Panel.
    2. Click Programs and Features.
    3. Locate Microsoft SQL Server 2014, 2016, 2017, or 2019 (64 bit).
    4. Right-click on Microsoft SQL Server 201# and click Uninstall/Change. Click Repair and run the repair wizard.
    5. When repair is completed, connect and log into Database Administration for Sage 100 Contractor.

    Keywords

    Error: "Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgment, Failed to connect to the specified SQL server
    Need help?

    Related resources

    • Intermittent timeout errors on workstations when working in Sage 100 Contractor SQL

    Additional information

    Try logging in, but before pressing the Connect button, hold down the Shift button and click Connect to see the Database Connection Status window. All accessible databases should show "Available" and "Ready for use".

    Please see the following third-party article for suggested solutions to this issue:

    https://blog.devoworx.net/2017/01/30/connection-timeout-expired-pre-login-handshake/

    The solutions in this article are not published by Sage and should implemented by and at the discretion of your IT or Network Administrator.