EventStream - SQL Server on VM DB (CDC)

[Karthikpv]

I am facing this issue while trying to connect to a SQL server on EventStream,
Error:

Property 'username's value '' is invalid.
What's the solution?

[Anonymous]

Hi @Karthikpv,

Thanks for reaching out to the Microsoft fabric community forum.

Since you've already went through the steps provided by @burakkaragoz and also verified the SQL login works in SSMS and CDC is properly configured. 

If none of the above help, at this point it may be worth opening a support ticket with Microsoft. You can reach out to Microsoft Support by raising a ticket with Microsoft Support.

Please refer below link on how to raise a contact support or support ticket.
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

I would also take a moment to thank @burakkaragoz, for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.

If I misunderstand your needs or you still have problems on it, please feel free to let us know.  

Best Regards,
Hammad.

[Anonymous]

Hi @Karthikpv,

I wanted to follow up on our previous conversation. Has your issue been resolved or were you able to raise a support ticket with Microsoft Fabric Support?

Your feedback would be greatly appreciated, as it can help us better understand and address similar issues in the community.

Thank you.

[burakkaragoz]

Hi @Karthikpv ,

Ah, this is a classic "empty field" error. You're probably leaving the username box blank when setting up the EventStream connection.

What's likely happening: EventStream is expecting SQL Server authentication (username/password), but you've left the username field empty. It won't accept Windows authentication for CDC connections.

Quick fix:

• Create a proper SQL login on your SQL Server instance
• Use that login's username (not a Windows domain account)
• Make sure the login has db_owner permissions on the database

CDC-specific gotchas: Your SQL user needs special permissions because CDC is picky. The account needs to read change data, and that requires elevated permissions. Also, make sure:

• CDC is actually enabled on your database AND the specific tables
• SQL Server Agent is running (CDC breaks without it)
• Your SQL Server allows mixed authentication mode

If you're still stuck: Try connecting with SQL Server Management Studio first using the same credentials. If that works but EventStream doesn't, it's probably a permissions issue rather than a connection problem.

What type of authentication were you trying to use? And have you verified CDC is properly set up on the SQL Server side?

---

If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.
This response was assisted by AI for translation and formatting purposes.

[Karthikpv]

Hi @burakkaragoz 

I have created a login on SQL server and tested it in SSMS. Also i have given the db_owner permission to the login , enabled mixed authentication , have enabled CDC for the db and the tables and verified it , the connections and gateway are online , still i am facing this issue

[burakkaragoz]

@Karthikpv ,

Hmm, that's weird if you've got the SQL login working in SSMS but EventStream is still complaining about an empty username.

A few things to double-check:

In the EventStream connection setup:

• Are you definitely typing the username in the right field? Sometimes there are multiple auth sections
• Try the username without any domain prefix (just sqluser, not domain\sqluser)
• Make sure there are no trailing spaces in the username field

Gateway-related issues: Since you mentioned the gateway is online, this might be a gateway configuration problem:

• Is the gateway service running under an account that can reach your SQL Server?
• Try testing the connection directly on the gateway machine
• Check if there are any firewall rules blocking the gateway from reaching SQL Server

EventStream-specific quirks:

• What's the exact format you're using for the server name? Try both servername\instance and servername,port formats
• Is your SQL Server instance named or default? Named instances can be tricky with EventStream

Debug step: Try creating a simple data flow (not EventStream) to the same SQL Server first. If that works, then it's definitely an EventStream-specific issue.

Can you share the exact server name format you're using and whether it's a named instance? That might help narrow down the issue.

This response was assisted by AI for translation and formatting purposes.