Windows Server 2003 - why a network-related or instance-specific error occurs and ways to fix it

Question

Windows Server 2003 - why a network-related or instance-specific error occurs and ways to fix it

JK Kwak 1

Hi, my web server (MS Windows Server 2003, Standard Edition SP2) connecting to an MS SQL server (Windows Server 2008 R2 Standard) for an application is encountering from a few months ago an error message of " 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) " intermittently. Since it's been running with no such errer, I just fastened cable connections and changed switch box to a new one but still occurs. When it occurs it lasts only a few seconds or minutes. Pls experts here help me fix this error.

Thanks,
Jockey

Shashank Singh 6,251 Reputation points

2021-01-11T14:41:49.443+00:00

I guess network is culprit here. Do you have other relevant logs from application server which can give more idea about your issue
JK Kwak 1 Reputation point

2021-01-12T06:16:28.72+00:00

Hi, Singh

The known error mjessage is always followed by:
55614-additional-information.txt

My application running on the web server is Text Messaging Systems, receiving text messages from external customer and relays them to mobile network operators who then deliver to end customers' mobile phones.

Thanks, Jockey
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2021-01-12T22:26:02.943+00:00

That's just a stack dump from your client application and of no interest. It could be relevant to check out the SQL Server errorlog to see if there is anything that coincides in time with these connection issues.

may virus or malwares cause the server getting busy?

If it would be that bad, you would see more than just transient issues. But, hey, it could be anti-malware software that is the problem. I have a recollection of seeing an SQL instance complete crawling because McAfee (or whatever it was) felt obliged to scan the machine. However, since your issue only lasted minutes, I don't think this is the likely explanation.

3 answers

Your answer

Shashank Singh 6,251 Reputation points

2021-01-11T14:41:49.443+00:00

I guess network is culprit here. Do you have other relevant logs from application server which can give more idea about your issue
JK Kwak 1 Reputation point

2021-01-12T06:16:28.72+00:00

Hi, Singh

The known error mjessage is always followed by:
55614-additional-information.txt

My application running on the web server is Text Messaging Systems, receiving text messages from external customer and relays them to mobile network operators who then deliver to end customers' mobile phones.

Thanks, Jockey
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2021-01-12T22:26:02.943+00:00

That's just a stack dump from your client application and of no interest. It could be relevant to check out the SQL Server errorlog to see if there is anything that coincides in time with these connection issues.

may virus or malwares cause the server getting busy?

If it would be that bad, you would see more than just transient issues. But, hey, it could be anti-malware software that is the problem. I have a recollection of seeing an SQL instance complete crawling because McAfee (or whatever it was) felt obliged to scan the machine. However, since your issue only lasted minutes, I don't think this is the likely explanation.

Answer 1

Tom Phillips 17,771

That is a generic "could not connect to server" message and does not help diagnose the true problem in any way.

Since this is an intermittent issue, it is likely you have a network problem or the SQL Server is too busy to respond to the login request. You would have to look at the server when it is happening.

I would start here:
https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/troubleshoot-connecting-to-the-sql-server-database-engine?view=sql-server-ver15#testing-a-local-connection

Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2021-01-11T23:03:24+00:00

That is a generic "could not connect to server" message and does not help diagnose the true problem in any way.

Just to clarify, it means that the server was not even reached. So connection is not failing because of permissions or whatever. And, yes, is likely to be due to some network/DNS issue. Although, I think have heard of conditions where SQL Server has been so tanked with work, that it has not responded in time, and this was something that happened with older versions like SQL 2008 R2.

What does "SELECT @@version" report?
JK Kwak 1 Reputation point

2021-01-12T07:00:56.03+00:00

may virus or malwares cause the server getting busy?
thanks, Jockey
JK Kwak 1 Reputation point

2021-01-13T08:59:12.397+00:00

Hereunder is what the sql said:

Microsoft SQL Server 2012 - 11.0.2100.60 (X64)
Feb 10 2012 19:39:15
Copyright (c) Microsoft Corporation
Developer Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)

Thanks for your help.
Jockey
Tom Phillips 17,771 Reputation points

2021-01-13T13:44:08.09+00:00

You are running the RTM version of SQL 2012. I highly suggest you upgrade to the last version.

https://support.microsoft.com/en-us/help/4018073/kb4018073-sql-server-2012-service-pack-4-release-information
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2021-01-13T22:14:03.953+00:00

Small nit-pick: It's actually SQL 2012, SP1. Whatever, it is seriously out of date. Apply SP4 before anything else. No guarantees that it resolves the issue, but it could be.
CathyJi-MSFT 22,396 Reputation points Microsoft External Staff

2021-01-14T08:02:30.867+00:00

Hi @JK Kwak ,

Did apply SP4 for SQL 2012 could resolve your issue? If not, still suggest you check your network.

Answer 2

Hi @JK Kwak ,

> When it occurs it lasts only a few seconds or minutes.

SQL server connection failed intermittently, the issues may be caused by your network. Suggest you ask help for your network colleague to check your network. Or using network process monitor to capture the network package and analysis the files.

Best regards,
Cathy

If the response is helpful, please click "Accept Answer" and upvote it, thank you.
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.

Answer 3

Thin Thuzar Oo 5

Untitled

When you connect using Microsoft Management Studio, please type the port no 1433.

Try Telnet command for 1433 also. In cmd.exe, type this command to check whether port 1433 is on : Telnet IPaddress or PC name 1433 (eg: Telnet 192.168.1.160 1433).

If cmd shows black screen, the port is opening.

please turn on Telnet Client in Win10 using Windows features on or off in Control panel.

Share via

Windows Server 2003 - why a network-related or instance-specific error occurs and ways to fix it

3 answers

Your answer