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

(0) Share

Report

Posted on by martinav

3,340

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):

Created a new connection
Deleted and re-created the action
"Save-As" to a new flow
Created the flow again from nothing (twice)

Categories:

Using connectors

I have the same question (0)

All responses (4)

Answers (1)

Sort by

martinav 3,340 on at

Like (0)

Report
Copy link

Link copied!

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

Was this reply helpful? Yes No
Verified answer

martinav 3,340 on at

Like (1)

Report
Copy link

Link copied!
Ok, this is what fixed it...

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

Then, pick "edit connections"

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

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...

Was this reply helpful? Yes No
pulsebeat 151 on at

Like (0)

Report
Copy link

Link copied!

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

Was this reply helpful? Yes No
martinav 3,340 on at

Like (1)

Report
Copy link

Link copied!

@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.

Was this reply helpful? Yes No