serenity-is / Serenity

Business Apps Made Simple with Asp.Net Core MVC / TypeScript
https://serenity.is
MIT License
2.57k stars 796 forks source link

Transaction count after Execute indicates a mismatching number of BEGIN and COMMIT statements #6735

Closed BDChinmayi closed 1 year ago

BDChinmayi commented 1 year ago

Before submitting the bug report, please read and check the following items

What happened?

While editing purchases, it should update the values in database when clicking the button Apply Changes. But instead of that it displays error message as 'Transaction count after Execute indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 1, current count = 2.' Image1

What did you expect to happen?

How to rectify this error, please guide me

How to reproduce?

  1. Add new purchase detail by clicking the link New Purchases, if there is no company name please add company name.
  2. Display the purchases by clicking the the menu item Purchases
  3. And click on id to edit the purchase detail, made some changes in the displayed dialog box and click the button Apply Changes button.
  4. It displays the error message and unable to update the purchase detail changes.

What Serenity Nuget Versions are you seeing the problem on? (separated by comma)

6.3.0.131

Relevant log output

An exception of type 'Microsoft.Data.SqlClient.SqlException' occurred in Serenity.Net.Data.dll but was not handled in user code
Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 1, current count = 2.

Serene template version

No response

Sergen version

1.0.0

Code editor

Visual Studio 2022 community version

Operating System

No response

Node.js version

No response

TypeScript version

No response

Database type and version

SQL Server 2019

On which device do you see the problem?

Laptop

On which operating system do you see the problem?

Windows 10

On which browsers do you see the problem?

Microsoft Edge

On what version of the browsers do you see the problem?

Version 111.0.1661.44

Additional information

I am using ASP dot net core 6.0