Power Automate gateway to SQL - Credentials are missing or not valid

(0) Share

Report

Posted on by Jorge_

Hi,

We have installed a data gateway in a SQL server.

However, when I try to login with credentials (that works in the server using SSMS) it shows me

Credentials are missing or not valid. inner exception: The credentials provided for the SQL source are invalid

Are there any extra steps need to be done in the SQL server t allow connections from Power Automate? (as opening ports?)

Screenshot 2021-10-04 113502.png

Categories:

Using connectors

I have the same question (0)

All responses (3)

Answers (1)

eric-cheng 5,171 on at

Like (1)

Report

Hi @Jorge ,

Can you try / test / clarify the below:

1. Ensure the correct Authentication Type is used i.e. AAD, SQL Auth, Windows Auth
2. Is MTR the username or servername?
3. If servername, can you try removing the LO-ROPO\

Also, please check the usual checklist:

1. Please make sure your database engine is configured to accept remote connections.
2. Please make sure that you create an exception on the firewall for the SQL Server instance and port you are using.
3. Please check if your SQL server services is up and running properly.
4. Please make sure that you enable TCP/IP in SQL Server Configuration

--------------------------------------------------------------------------
If I have answered your question, please mark my post as a solution
If you have found my response helpful, please give it a thumbs up

Connect on LinkedIn

Was this reply helpful? Yes No
Jorge_ on at

Like (0)

Report
Hi Eric, thanks for your reply.
I'm using SQL Auth, as I do use in SSMS in the server.
LO-ROPO\MTR is the server name If I remove any of two parts, I get following:

Firewall exception is not created automatically? How do I know which port uses Power Automate to access SQL on-prem?
Thanks

Was this reply helpful? Yes No
Verified answer

eric-cheng 5,171 on at

Like (1)

Report

Hi @Jorge ,

So I did a bit of testing against my on prem SQL.

1. I had to specify the domain in my SQL server e.g. servername.xxxx.com.au. Not sure if this is specific to my network.

2. Database name was case sensitive. I had a capital as the first character and it threw the same error.

--------------------------------------------------------------------------
If I have answered your question, please mark my post as a solution
If you have found my response helpful, please give it a thumbs up

Connect on LinkedIn

Was this reply helpful? Yes No