Login Timeout Expired for all networked clients connecting to GoldMine - The Application Server where Microsoft SQL Server is installed works fine.

Version 3

    [BEHAVIOR]/[SYMPTOMS]

     

    After new installations, migrations of GoldMine or changes in the system environment, all networked clients are getting the following error

     

    Login Timeout Expired for all networked clients connecting to GoldMine, when clicking OK the GoldMine SQL Login window appears

    GoldMine on the machine where Microsoft SQL Server is also installed starts correctly and without the same message

     

     

    [SUGGESTIONS]

    As all networked clients fail to connect the most likely reason is a configuration issue on the Microsoft SQL Server machine.

     

    A. Verify Firewall has TCP port 1433 (MS SQL default port) opened 

    Very often this needs only to be adjusted on the MS SQL Server/Application Server but might be also necessary to be reviewed on the local machine depending which and how the Firewall is setup
    The following article may help to adjust the Windows Firewall
    http://msdn.microsoft.com/en-us/library/cc646023.aspx
    http://technet.microsoft.com/en-us/library/cc766312(v=ws.10).aspx
    http://technet.microsoft.com/en-us/library/cc753558.aspx


    Please keep in mind that certain Microsoft SQL Server installation (e.g. named instances or SQL Express) may use dynamic ports instead, in such cases either

    - The SQLSERVR.EXE should be added as Program related exceptions for the Firewall instead of a certain port

    Windows Firewall Is Blocking a Program

    - The SQL Server configuration needs to be adjusted to listen on port 1433 (or another desired and open port)

    https://support.microsoft.com/en-us/help/823938/how-to-configure-sql-server-to-listen-on-a-specific-port

    Configure a Server to Listen on a Specific TCP Port | Microsoft Docs


    B. Make sure that Named Pipes and TCP/IP are set in the SQL Server Configuration Manager >> applies to SQL Server Network Configuration, SQL Server Native Client Configuration (32-bit ) on 64-bit MS SQL installations and SQL Server Native Client Configuration on 32-bit MS SQL installations

    1. On MS SQL Server machine
    2. Start >> (All) Programs >> Microsoft SQL Server xxxx >> Configuration Tools >> SQL Server Configuration Manager
    3. Browse to SQL Server Network Configuration >> Protocols
    4. Make sure that Named Pipes and TCP/IP is enabled
    5. Browse to SQL Server Native Client Configuration 32-bit (on 64-bit installations of MS SQL Server) / SQL Server Native Client Configuration  (on 32-bit installations of MS SQL Server) >> Client Protocols
    6. Make sure that Named Pipes and TCP/IP is enabled and that order is Named Pipes prior TCP/IP
    7. It might be necessary to restart the MS SQL Server services

    The following articles provide the information how to adjust and further information
    http://msdn.microsoft.com/en-us/library/ms190425(v=sql.105).aspx
    http://msdn.microsoft.com/en-us/library/ms181035.aspx
    http://msdn.microsoft.com/en-us/library/ms189083.aspx


    C. On certain environments also the SQL Server Browser Service needs to be started, in this cases also the related port (by default UDP port 1434) should be opened in the Firewall

    From SQL Server Configuration Manager

    1. On MS SQL Server machine
    2. Start >> (All) Programs >> Microsoft SQL Server xxxx >> Configuration Tools >> SQL Server Configuration Manager
    3. Browse to SQL Server Services
    4. Start SQL Server Browser

    From Windows Services (services.msc) >> Configure and Start SQL Server Browser

    The following article provides further information about the SQL Server Browser Service
    https://technet.microsoft.com/en-us/library/ms181087(v=sql.105).aspx

     

     

    Additional Information:

    On the networked GoldMine client enable SQL Server Client Network Utility to Named Pipes and TCP/IP

     


    On a 32-bit Operating system - Do not set this for GoldMine on a 64-bit Operating System 

    1. Browse to C:\Windows\SYSTEM32\cliconfg.exe
    2. Highlight Named Pipes >> Button Enable
    3.
    Highlight
    TCP/IP >> Button Enable

    4. OK
    5. Verify that GoldMine is now starting successfully and as expected


    On a 64-bit Operating system - Use this when using GoldMine on a 64-bit Operating System

    1. Browse to C:\Windows\SYSWOW64\cliconfg.exe
    2. Highlight Named Pipes >> Button Enable
    3.
    Highlight TCP/IP >> Button Enable


    4. OK