Error Microsoft SQL server connector 3:1466 Execute failed: network error Io exception : connect ion refused no future information

Anandhswarupp 85 Reputation points
2024-07-18T11:50:04.3366667+00:00

I have verified the connections on SQL server all are good but throwing mentioned error . Error Microsoft SQL server connector 3:1466

Execute failed: network error Io exception : connect ion refused no future information

I am able to connect SQL server on vm not in connected with local machine with same credentials . Please respond as soon as possible

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
13,948 questions
{count} votes

Accepted answer
  1. Zahid Butt 956 Reputation points
    2024-07-18T17:54:08.3066667+00:00

    Hi,

    Here is what I got from Copilot (may help you to narrow down):

    The error message “Microsoft SQL Server Connector 3:1466” indicates an issue related to the SQL Server Connector for Microsoft Azure Key Vault. Here are some steps you can take to troubleshoot this error:

     

    1. Upgrade the SQL Server Connector:

    Stop the SQL Server service using SQL Server Configuration Manager.

    Uninstall the old version of the connector from Control Panel > Programs and Features.

    Install (upgrade to) the new version of the SQL Server Connector for Microsoft Azure Key Vault.

    Start the SQL Server service.

    Test if the encrypted databases are accessible.

    If needed, you can roll back to the old version by following similar steps.

     

    2. Check Event Logs:

    Starting with version 1.0.3.0, the SQL Server Connector reports relevant error messages to the Windows event logs. Check the event logs for any additional details on the error.

     

    3. Verify Compatibility:

    Ensure that the SQL Server Connector version is compatible with your SQL Server instance. Some older versions are no longer supported in production environments1.

     

    Remember to consult the official documentation or seek further assistance if needed. Troubleshooting SQL Server errors can be complex, but these steps should help you get started!

    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. LucyChenMSFT-4874 5,060 Reputation points
    2024-07-19T02:05:02.84+00:00

    Hi @Anandhswarupp ,

    Thank you for your reaching out and welcome to Microsoft Q&A!

    As Erland says, the error message is rare, it seems like a connection issue. However, you mentioned that you are able to connect SQL server on VM not in connected with local machine with same credentials. What were you doing when this error message prompted?

    Could you please provide more information in detail to help us narrow down the issue? Such as your operation and your settings, etc.

    In addition, please make sure the configuration below:

    • Please ensure that you are using the correct servername/IP to Discover the MSSQL server.
    • Check if TCP/IP is configured on the SQL Server.
    • Ensure that the 1433 port is open.
    • Enable the SQL Server Browser Service.

    It may also the problem that the JDBC driver is not compatible with your SQL Server. As such we highly recommend that you work with the latest version of Microsoft JDBC driver.

    Thanks for your understanding. Your time and cooperation are much valued by us. We are looking forward to hearing from you to assist further.

    Best regards,

    Lucy Chen


    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our Documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    https://docs.microsoft.com/en-us/answers/support/email-notifications

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.