Track-It! : Solving Connectivity errors to SQL Server

Version 3
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    Track-It!


    COMPONENT:

    Track-It! 2019 R3


    APPLIES TO:

    Track-It! all versions



    PROBLEM:

    Majority of connectivity issues to SQL server, can be solved by going through a simple checklist and a sequence of easy steps. This guided walk through aims at providing the same for various connection errors that connecting to SQL Server.

    Before you delve into troubleshooting specific connectivity errors, we recommend, though not mandatory, you gather the prerequisite items and run down a quick checklist. Though they may appear to take an extra few minutes of your time they can help get to the resolution sooner.


    SOLUTION:

     

      To effectively use this troubleshooter, you may want to gather the following information. 
      
       
    1. The complete text of the error message along with the error codes and whether the error is intermittent (happens only sometimes) or consistent (happens all the time).
    2.  
    3. Error logs from SQL Server from which you can note the following:     
           
      1. Fully qualified domain name (FQDN) of the SQL Server machine or in case of clustered installations, the FQDN virtual name. If you are using a named instance, note down the instance name. (Note: You can search for: “Server name is” string to get this info in the errorlog).
      2.    
      3. Network libraries and ports the SQL instance is listening on
        Example messages:
        Named pipes: Server local connection provider is ready to accept connection on [ \\.\pipe\sql\query ].
        TCP/IP and port number: Server is listening on [ ::1 1433].
      4.   
    4.  
    5. Application and System event logs from SQL Server and Client systems.
    6.  
    7. If the connections are failing from an application, the connection string from the app. These are typically found in Web.config files for ASP.net applications.
      

    Checklist

      
       
    • Ensure SQL server is started and you see the following message in the SQL Server ErrorLog:
      SQL Server is now ready for client connections. This is an informational message; no user action is required.
    •  
    • Verify basic connectivity over IP address and check for any abnormalities:
      ping –a <SQL Server machine>, ping –a <SQL Server IP address>. If you notice any issues, work with your network administrator to fix the same. 
    •  
    • Check if SQL is listening on appropriate protocols by reviewing the ErrorLog.
    •  
    • Check if you are able to connect to SQL server using a UDL file – if it works, then there may be an issue with the connection string. For instructions on the procedure about UDL test, select the option "Connect to SQL server using a UDL file " at the bottom.
    •  
    • Check if you are able to connect to SQL Server from other client systems and different user logins– if you are able to, then the issue could be specific to the client or login that is experiencing the issue. Check the Windows event logs on problematic client for additional pointers. Also check if network drivers are up to date.
    •  
    • If you are experiencing login failures, ensure the user has a login at the server level and appropriate permissions to connect to the database that the user is trying to connect to.
      

    Now, you can select the issues you encountered to continue. 
     

      
      
       
        
         
          
           
            
             
              

    The 'A network-related or instance-specific error occurred while establishing a connection to SQL Server' error represents one or more of the following error messages:

              
               
    • A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
    •          
    • SQL Server Native Client Data Link Error
      [Microsoft SQL Server Native Client 10.0]: Login timeout expired
      [Microsoft SQL Server Native Client 10.0]: A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.
      [Microsoft SQL Server Native Client 10.0]: SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].
    •          
    • A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) (Microsoft SQL Server, Error: 10060)
    •          
    • A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error:40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error:53)
      The network path was not found
    •          
    • [Microsoft][SQL Server Native Client 11.0]TCP Provider: No connection could be made because the target machine actively refused it.
      [Microsoft][SQL Server Native Client 11.0]Login timeout expired
      [Microsoft][SQL Server Native Client 11.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. 
    •         
             
            
           
          
         
        
       
      

     


    Article Number:

    000176213


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles