SharePoint Products TechCenter >
SharePoint Products and Technologies Forums
>
SharePoint - Setup, Upgrade, Administration and Operation (pre-SharePoint 2010)
>
stsadm getsitelock in WSS 2.0 or SPS 2003
stsadm getsitelock in WSS 2.0 or SPS 2003
- Hi,
we took over a huge SharePoint 2003 farm (> 2000 Site Collections, 5 TB of data) from a former provider. We will soon be upgrading to Moss, but before that we need to do some clean up.
It appears that the farm was maintained very poorly and Site Collections were migrated, deleted or whatever - speak - set on "adding content prevented" with the additional lock information "migrated". That's it.
No word about "can be deleted", "a date", "a change number" or anything else...
It would be a pain to go through all Site Collections to find out the lock state (there is no documentation which Site is locked) to clean it up.
We need the stsadm command "getsitelock" from Moss 2007 to find out about the current state, but it is not available for SPS 2003 / WSS 2.0.
Any ideas?
Thanks a lot in advance,
Stephanie- Edited byOkel Tuesday, November 24, 2009 8:30 AMtypo
- Edited byMike Walsh MVPMVP, ModeratorTuesday, November 24, 2009 8:36 AM"urgently" removed from Text. Ring MS Customier Support Services if you are in a hurry. Do not say in forums that something is urgent or you want it asap (etc.)
All Replies
- OK, I see there seems to be no "easy" solution.
Does someone know which "flag" in the content DB shows, that a Site Collection was set on "adding content prevented"? I have been deeply investigating a content DBs of a Site in unlocked and in locked state, but I have not found any change of any record. Is it hiding in the Config DB?
Please help us to find some way to find out which Site Collections have been locked or set on "adding content prevented" in WSS 2.0 and SPS 2003 in the past. So far no "googling" or anything has helped us.
Thank you,
Stephanie
