Answered

SQL on premise connector to run stored procedure issue

(0) Share

Report

Posted on by IncursioML1

So I'm not sure what happened if this is Microsoft making updates, I set this up wrong, or something else is happening but at one point this worked.

We have an on premise SQL Server and I installed the gateway on my laptop to run a stored procedure in Power Automate. Works fine at that point. Now I was able to get access to a virtual machine, in which I also installed the gateway on that VM.

When I tried to set up the gateway connection on that VM - I set it up as a Windows Authentication but it seems to fail and now nothing is working. Is this something internally I should follow up with my SQL Server team, or is this something on Microsoft?

I'm pretty sure I got the connection correctly since I can login properly with SSMS and other apps.

Any ideas?

Categories:

Using connectors

I have the same question (0)

All responses (4)

Answers (1)

Sort by

eric-cheng 5,171 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @IncursioML1 ,

Have you tried deleting and recreating the connection?

What errors/if any are you getting?

Do you see the new data gateway under Date > Gateways?

--------------------------------------------------------------------------
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
IncursioML1 99 on at

Like
a
(0)

Report
Copy link

Link copied!

Yes I have to clean things up since I was making a bunch with bad parameters (my own fault).

Now that i do have some created, I see here that I installed the gateway in a VM but I can't adjust the setting in the 'Connections' it always utilizes the 'Cloud' instead of 'On Premise'. How do I actually change that connection to 'On Premise' in the 'Connections' tab of Power Automate?

Was this reply helpful? Yes No
eric-cheng 5,171 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @IncursioML1 ,

Is this when you are recreating the connection? If not, can you try recreating it?

--------------------------------------------------------------------------
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
Verified answer

IncursioML1 99 on at

Like
a
(0)

Report
Copy link

Link copied!

Ok it definitely was on our end - we changed the login instead of using 'UNIXNAME' we added this additional layer of 'COMPANYNAME\UNIXNAME' so I had to redo the 'Connection' login. Which I keep getting confused since the gateway is one thing, but the connection is another in which it attaches to a gateway. Once I updated the login and pointed the 'Connection' to the new gateway that was set up on the VM, I retested a power automate flow to run a stored procedure, that works. The real test now will be will that automated flow run at midnight tonight when I'm not working and the VM is still on.

I'll mark as answered, sorry for confusion.

Was this reply helpful? Yes No