This article by Wendy Neal illustrates what I try to communicate to businesses about their SharePoint investment. Most companies install the product and point users to the URL. That’s like planting a sapling, and then walking away from it! Don’t blame the sapling that doesn’t grow because you don’t provide care for and feed it. No wonder people don’t like saplings!
I’m still working with SharePoint 2010 because that is what my customer just migrated to. Am I getting too far behind in SharePoint land? I feel somewhat stressed because all the SP frontrunners are all talking about 2013, and one even mentioned SPNext! This is all overwhelming and I wonder if I’m hurting my career by not getting up to speed with 2013. Since my customer just went to 2010, I am still learning some things about that. Do I need to brush up on some 2013 courseware to stay abreast of the technology? Does anyone else feel like they are having a hard time staying afloat with SharePoint?
Some time back I had an issue with a SP2007 site. Users were getting the Access Denied error in the front end site. I couldn’t even log in with a Farm Administrator site! I could get to CA though. I spent days searching and trying different things, messing with permissions, etc. Eventually I stumbled upon a page with information about the SetSiteLock feature.
So I check the site lock setting with this script:
stsadm -o getsitelock -url http://server_name
Lo and behold it was set to readonly, which makes you think that you could access it. In this case however, no one could access it! So when I set the SetSiteLock to none, it was fixed. So I found that while the server was performing a backup, Windows Update came along and applied updates. Naturally it kindly restarted the server for me, leaving the site in Readonly (but somehow locked) status. Since the powers that be would not let ME control the Windows Updates, I scheduled backups to NOT coincide. I’ve never had that issue come up since.