Linkedin

  • Home >
  • Resolve connection errors after migrating Microsoft SQL Server to the AWS Cloud

Resolve connection errors after migrating Microsoft SQL Server to the AWS Cloud

Project Overview

Project Detail

After you migrate Microsoft SQL Server running on Windows Server 2008 R2, 2012, or 2012 R2 to Amazon Elastic Compute Cloud (Amazon EC2) instances on the Amazon Web Services (AWS) Cloud, the connection to SQL Server fails and the following errors appear: 

  • [Microsoft][ODBC SQL Server Driver][DBNETLIB] General Network error

  • ERROR [08S01] [Microsoft][SQL Native Client]Communication link failure. System.Data.SqlClient.SqlException: 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.)

  • TCP Provider: The semaphore timeout period has expired

This pattern describes how you can resolve these errors by turning off the Windows Scalable Networking Pack (SNP) features at the operating system (OS) and network interface level for SQL Server running on Windows Server 2008 R2, 2012, or 2012 R2.

https://docs.aws.amazon.com/prescriptive-guidance/latest/patterns/resolve-connection-errors-after-migrating-microsoft-sql-server-to-the-aws-cloud.html?did=pg_card&trk=pg_card

To know more about this project connect with us

Resolve connection errors after migrating Microsoft SQL Server to the AWS Cloud