This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
The following article provides detail about how to address potential issues you might encounter when connecting the Azure Database Migration Service (DMS) to your source database. Each section below relates to a specific type of source database, listing the error you might encounter together with detail and links to information about how to troubleshoot the connectivity.
Potential issues associated with connecting to a source SQL Server database and how to address them are provided in the following table.
| Error | Cause and troubleshooting detail |
|---|---|
| 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. | This error occurs if the service can't locate the source server. To address the issue, see Error connecting to source SQL Server when using dynamic port or named instance. |
| Error 53 - SQL connection failed. (Also, for error codes 1, 2, 5, 53, 233, 258, 1225, 11001) | This error occurs if the service can't connect to the source server. To address the issue, refer to the following resources, and then try again. Interactive user guide to troubleshoot the connectivity issue Prerequisites for migrating SQL Server to Azure SQL Database Prerequisites for migrating SQL Server to an Azure SQL Managed Instance |
| Error 18456 - Login failed. | This error occurs if the service can't connect to the source database using the provided T-SQL credentials. To address the issue, verify the entered credentials. You can also refer to MSSQLSERVER_18456 or to the troubleshooting documents listed in the note below this table, and then try again. |
| Malformed AccountName value '{0}' provided. Expected format for AccountName is DomainName\UserName | This error occurs if the user selects Windows authentication but provides the username in an invalid format. To address the issue, either provide username in the correct format for Windows authentication or select SQL Authentication. |
Potential issues associated with connecting to a source AWS RDS MySQL database and how to address them are provided in the following table.
| Error | Cause and troubleshooting detail |
|---|---|
| Error [2003][HY000] - connection failed. ERROR [HY000] [MySQL][ODBC x.x(w) driver] Cannot connect to MySQL server on '{server}' (10060) | This error occurs if the MySQL ODBC driver can't connect to the source server. To address the issue, refer to the troubleshooting documents listed in the note below this table, and then try again. |
| Error [2005][HY000] - connection failed. ERROR [HY000] [MySQL][ODBC x.x(w) driver] Unknown MySQL server host '{server}' | This error occurs if the service can't find the source host on RDS. The issue could either be because the listed source doesn't exist or there's a problem with RDS infrastructure. To address the issue, refer to the troubleshooting documents listed in the note below this table, and then try again. |
| Error [1045][HY000] - connection failed. ERROR [HY000] [MySQL][ODBC x.x(w) driver] Access denied for user '{user}'@'{server}' (using password: YES) | This error occurs if MySQL ODBC driver can't connect to the source server due to invalid credentials. Verify the credentials you have entered. If the issue continues, verify that source computer has the correct credentials. You might need to reset the password in the console. If you still encounter the issue, refer to the troubleshooting documents listed in the note below this table, and then try again. |
| Error [9002][HY000] - connection failed. ERROR [HY000] [MySQL][ODBC x.x(w) driver] The connection string might not be right. Visit portal for references. | This error occurs if the connection is failing due to an issue with the connection string. Verify the connection string provided is valid. To address the issue, refer to the troubleshooting documents listed in the note below this table, and then try again. |
| Error in binary logging. Variable binlog_format has value '{value}'. Please change it to 'row'. | This error occurs if there's an error in binary logging; the variable binlog_format has the wrong value. To address the issue, change the binlog_format in parameter group to 'ROW', and then reboot the instance. For more information, see to Binary Logging Options and Variables or AWS RDS MySQL Database Log Files documentation. |
For more information about troubleshooting issues related to connecting to a source AWS RDS MySQL database, see the following resources:
Potential issues associated with connecting to a source AWS RDS PostgreSQL database and how to address them are provided in the following table.
| Error | Cause and troubleshooting detail |
|---|---|
| Error [101][08001] - connection failed. ERROR [08001] timeout expired. | This error occurs if the Postgres driver can't connect to the source server. To address the issue, refer to the troubleshooting documents listed in the note below this table, and then try again. |
| Error: Parameter wal_level has value '{value}'. Please change it to 'logical' to allow replication. | This error occurs if the parameter wal_level has the wrong value. To address the issue, change the rds.logical_replication in parameter group to 1, and then reboot the instance. For more information, see to Pre-requisites for migrating to Azure PostgreSQL using DMS or PostgreSQL on Amazon RDS. |
For more information about troubleshooting issues related to connecting to a source AWS RDS PostgreSQL database, see the following resources:
Potential issues associated with connecting to a source AWS RDS SQL Server database and how to address them are provided in the following table.
| Error | Cause and troubleshooting detail |
|---|---|
| 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) | This error occurs if the service can't connect to the source server. To address the issue, refer to the troubleshooting documents listed in the note below this table, and then try again. |
| Error 18456 - Login failed. Login failed for user '{user}' | This error occurs if the service can't connect to the source database with the T-SQL credentials provided. To address the issue, verify the entered credentials. You can also refer to MSSQLSERVER_18456 or to the troubleshooting documents listed in the note below this table, and try again. |
| Error 87 - Connection string is not valid. 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: SQL Network Interfaces, error: 25 - Connection string is not valid) | This error occurs if the service can't connect to the source server because of an invalid connection string. To address the issue, verify the connection string provided. If the issue persists, refer to the troubleshooting documents listed in the note below this table, and then try again. |
| Error - Server certificate not trusted. A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.) | This error occurs if the certificate used isn't trusted. To address the issue, you need to find a certificate that can be trusted, and then enable it on the server. Alternatively, you can select the Trust Certificate option while connecting. Take this action only if you're familiar with the certificate used and you trust it. TLS connections that are encrypted using a self-signed certificate don't provide strong security -- they're susceptible to man-in-the-middle attacks. Don't rely on TLS using self-signed certificates in a production environment or on servers that are connected to the internet. For more information, see to Using SSL with a Microsoft SQL Server DB Instance or Tutorial: Migrate RDS SQL Server to Azure using DMS. |
| Error 300 - User does not have required permissions. VIEW SERVER STATE permission was denied on object '{server}', database '{database}' | This error occurs if user doesn't have permission to perform the migration. To address the issue, refer to GRANT Server Permissions - Transact-SQL or Tutorial: Migrate RDS SQL Server to Azure using DMS for more details. |
For more information about troubleshooting issues related to connecting to a source AWS RDS SQL Server, see the following resources:
Training
Module
Introduction to open-source database migration on Azure - Training
Introduction to open-source database migration on Azure
Certification
Microsoft Certified: Azure Database Administrator Associate - Certifications
Administer an SQL Server database infrastructure for cloud, on-premises and hybrid relational databases using the Microsoft PaaS relational database offerings.
Documentation
MSSQLSERVER_11001 - SQL Server
MSSQLSERVER_11001