Post reply

Transaction (Process ID 107) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

  • March 2, 2011 at 11:17 pm

    #235410

    Dear All!

    I have this problem in our one of module, Please let me know your suggestion to overcome this problem..

    Transaction (Process ID 107) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

  • March 2, 2011 at 11:50 pm

    #1293859

    That's useless for fixing the problem.

    Enable traceflag 1222. That will cause SQL to write the deadlock graph into the error log when a deadlock happens. Get the deadlock graph and post it, along with the definition of any tables and indexes referenced by the graph.

    DBCC TRACEON (1222,-1)

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • October 6, 2014 at 1:42 pm

    #1750403

    Hi learned people. I have low to mid level sql knowledge. I support emr software. I get this issue upon logon; the mentioned error, i will paste at the end. ( i have a client app hitting an sql database). When you keep on trying to log on, upon the eigth or ninth attempt, the logon would work.

    Here is my error:

    Transaction (Process ID 63) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction

    Thank you.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply