Small and medium business | Business Central, N...

Reporting Error: “An error occurred and the transaction is stopped”

(3) Share

Report

Posted on by Nimsara Jayathilaka.

4,455

Hi Community,

When running any report in Business Central, we’re encountering the following error message:

“An error occurred and the transaction is stopped. Contact your administrator or partner for further assistance.”

Is this a common issue in Business Central, or could it be related to customizations in our environment?

Has anyone else faced this recently — or could this be related to a recent Microsoft wave update?

If requesting support, please provide the following details to help troubleshooting:

Error message: 
An error occurred and the transaction is stopped. Contact your administrator or partner for further assistance.

The following AL methods are limited during write transactions because one or more tables will be locked: Form.RunModal, Codeunit.Run, Report.RunModal, XmlPort.RunModal.

Form.RunModal is not allowed in write transactions.

Codeunit.Run is allowed in write transactions only if the return value is not used. For example, 'OK := Codeunit.Run()' is not allowed.

Report.RunModal is allowed in write transactions only if 'RequestForm = false'. For example, 'Report.RunModal(...,false)' is allowed.

XmlPort.RunModal is allowed in write transactions only if 'RequestForm = false'. For example, 'XmlPort.RunModal(...,false)' is allowed.

Use the commit method to save the changes before this call, or structure the code differently.

Contact your application developer for further assistance.

Internal session ID: 
61d4d6f2-9e50-4c76-b087-0425fe4eb722

Application Insights session ID: 
46ad9891-92ee-4ed0-b065-daadb8b67586

Client activity id: 
b6ac8d04-7e3a-41dc-ac89-980bbb7a489d

Time stamp on error: 
2025-10-07T05:58:54.6695947Z

User telemetry id: 
6b882ab2-1a3b-4362-83ee-36e9f3b4179d

Thank you in advance for any insights.

Nimsara

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (4)

Answers (0)

Suggested answer

Rishabh Kanaskar 4,207 on at

Like (1)

Report

Reporting Error: “An error occurred and the transaction is stopped”

Hi,

This error is not a general platform issue but is usually caused by customizations or extensions that run reports or modal pages inside a write transaction. Business Central restricts certain AL methods during write transactions to prevent deadlocks. The error message indicates that a Report.RunModal or similar call is being executed while the database transaction is still open.

Thanks

Rishabh

Was this reply helpful? Yes No
Suggested answer

Aman Kakkar 462 on at

Like (2)

Report
Reporting Error: “An error occurred and the transaction is stopped”

Hi,

When you perform database writes (INSERT, MODIFY, DELETE etc.), BC opens a transaction.

While inside that uncommitted transaction, you cannot run UI-bound functions like:

PAGE.RUNMODAL

REPORT.RUNMODAL

CODEUNIT.RUN

XMLPORT.RUNMODAL

Because those calls may cause user interaction or nested transactions, BC blocks them with this runtime error.

As other experts suggested, you need to add COMMIT before using UI-Bound Functions.

If the issue still persists, you can try restarting your environment.

Hope it helps.

Aman K

Was this reply helpful? Yes No
Suggested answer

Teddy Herryanto (Th... 14,169 Super User 2025 Season 2 on at

Like (1)

Report

Reporting Error: “An error occurred and the transaction is stopped”

This is a customisation issue. You should contact your partner to help you with this.

When BC tries to open a new page/report, all the ongoing transactions need to be committed (saved) before opening the page/report.

Your partner needs to refactor the code to make sure the record changes are saved before opening any page/report.

Was this reply helpful? Yes No
MariusTeleman_VGR 40 on at

Like (1)

Report
Reporting Error: “An error occurred and the transaction is stopped”

Hi,

This is a standard BC message because the bellow operations are not allowed. As a weird workaround try adding a COMMIT; before runmodal. This is to release the tables involved in the dataset and avoid locks.

Form.RunModal, Codeunit.Run, Report.RunModal, XmlPort.RunModal.

Was this reply helpful? Yes No