[There's a reason that Yoda is the unofficial mascot of SBS. Size indeed matters not.] Another reason to NOT patch - THE OFFICIAL BLOG OF THE SBS "DIVA"
Wed, Oct 10 2007 18:13 bradley

Another reason to NOT patch

There are two kinds of patches that I'll slow down and hold back on if I can... .NET is one, SharePoint is the other.  When SharePoint 3 is not externally exposed there is less risk to that site.  That's why I keep saying to folks "slow down".. READ... take a backup.

Vlad is reporting that his v3 sites are seeing an issue - Vlad Mazek - Vladville Blog » Fixing SharePoint 3.0 with KB932091:
http://www.vladville.com/fixing-sharepoint-30-with-kb932091

And http://blogs.sbsfaq.com/ is blank right now because Wayne blew up his site as he thinks he has an orphaned site

(update) - MS KB 934525 Breaks WSS 3.0 sites – here’s how I fixed it - SBSfaq.com Blog Site:
http://blog.sbsfaq.com/Lists/Posts/Post.aspx?ID=46
 

Thus I cannot stress this enough.. ALWAYS HAVE A TRAIL BACK.  And with SharePoint know how to restore it as well.

Filed under:

# re: Another reason to NOT patch

Wednesday, October 10, 2007 8:21 PM by Vlad Mazek

Just for the record, the first thing my team tried was a rollback, then a manual SQL access. That didn't work at all.

-Vlad

# re: Another reason to NOT patch

Wednesday, October 10, 2007 8:58 PM by Wayne Small

All fixed now - check out blog.sbsfaq.com/.../Post.aspx for more info.

This sucker is not nice.

# re: Another reason to NOT patch

Thursday, October 11, 2007 7:45 PM by Robert Crane

Unfortunately, I didn't read yours, Vlad's or Wayne's blog before I also managed to blow up both my Sharepoint sites (internal and external). Disappointing thing is that Vlad's fix didn't work for me and even more disappointing is that I am still waiting on Microsoft PSS to give something to try and resolve the issue.

In the meantime I have taken the opportunity to migrate both of my Sharepoint sites from WMSDE to SQL2005 and then do a Sharepoint site restore because the server restore also failed to get Sharepoint working.

A very nasty patch and poor response from MS in my books since both my production Sharepoint sites have been down since I applied the patch yesterday morning.

All I can say is I'm glad I have a Sharepoint backup AS WELL AS a server backup.

Thanks

Robert Crane

Saturn Alliance