ODBC error - trying again (1 Viewer)

[CedarTree]

Sorry to post again but just checking if someone else has run into this... I have linked tables via ODBC. The connection works fine for 10 to 15 mins, then randomly shuts down. Once I click "cancel" on the error, the coding picks right back up again (doing a batch process). IT has tried fixing TLS settings, etc. No luck so far.

---------------------------
Microsoft SQL Server Login
---------------------------
Connection failed:
SQLState: '08001'
SQL Server Error: 10054
[Microsoft][SQL Server Native Client 11.0]TCP Provider: An existing connection was forcibly closed by the remote host.

Connection failed:
SQLState: '08001'
SQL Server Error: 10054
[Microsoft][SQL Server Native Client 11.0]Client unable to establish connection

 

[CedarTree]

BTW, when the error hits, if I just CONTINUE (F5) the VBA, it keeps working! Infuriating!

 

[PeterF]

How are you connected to the server, wired or Wifi?
If the network connection temporarily disconnects error 10054 can happen.
Microsoft support article on error 10054

 

[CedarTree]

I'm using a remote server so that shouldn't be an issue since the remote server and the SQL server are all on the same Company network. Also, I tried a "keep alive" subroutine that runs every 5 records... to reconnect one of the ODBC tables. Still not helping.

 

[GPGeorge]

Sorry to post again but just checking if someone else has run into this... I have linked tables via ODBC. The connection works fine for 10 to 15 mins, then randomly shuts down. Once I click "cancel" on the error, the coding picks right back up again (doing a batch process). IT has tried fixing TLS settings, etc. No luck so far.

---------------------------
Microsoft SQL Server Login
---------------------------
Connection failed:
SQLState: '08001'
SQL Server Error: 10054
[Microsoft][SQL Server Native Client 11.0]TCP Provider: An existing connection was forcibly closed by the remote host.

Connection failed:
SQLState: '08001'
SQL Server Error: 10054
[Microsoft][SQL Server Native Client 11.0]Client unable to establish connection

"An existing connection was forcibly closed by the remote host."

That sounds like a timeout on the connection itself. Have IT check into that.

 

[CedarTree]

I hear you - IT is still trying but no luck so far. Ugh.

 

[CedarTree]

Is it possible that running Access 2016 is part of the issue? If I update to say Access 2019 on the terminal server, that might lessen the issue?