Unable to connect to source server in azure database migration service

Bellam Manoj 1

I am unable to connect to source server in azure migration service. I am doing a POC for migrating SQL Server database to azure sql MI using the Azure database Migration Service.

But when I create the New Migration Project and specify the source instance it gives me an error,

Error 53 - SQL connection failed.

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) The network path was not found

The SQL server is on my local machine itself.

SwathiDhanwada-MSFT 17,726 Reputation points

2021-04-07T08:58:10.073+00:00

@Bellam Manoj Welcome to Microsoft Q&A platform and thanks for your query. Before starting the migration process, there are few prerequisites that needs to be adhered. This article documents the prerequisites to ensure Azure Database Migration Service runs smoothly when performing database migrations. Kindly check if the prerequisites are met and revert if you still face the issue.
Bellam Manoj 1 Reputation point

2021-04-13T08:21:50.147+00:00

in windows firewall inbound and outbound rules i added tcp port 1433 to access the source database.
still i'm getting the same error.

please help

{ "resourceId":"/subscriptions/4424f888-90c5-4da5-ada8-c7a392adfdd8/resourceGroups/SQLWorkshop/providers/Microsoft.DataMigration/services/sqlmi-migration", "errorType":"Failed to connect, please check error details", "errorDetail":"Error 53 - SQL connection failed.Please use this interactive user guide to troubleshoot the connectivity issue: https://support.microsoft.com/en-us/help/4009936/solving-connectivity-errors-to-sql-server 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)The network path was not found" }
Bellam Manoj 1 Reputation point

2021-04-13T08:22:37.643+00:00

i configured the same which is shown here also

https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/enable-or-disable-a-server-network-protocol?view=sql-server-ver15#SSMSProcedure
Bellam Manoj 1 Reputation point

2021-04-13T08:24:31.453+00:00

in azure database migration service source iam giving my local ip address and authentication selected sql authentication.
Raj Pochiraju 6 Reputation points Microsoft Employee

2021-04-13T13:44:57.473+00:00

More detailed MI migration requirements provided below. Please let us know if you still run into any issues
https://learn.microsoft.com/en-us/azure/dms/resource-network-topologies
Raj Pochiraju 6 Reputation points Microsoft Employee

2021-04-13T13:46:02.183+00:00

The detailed Azure SQL MI migrations using DMS service are documented here, https://learn.microsoft.com/en-us/azure/dms/resource-network-topologies

1 answer

KalyanChanumolu-MSFT 8,316 Reputation points

2021-04-28T09:39:59.013+00:00

@Bellam Manoj Apologies for the delayed response.

If you are still not able to resolve the connectivity issue with Azure Database Migration Service, there are alternative methods you could consider for moving your on-premises SQL Server to Managed Instance. Like Backup and restore, Import Export Wizard/BACPAC etc

More details are here

Please let us know if you have further questions.

----------

If an answer is helpful, please "Accept answer" or "Up-Vote" which might help other community members reading this thread.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment