SQl server is not connecting.

Question

SQl server is not connecting.

Vishakhan K 10

Hi Team,

We are facing an issue with SQL Server connectivity.

We hosted windows SQL 2022 Server in Azure. and every 30 days the connection to the Database is crashing and getting this below error message.

Can anybody help on this issue?

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 - The wait operation timed out.) (Framework Microsoft SqlClient Data Provider)

Error Number: 258

Severity: 20

State: 0

NIKHILA NETHIKUNTA 4,690 Reputation points Microsoft External Staff

2024-11-05T06:35:56.7866667+00:00

Duplicate thread: https://learn.microsoft.com/en-us/answers/questions/2115495/sql-2022-connection-from-ssms-is-timed-out-every-3

2 answers

Your answer

NIKHILA NETHIKUNTA 4,690 Reputation points Microsoft External Staff

2024-11-05T06:35:56.7866667+00:00

Duplicate thread: https://learn.microsoft.com/en-us/answers/questions/2115495/sql-2022-connection-from-ssms-is-timed-out-every-3

Answer 1

LiHongMSFT-4306 31,621

Hi @Vishakhan K

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible.

You may start up with this doc which provides some steps to help you troubleshoot this error.

A network-related or instance-specific error occurred while establishing a connection to SQL Server.

Best regards,

Cosmog

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".

Vishakhan K 10 Reputation points

2024-11-05T06:56:43.2733333+00:00
Hi @LiHongMSFT-4306

We have already tried so many troubleshooting includes the steps which you shared in the link.

But only after server reboot the connection is restoring.

these troubleshooting steps we followed in the downtime window

The connection was rejecting when we connect via SSMS or application.

Telnet connection to the SQL server (Port 4575) was successful

During that time server resources are very minimal utilized.

We have verified the event and other, we haven’t noticed any events related with this issue.

We tested the server dynamic port utilization that also minimal.

We have restarted the SQL services; however, the issue hasn’t resolved.

Still now we couldn’t identify the exact issue -however we have done the below setting changes

We upgraded the SQL version from 16.0.4120.1 to latest stable build 16.0.4140.3

Create a service account for SQL services
NIKHILA NETHIKUNTA 4,690 Reputation points Microsoft External Staff

2024-11-07T07:25:08.7266667+00:00

Hi @Vishakhan K
I agree that this issue looks strange and I wasn't able to reproduce this issue. If you have a support plan could you please file a support ticket for deeper investigation and do share the SR# with us? In case if you don't have a support plan please let us know here.
NIKHILA NETHIKUNTA 4,690 Reputation points Microsoft External Staff

2024-11-08T15:57:27.5133333+00:00

Hi @Vishakhan K
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Answer 2

Olaf Helper 47,616

The error message is raised by the client component itself, not by SQL Server.

Could be anything network related, like a busy switch/router, hickup at your IPS or maybe Azure.

You have to monitor your network + related components for troubleshooting.

0 comments

Share via

SQl server is not connecting.

2 answers

Your answer