Solved

CData Sync error when creating a source connection to SQL Server

Forum|Forum|1 year ago
September 10, 2024
3 replies
312 views

ella.evio
Apprentice

I’m encountering an error in CData Sync when I try to create and test a source connection. The complete error message is Connection open failed: [500] Failed to login 'SERVERNAME', Cannot open database 'DBNAME' requested by the login. The login failed. Login failed for user ‘user’.

What is the requirement for the SQL server so that CData can establish a connection? Also, are there any logs in CData we can check that has more details about the error?

The documentation does not say anything required from the source other than the server and login credentials.

Best answer by Luçjano Capo

Hi @ella.evio,

Thank you for reaching out.

Firstly, I would suggest confirming the credentials for User and Password are correct, and please ensure that the user has read/write permissions for the data source. Your Database Administrator should be able to confirm that the user has these correct permissions. You can additionally try to connect using the admin user (sa).

Another thing to keep in mind is to enable the TCP/IP protocol for the server instance by going to SQL Server Configuration Manager, and under SQL Server Network Configurations locate your SQL Server and enable the TCP/IP:

Make sure the server and database name you are trying to connect is correctly spelled.

And you will be able to successfully connect to your SQL Server instance.

If any issues occur, please reach out to [email protected]

This topic has been closed for replies.

Luçjano Capo
Employee
Answer
Forum|Forum|1 year ago
September 10, 2024

Hi @ella.evio,

Thank you for reaching out.

Firstly, I would suggest confirming the credentials for User and Password are correct, and please ensure that the user has read/write permissions for the data source. Your Database Administrator should be able to confirm that the user has these correct permissions. You can additionally try to connect using the admin user (sa).

Another thing to keep in mind is to enable the TCP/IP protocol for the server instance by going to SQL Server Configuration Manager, and under SQL Server Network Configurations locate your SQL Server and enable the TCP/IP:

Make sure the server and database name you are trying to connect is correctly spelled.

And you will be able to successfully connect to your SQL Server instance.

If any issues occur, please reach out to [email protected]

Like

E

ella.evio
Author
Apprentice
Forum|Forum|1 year ago
September 10, 2024

Thank you @Luçjano Capo for the prompt and detailed response. The connection was established when the source (from another team) gave a different database name. I’m guessing the cause is a wrong db name. Thanks for your help anyway!