Unable to insert row in SQL on premise

(0) Share

Report

Posted on by Community Power Pla... Microsoft Employee

I cannot insert a row in an on premise SQL database.

I get the following error:

{

"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: 3cf2aec1-0c10-4f48-b6da-1710af2791cb",

"source": "sql-we.azconn-we.p.azurewebsites.net"

}

The gateways are upgraded to the latest version.

When I add the "insert row"-action, the database and its tables are being resolved.

There are no sql-triggers on the table. It's a simple table with just two columns.

I have an existing flow with an "insert row"-action to the same database and this one works fine, but each new flow that I create with this sql-action give me this error.

Categories:

Using connectors

I have the same question (0)

All responses (9)

Answers (0)

v-bacao-msft Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi @Anonymous,

I did a test on my side and didn't meet the issue you mentioned.

Image reference:

For reference, when I configure the connection, the Authentication Type selected is Windows.

Please use Windows authentication to configure the connection and try again and see if issue still exists.

Best Regards,

Barry

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi Barry,
Authentication Type on my connection is already Windows.
As I mentioned in my post, I have another flow which inserts rows to the same database without problems, this flow uses the same connection.
Best Regards,
Sam

Was this reply helpful? Yes No
v-bacao-msft Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi @Anonymous,

Perhaps you could consider configuring a new connection for this action and then giving the connection a new name.

Please take a try again.

Best Regards,

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

I already tried that, no success

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

Like (0)

Report
Copy link

Link copied!

Having the exact same issue. I have MANY SQL actions in other flows that are working. I am trying to create new actions in a new flow (tried creating new twice) with the same ill result!

@Anonymous , did you get a positive result?

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

@martinav : I'm not sure, but I think that I've deleted the table, recreated it and that the error disappeared.

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

Like (0)

Report
Copy link

Link copied!

Yea, that is what I normally do as well with cases similar to this. In my case, even creating the flow again from nothing yeilded the same result!!

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Did you recreate the table on the sql-server?

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

Like (0)

Report
Copy link

Link copied!

@Anonymous ,

No, i do not have the ability to do anything with the tables. They cannot be altered in any way because they are part of a purchased software system.

In fact, I am getting the same problem with actions I'm creating new from all tables and views I have tried from that same SQL instance. BUT... I am using these tables in existing flows, and they are working.

Of course, I will not be messing with those flows because I have had issues in the past that simply saving a flow during the time there was some sort of a Micorsoft issue with Flow was enough to kill the flow from subsequent execution.

Was this reply helpful? Yes No