Sql server is not committing row

I have three tables. Customers with PersonID as identity PK and Functionalities with FunctionalityID as identity PK.
Between them, I have a N:M table with these both keys, as group key.
well, some records, not all, that I try to insert it mannually (with the stored procedure is the same), I got the error:
"This row was successfully committed to the database. However, a problem occurred when attempting to retrieve the data back after the commit. Because of this, the data in this row is read-only. To fix this problem, please re-run the query."
what is wrong? why only some records?

thx in advance.
Deraldo SilvaAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

ste5anSenior DeveloperCommented:
So, what kind of front-end are you using?
Deraldo SilvaAuthor Commented:

Microsoft SQL Server Management Studio                                    11.0.5058.0
Microsoft Data Access Components (MDAC)                                    6.3.9600.16384
Microsoft MSXML                                    3.0 4.0 6.0
Microsoft Internet Explorer                                    9.11.9600.17351
Microsoft .NET Framework                                    4.0.30319.34209
Operating System                                    6.3.9600
ste5anSenior DeveloperCommented:
So you're working in SSMS? Then post a concise and complete example. A screenshot would also be interesting.
Acronis True Image 2019 just released!

Create a reliable backup. Make sure you always have dependable copies of your data so you can restore your entire system or individual files.

Deraldo SilvaAuthor Commented:
Ok. attached
ste5anSenior DeveloperCommented:
Well, just press the ! button - Query Designer\Execute SQL (Ctrl+R). The edit grid has some limitations.
Deraldo SilvaAuthor Commented:
yep. I already did it. BUT, when I do that, the record goes away.
ste5anSenior DeveloperCommented:
So, then use a query to do your update or insert. The grid hiddes the real cause.

btw, sure that there are no triggers on those tables?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Deraldo SilvaAuthor Commented:
no. there are no triggers.
so, I remove all records and recreate them. it is ok now.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2008

From novice to tech pro — start learning today.