Error: Error: Transaction (Process ID xxx) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. We have been plagued lately with getting deadlock errors during an STSADM export. We are doing a lot of migrations and this error occurs multiple times and we have a low passing rate. Does anybody have any ideas how to resolve this or tips so that we don’t get them? Is this SQL related or SharePoint version related? We are running SP version 12.0.0.6524 During my search, didn’t find any resolutions… No answers here: http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/b068d1d9-cf8e-4eee-80e2-50b96b023e2e This refers to STSADM import, but we have not encountered it during import: http://technet.microsoft.com/en-us/library/dd795107(office.12).aspx#Section9 Again, import only, but this blog talks about disabling event receivers on box. How do I do that? http://blogs.technet.com/b/stefan_gossner/archive/2009/01/16/content-deployment-best-practices.aspx?PageIndex=2 Any advice is appreciated!

Hi Jonathan, Reduce activity on the site you are exporting as much as possible. The April 2010 cumulative update for sharepoint has resolved at least two deadlock issues found on the export cycle of content deployment (equivalent to stsadm -o export). References Updates Resource Center for SharePoint Products and Technologies http://technet.microsoft.com/en-us/office/sharepointserver/bb735839.aspx Description of the Windows SharePoint Services 3.0 Cumulative Update Hotfix Package: April 27, 2010 http://support.microsoft.com/kb/981043 Description of the Windows SharePoint Services 3.0 Cumulative Update hotfix package (sts-x-none.msp): April 27, 2010 http://support.microsoft.com/kb/981040/ Reagrds, Hiran Microsoft Online Community Support