Deadlock error during STSADM export

[JonathanHerschel]

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...n/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_g...nt-deployment-best-practices.aspx?PageIndex=2

Any advice is appreciated!


Jonathan K Herschel

 

[SPV]

Hi Jonathan. I haven't hit this particular error before and don't know anything about Sharepoint's event receivers.

However I do have a suggestion... have you put a read-only lock on the site collection (Admin Console -> Application Management -> Site Collection Quota and Locks) before starting your export? I believe Microsoft recommend this, if only because it ensures your export will be consistent.

 

[JonathanHerschel]

Do you have a reference where this is recommended? I have read a few blogs that suggest it doesn't work.

http://technet.microsoft.com/en-us/library/cc262811(office.12).aspx

the message on the bottom says "Export and sitelock: When using export rather than backup, it appears that the noaccess lock is too restrictive and the export command cannot execute. I used sitelock readonly instead. That seemed to work fine for the export.
But careful, the import then failed with an error message indicating that a certain parent web not being present.
Conclusion: sitelock cannot be used with export."

http://social.technet.microsoft.com...n/thread/25fe701b-b1dc-410d-88f8-c0378fa4f8a9

- says not to use setsitelock

I guess it is worth a try to see if it resolves our issue...

Jonathan K Herschel

 

[SPV]

Hmmm, you've caught me there. Sorry, I think I was thinking of the stsadm backup operation, not the import operation you clearly mentioned. My bad.

As an aside, WSS SP2 introduced automatic site locking for the backup operation (which I take to be a very strong recommendation from Microsoft).

As for the export problem you mention, sorry I'm out of ideas. I hope someone else can offer further suggestions for you. Good luck.