locked
Transaction (Process ID 59) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim RRS feed

  • Question

  • Hi Team,

    Am executing bellow script by using OLEDB command but am getting error. Please help on same

    My query: 

    with cteChk as (
    select *,ROW_NUMBER() OVER (
                PARTITION BY branchId,ChkSum
    order by branchId,ChkSum) rw_num
    from BranchDetails with (nolock)
    ) delete from cteChk where rw_num>1

    Error Message:

    Branch Details:Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred.
    Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005
    Description: "Transaction (Process ID 59) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim.Rerun the transaction.".


    Thanks Bala Narasimha

    Thursday, December 12, 2019 6:17 AM

All replies

  • Hi Bala,

    Please do not post the the same question in this forum.

    May I know if the solutions here are helpful for you?

    Best Regards,

    Mona


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Thursday, December 12, 2019 9:08 AM
  • Hi Mona,

    Sorry for same post. By mistake have posted same post.

    Noted next time will not repeat same 


    Thanks Bala Narasimha

    Thursday, December 12, 2019 11:11 AM
  • Hi Bala,

    Please delete this duplicate post.

    Regards,

    Mona


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Friday, December 13, 2019 7:42 AM