FormerMember

Failure to Connect to SQL Server

Posted By FormerMember

Our Sage 100 Contractor is working on the Sage Server but none of the other PCs in the office can connect to the Sage Machine.  The message we are getting is as follows on all the machines that are attempting to connect to the Server:  

Failed to Connect to the Specified SQL Server:

Connection to the Remote Machine running MS SQL Server failed although the machine exists. Check your firewall settings.

Please help this is a new message that came up and no one can connect.  We haven't had issues previously like this.

  • 0

    Hi ,

     

    Since it looks like you are using Sage 100 Contractor US edition, I am going to move this post to that Support Group so that other users of this software will see it and can offer you their thoughts and insight.

     

    Thanks,

    Erzsi

  • 0

    Hi Alberttomar,

    This could mean the connection to SQL is being blocked by the firewall on the server, or the SQL Server name is not being recognized. In the connection window on the workstations, try changing the server name to the server's IP address in the top field. Example: if SQL Server name is "myserver\sage100con", change to "(ip address)\sage100con"

    For the firewall, in windows defender advanced firewall settings, add an inbound rule for TCP Port 1433

    If these do not resolve, please open a web ticket via the customer portal or a new ticket via Live Chat.

    Thank you,

    Greig Hollister

    Sage

  • 0

    Hello Alberttomar!

    When did this problem start?

    Also, in cases like this, it would be useful to tell us, at the very least, the build numbers of Windows (both Server and workstation), SQL Server, and Sage.

    As Microsoft's July Patch Tuesday was just last week (10 July) and IT staff usually patch on weekends, I have to ask: Did your IT staff install or reconfigure anything right before this problem started?

    Such IT work can include things like applying patches for Windows (both Server and workstation) and SQL Server, changing firewall rules on the server or workstations, installing new network monitoring or firewall software, reconfiguring VLAN membership, updating NIC drivers, and updating firmware on the Ethernet switches, WAPs, and router.

    Fyi, Microsoft had some buggy Windows updates last week (10 July) that prompted them to quickly release fixes for Windows (server and workstation) this past Monday (16 July).

    These fixes are KB4345424 (for Windows 8.1 and Server 2012 R2), KB4345420 (for Windows 10 Version 1709 and Server 1709), and KB4345421 (for Windows 10 Version 1803 and Server 1803).

    Let us know how you eventually resolved this issue.

    Best,

    Roberto