cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Impactful Individual
Impactful Individual

SQL execute stored procedure V2 no permission for connector

Hi everyone, 

I have an issue since yesterday with calling a sql stored procedure in my flow.

I can find the stored procedure and fill in the input parameter fields, but when I try to run it it doesn't seem to have permission to run and gives next error:

Capture.PNG

It says that caller has no permission to the connection, but running other stored procedures under the same connections do work perfectly. Also tried recreating the stored procedure but with the same error. 

Someone knows how to fix this? Help is much appreciated.

Thanks,

Ski

1 ACCEPTED SOLUTION

Accepted Solutions
Impactful Individual
Impactful Individual

Hi @manuelstgomes 

Thanks very much for your reply. The stored procedure was created by the same user, as well was the permission the same for the other stored procedures.

I managed to solved it by adding a new connection with the same credentials. So I guess it had something to do with the connection, only it's weird that it did work for other stored procedures.

Kind regards,

Ski

View solution in original post

3 REPLIES 3
Super User II
Super User II

HI @SkiDK 

 

Was this procedure created by a different person from the others that are working? You may have permission to execute but be able to see them.

 

Can you please check what's different, permissions wise, on this specific procedure so that we can try to figure this out?

 

Just to try please grant "Execute" permissions on that object:

https://docs.microsoft.com/en-us/sql/relational-databases/stored-procedures/grant-permissions-on-a-s...

 

If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

Cheers
Manuel

Impactful Individual
Impactful Individual

Hi @manuelstgomes 

Thanks very much for your reply. The stored procedure was created by the same user, as well was the permission the same for the other stored procedures.

I managed to solved it by adding a new connection with the same credentials. So I guess it had something to do with the connection, only it's weird that it did work for other stored procedures.

Kind regards,

Ski

View solution in original post

Hi @SkiDK 


Probably the connection was somehow different from the others, but I'm glad the issue is fixed.

 

Well done!

 

If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

Cheers
Manuel

Helpful resources

Announcements
PP Bootcamp Carousel

Global Power Platform Bootcamp

Dive into the Power Platform stack with hands-on sessions and labs, virtually delivered to you by experts and community leaders.

secondImage

Power Platform Community Conference On Demand

Watch Nick Doelman's session from the 2020 Power Platform Community Conference on demand!

MPA Community Blog

Power Automate Community Blog

Check out the community blog page where you can find valuable learning material from community and product team members!

Users online (19,376)