web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Microsoft Dynamics RMS (Archived)

HQ Client Error - "Transaction(Procss ID 59) was delocked on lock resouces with another process......"

(0) ShareShare
ReportReport
Posted on by

Hi,

Does anyone have this deadlock issue with HQ Client?

"transaction(Process ID 59) was deadlocked on lock resources with another process and has been choosen as the deadlock victim.Return the transaction"

I am having this issue at few of my HQ Client stores. It occur couple of times a day.

I use query - "SET DEADLOCK_PRIORITY NORMAL; GO'  and this did not help. I always backdate 401 worksheet so it will upload data again. Otherwise, it will not upload any data at all.

I am currently running two different server computers.

Server1 - Running SQL Server 2008 / Windows Server 2008
Server2 - Running WIndows Server 2008 / 6 Different HQ Servers with a different server ports
Stores x 23 - Each HQ Servers running 4 store connections and each store connection time is 10mins apart from each store connection

Is there any Hotfix that will fix this issue?

-Danny 

*This post is locked for comments

I have the same question (0)
  • Community Member Profile Picture
    on at
    RE: HQ Client Error - "Transaction(Procss ID 59) was delocked on lock resouces with another process......"

    Hello Danny,

    Thank you for your question.

    A number of Deadlock errors were resolved on Cumulative Update 5, which will bring you up to version 2.0.2000.

    Also make sure that your stores are not connecting to headquarters at the same time by staggering the connections times and that Headquarters Client is not running on the same computer that hosts the store database and that Headquarters Server is not on the computer hosting the Headquarters database.

    Thank you,

    Scott Wardzinski

    Microsoft Dynamics RMS & POS Support Engineer

  • Community Member Profile Picture
    on at
    RE: HQ Client Error - "Transaction(Procss ID 59) was delocked on lock resouces with another process......"

    Hi Scott,

    We are currently using FP2 and my RMS ver 2.0.1005.

    I am running Headquarter Server and Database server separately two different machine.

    On the HQ Server machine, I am running 6 different HQ Servers using HQServer command.

    Do you recommend using separate machine running each servers?

    Also, my HQ Client is running on same machine where Store Database is also it runs the POS as well.

    I will separate those programs.

  • Community Member Profile Picture
    on at
    RE: HQ Client Error - "Transaction(Procss ID 59) was delocked on lock resouces with another process......"

    Scott, I have upgraded to CU5 and Hotfix#40 and it still giving me a deadlock error from HQ Client.

    Store connection times are different from each stores. they are 10 mins apart.

    Like I mentioned, I am running 6 different HQ Server app from one machine.

    they all have different port numbers and each server contains 5 different stores to connect. Stores connect every hours with 10/20/30/40/50 min. And other server apps are same connection settings.

    Connect at XX minutes past the hour.

    Port# 34000

    S1 - 10min

    S2 - 20min

    S3 - 30min

    S4 - 40min

    S5 - 50min

    Port#34100

    S1 - 10min

    S2 - 20min

    S3 - 30min

    S4 - 40min

    S5 - 50min

    Port#34200

    S1 - 10min

    S2 - 20min

    S3 - 30min

    S4 - 40min

    S5 - 50min

    I have 6 servers connection like this to HQ servers.

    Does connection time must be different even they are connecting to different server?

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics RMS (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans