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

Assistance Required to Resolve Deadlock Issue in Webservice API

(1) Share

Report

Posted on by Rajaneesh H

244

Hi Techis,

I am currently working with a Webservice API (BC OnPrem) that inserts lines into Payment Journal Pages. However, when the volume exceeds 100 lines, I encounter the following error:

“The activity was deadlocked with another user who was modifying the Gen. Journal Line table. Please retry the activity.”

Could you please help me with the following:

1. Is there a way to identify which users or processes are causing the table lock?

2. What steps can be taken to resolve or avoid the deadlock issue?

Looking forward to your guidance.

Regards

Raj

Categories:

Dynamics 365 Business Central

Microsoft Dynamics RMS

Dynamics 365 Business Central migration

Microsoft Dynamics NAV

I have the same question (0)

All responses (4)

Answers (0)

Sort by

xgaronnat 40 on at

Like (0)

Report
Copy link

Link copied!

Hello Rajaneesh,

You should have a look to batch / error handling with API : https://www.kauffmann.nl/2020/12/22/batch-calls-with-business-central-2-error-handling/

Was this reply helpful? Yes No
Suggested answer

Ramiz 597 on at

Like (0)

Report
Copy link

Link copied!

Hi,

Try this PowerBI reports or telemetry to see in depth details. It requires PowerBI pro license but you can use a trial for 60 days.

https://appsource.microsoft.com/en-us/product/power-bi/microsoftdynsmb.bc_telemetry_pbi_app

Also, how are you consuming the API? I have inserted 100+ records in General Jounral Line using API and never faced this error.

Was this reply helpful? Yes No
Suggested answer

Khushbu Rajvi. 22,206 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

If it helps: https://community.dynamics.com/forums/thread/details/?threadid=8f42ba1b-da09-4a42-940f-cd9c8a9b9f75

https://community.dynamics.com/forums/thread/details/?threadid=95a16663-d135-ee11-bdf4-000d3a557230

https://community.dynamics.com/blogs/post/?postid=d67b889c-ec0a-41bc-996d-a97f9c9eb29a

Was this reply helpful? Yes No
Alexander Drogin 262 on at

Like (0)

Report
Copy link

Link copied!

There are no tools in Business Central that could point to a specific user session that intervenes with the insert. But on the other hand, it's a good thing that you are dealing with an on-prem environment rather than SaaS, it's always easier to troubleshoot when it comes to locking problems. Best way to start is to capture SQL events with the SQL Server Profiler while your web service client is active. Enable capturing the Deadlock Graph event in the profiler: Analyze Deadlocks - SQL Server Profiler | Microsoft Learn

This event will show you exact SQL queries that were deadlocked, and from there you can figure out the code causes the lock.

Only when you have the first answer you can start taking measures to prevent the deadlock, because reasons can vary widely and the respective steps can be very different.

Was this reply helpful? Yes No