SQL Server Error Msg 10054, Level 20, State 0, Line 0

-

Msg 10054, Level 20, State 0, Line 0

A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)



Some possible causes are as below

  1. The server has been restarted, this will close the existing connections.
  2. Someone has killed the SPID that is being used.
  3. Network Failure
  4. SQL Services restarted

RESOLUTION: Just hit F5 or (ALT + X) to re-run your query. SSMS will determine it is no longer connected and then prompt you to reconnect it will put you back into the same database.

Otherwise reconnect to SSMS and re execute the query.

Comments

Post a Comment

Popular posts from this blog

Failed to execute the package or element. Build errors were encountered

-
Error: TITLE: Microsoft Visual Studio ------------------------------ Failed to execute the package or element.   Build errors were encountered. For more information, see the Output window. ------------------------------ BUTTONS: OK ------------------------------   Solution: We tried to close SSDT and run it again but, we still got the same error while running SSIS package. Then, we need to follow bellow solution: Step 1: Go to Task Manager–> Details Tab. Step 2: Locate the process “ DtsDebugHost.exe “. Kill this process. There might be multiple instances of this process. Kill all of them. Step 3: Rerun SSIS package
Read more

Restore of database 'DataBase_Name' failed. (Microsoft.SqlServer.Management.RelationalEngineTasks)

-
TITLE: Microsoft SQL Server Management Studio ------------------------------ Restore of database 'DataBase_Name' failed. (Microsoft.SqlServer.Management.RelationalEngineTasks) ------------------------------ ADDITIONAL INFORMATION: System.Data.SqlClient.SqlError: Exclusive access could not be obtained because the database is in use. (Microsoft.SqlServer.SmoExtended) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=12.0.2000.8+((SQL14_RTM).140220-1752)&LinkId=20476 ------------------------------ BUTTONS: OK ------------------------------ Procedure 1: 1. Right click Databases 2. Restore Database... 3. [General] Source from Device, select the bak file 4. [General] Change the Destination database name to a new name 5. [Files] Change mdf and ldf Restore As paths to a different, new path 6. [Options] (unnecessary on the other computer) Check Overwrite the existing database (WITH_REPLACE) 7. [Options] (unnecessary on the other computer) Chec...
Read more

On-premises data gateway December release

-
We are happy to announce that we have just released the December update for the on-premises data gateway (version 3000.154.3). This update brings the on-premises data gateway up to date with the December release of Power BI Desktop. Download:  On-premises data gateway December release This version of the gateway will ensure that the reports that you publish to the Power BI Service and refresh via the gateway will go through the same query execution logic/run-time as in the December version of Power BI Desktop.
Read more