cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
Resident Rockstar
Resident Rockstar

New SQL Actions failing! Connection/on-prem problem?? "The key didn't match any rows in the table"

Just  noticed this today.  Its not new for me to crate actions to this SQL database via this connector.  I get this:

 

{
"status": 400,
"message": "The key didn't match any rows in the table.\r\n inner exception: The key didn't match any rows in the table.\r\nclientRequestId: eaa27222-3569-42bd-ac21-0091761aaf27",
"source": "sql-eus.azconn-eus.p.azurewebsites.net"
}
 
Steps taken to resolve (all of which yeild same result):
  1. Created a new connection
  2. Deleted and re-created the action
  3. "Save-As" to a new flow
  4. Created the flow again from nothing (twice)  
1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Resident Rockstar
Resident Rockstar

Re: New SQL Actions failing! Connection/on-prem problem?? "The key didn't match any rows in the table"

Ok, this is what fixed it...  

 

  1. I had to test the flow, but selected "I'll Perform the trigger action

    image.png
  2. Then, pick "edit connections"

    image.png
  3. Then, I re-selected the connection... even though it was already correct and "green"
    image.png

  4. The flow then ran correctly.  I repeated this procedure on another of my failed trials, and it worked.  Selecting the connection from the action itself did NOT resolve the issue!

 

Sorry MS, I get credit for this one...

View solution in original post

4 REPLIES 4
Highlighted
Resident Rockstar
Resident Rockstar

Re: New SQL Actions failing! Connection/on-prem problem?? "The key didn't match any rows in the table"

Ok, MS... did someone do something?  It just now started working...

Highlighted
Resident Rockstar
Resident Rockstar

Re: New SQL Actions failing! Connection/on-prem problem?? "The key didn't match any rows in the table"

Ok, this is what fixed it...  

 

  1. I had to test the flow, but selected "I'll Perform the trigger action

    image.png
  2. Then, pick "edit connections"

    image.png
  3. Then, I re-selected the connection... even though it was already correct and "green"
    image.png

  4. The flow then ran correctly.  I repeated this procedure on another of my failed trials, and it worked.  Selecting the connection from the action itself did NOT resolve the issue!

 

Sorry MS, I get credit for this one...

View solution in original post

Highlighted
Advocate IV
Advocate IV

Re: New SQL Actions failing! Connection/on-prem problem?? "The key didn't match any rows in the table"

5 Hours and nothing worked.  Messed with Gateways, Databases, Security, and on and on.  Then I read your post.  Bingo.  Well done.  What the....?

Highlighted
Resident Rockstar
Resident Rockstar

Re: New SQL Actions failing! Connection/on-prem problem?? "The key didn't match any rows in the table"

@pulsebeat ,

 

Good question.  Before this method, the only resolution I had was to RECREATE the entire flow!!  Its like the connection just needs a kick in the butt, then its all good.

Helpful resources

Announcements
firstImage

Super User Program Update

Three Super User rank tiers have been launched!

firstImage

Power Platform 2020 release wave 2 plan

Features releasing from October 2020 through March 2021

firstImage

Join the new Power Virtual Agents Community!

We are excited to announce the launch of Power Virtual Agents Community. Check it out now!

firstImage

New & Improved Power Automate Community Cookbook

We've updated and improved the layout and uploading format of the Power Automate Cookbook!

thirdimage

Power Automate Community User Group Member Badge

Fill out a quick form to claim your user group badge now!

Top Solution Authors
Users online (5,458)