We use Azure Databases to hold our data for our web app.
All of a sudden as of 8pm Central Time on 10/12/2021, I am seeing this error:
A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: SSL Provider, error: 0 - The wait operation timed out.) (Microsoft SQL Server, Error: 258)
We are seeing this via SQL Server Management Studio and also when I debug within VS 2019.
This doesn't appear to happen with everyone on our team.
Is anyone else seeing issues with Azure database service?
Ping the Azure SQL database server to get the current IP address of the server.
C:\>ping <myserver>.database.windows.net
Pinging data.sn1-1.database.windows.net [65.55.74.144] with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 65.55.74.144: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
Once you get the IP, run a tracert to find out on what hop the communication gets timed out or has noticeable latency.
C:\>tracert 65.55.74.144
Tracing route to 65.55.74.144 over a maximum of 30 hops
1 2 ms 1 ms 1 ms 192.168.0.1
2 6 ms 5 ms 5 ms 10.33.34.50
3 5 ms 4 ms 5 ms 4-1-753.DLLSTX-LCR-07.verizon-gni.net [130.81.107.26]
4 8 ms 5 ms 5 ms so-6-2-0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.28.208]
5 44 ms 43 ms 44 ms so-11-0-0-0.LCC1-RES-BB-RTR1-RE1.verizon-gni.net [130.81.17.40]
6 49 ms 44 ms 44 ms so-6-0-0-0.ASH-PEER-RTR1-re1.verizon-gni.net [130.81.10.90]
Sometimes you experience this when you are trying to get connected to SQL Azure using a VPN software on the corporate network, but when you get connected from home you are fine.
It appears that this issue was due to my home network ISP.
I assume the ISP accidently changed a setting for port 1433. I called the ISP, they reconfigured my modem, I rebooted and it still didn't work.
Then about 30 minutes to 45 minutes later, it started working perfect, without any issues within my local debug session in VS 2019 OR with trying to access the Azure database via SSMS.
We also had another developer that was seeing the same issue and he had the same ISP provider since he lives about 15 minutes from me.
All other developers were working fine because they had different ISPs
Related
I keep getting the following error:
the timeout period elapsed prior to obtaining a connection from the pool
I have the database on 3 servers, 2 servers are working fine, locally is fine too.
However, on the production server, if i try to access any API i get this error.
I dont think its something related to my query, how can i fix this ?
Kindly check the port for accessing the sql connection from your production api hosted servers to database hosted server. Might be port issue.
We have a .Net ASMX webservice hosted in IIS on an Azure VM. We are retriving some data from Azure SQL datawarehouse in the webservice. We have configured the following connection string in the web.config file.
add key="connectionString" value="Driver={ODBC Driver 13 for SQL Server};Server=;Database=;Uid=;Pwd=;Encrypt=yes;TrustServerCertificate=no;Min Pool Size=0;Max Pool Size=500; Pooling=true;Connection Timeout=10800"/
We tried to do a POC and made consecutive 200 calls to the webservice. In the webservice webmethod we are just opening the connections. However after just 55 to 60 calls we start getting exception : Connection timed out.
My question is why are we getting the connection timeout after just 55 calls when we have set the Max Pool Size value to 500 in connections string.
Is there any other setting I need to change to make it work for atleast 500 connections?
Azure SQL Datawarehouse is Gen2: DW1000c
I have a dotnet exe app in a server which runs in sql server. during the factory production time my application were unable to connect to db for 1 to 2 minutes and then it gains connectivity at this unresponsive time when i accessed sql server management studio, i got the below error:
Taken from the answer over here.
This usually happens when there are too many open transactions that are blocking read access to your database server. You can try restart your server which will usually solve the issue.
I've been trying for a few days to work out what's wrong with connecting to our SAP server from a workstation installed with a client.
My setup:
server:
Win 2008 R2
SQL Server 2008 R2
SAP B1 8.82 PL 14
Workstation:
Win 7 64bit
SQL Native Client 2008 R2 (same as on the server as recommended)
Situation:
I can see the companies\DBs from the client side but when I enter the right credentials it stalls for a few seconds then throws out the dreaded "Internal Error 1102 131-183".
Firewall has been completely turned off.
Communication is working perfectly fine on all ports.
I made sure both TCPIP and Piping have been enabled on CLICONFG.
When using Process Monitor I noticed 2 missing keys the SAP Business One.exe attempts to access but fails as they do not exist:
HKLM\SOFTWARE\Wow6432Node\SAP\SAP Manage
HKLM\SOFTWARE\Wow6432Node\Microsoft\CTF\KnownClasses
I have no idea where to get them from...
I'd appreciate all help I can get.
Thanks
SQL Server Management Studio is not connecting on my database server machine at production server.
Whereas production sites accessing database. When I tried to connect database from SSMS, I get this error:
Cannot connect to 111.11.11.11.
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)
I was using this SSMS last couple of years,n this SSMS is running fine since more then year on production database server n i didn't closed ever, now when i connecting this SSMS but facing this issue, whereas my sites which accessing this database is working fine.
I also tried to access database from sqlcmd but no luck n facing facing this error:
HResult 0x35, Level 16, State 1
Named Pipes Provider: Could not open a connection to SQL Server [53].
Sqlcmd: Error: 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..
I thinks we resolved the issues.
1. Active Directory server was not behaving, so
2. SQL server couldn't run without credentials and
3. they found another SQL server issue and fixed it.
We started looking into the SQL connections that my team had found and it lead us to find that the Active Directory server had basically crashed. It was allowing us to log in however it wasn't able to access the majority of the AD functionality. We ended up rebooting the AD server which corrected the issue however we were still seeing issues with the SQL cluster manager and SQL itself was rejecting connections on a somewhat regular basis.
After the AD server was rebooted we were able to log into the SQL cluster manager but with limited capabilities, since it had been erroring due to the AD issue we restarted the cluster service to see if this would correct the issue. This caused the SQL service to fail over to the passive server and caused SQL to start rejecting even more connections than it had been. The cluster service started working with this restart however the SQL connections were getting worse. We found that the IPv6 protocol was enabled for the SQL service which causes problems, like the ones we were seeing, in SQL clusters, to disable this we had to reboot the 2 SQL servers. We rebooted them one at a time and once they were back up everything was working properly.