In one of the environments I work in, we have a SharePoint 2007 server on Server 2003.  Recently we applied our June Windows patches and the April cumulative update (CU) packs for WSS 3.0 (http://support.microsoft.com/kb/2512783) & SharePoint 2007 (http://support.microsoft.com/kb/2512782).  As a note, if you aren’t patching your SharePoint with the CUs as per this site, I would highly recommend a change.  Check out the site and decide for yourself.  Anyway, after patching I had users complaing of certain menu items disappearing.  Namely, the “Settings” options for just about everything.  I went in to check it out and noticed the “Site Settings” was gone from the site menu even though I am the site collection administrator.  I was able to get to it via the direct url (<site url>/_layouts/settings.aspx), but things were not quite right.  I also noticed I could not modify permissions for the site collection.

Everything seemed to be functioning as far as the site would display for users, noone was denied access, they just weren’t able to modify workflows or lists or anything.  I also found it strange that it was only affecting 1 site collection of 1 web application on the server.  I ended up discovering that the site was set in readonly mode.  The content DBs are locked during patching and backups, sometimes if the process is interupted they can remain locked afterwards.  The way to check whether there are any locks on any of your sites is via this command (remember to change your prompt to the 12-hive, C:\Program Files\common files\Microsoft Shared\web server extensions\12\BIN):

 

stsadm -o getsitelock -url http://server_name

 

If it returns anything other than “none”, something is locked. Now, remember, if you are during backup/patching timeframe, someone else may be doing something that requires a db lock.  In order to release all locks on your server and return to normalcy, run this command:

 

stsadm -o setsitelock -url http://server_name -lock none

 

Now, you should be good to go. If you notice lingering issues, or anything different, let me know. I’d be glad to help look into it.

Be Sociable, Share!

« »