Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Transaction (Process ID 67) was deadlocked on lock

Transaction (Process ID 67) was deadlocked on lock

Transaction (Process ID 67) was deadlocked on lock

Hi I am getting the below given error for a package which was deployed and running fine from last 2 years in production :-

The package "PRINT_STATUS_UPDATE" failed with the errorcode: -1073548784 Executing the query " update macgi.MACGI_PRINTING_STATUS set PRINT_ER..." failed with the following error: "Transaction (Process ID 67) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

The same package runs fine in QA and Development. I request for help if someone has an idea or solution to this problem


RE: Transaction (Process ID 67) was deadlocked on lock

IS step which giving error update records? If not make sure you use (nolock) attribute when query tables. Search on server log what else running on server at the same time may be problem not in your ssis, but on another process.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close