Thursday #PowerShell #PowerTweet – Looking for Broken Webs in #SharePoint 2007

By | July 17, 2014

Yep, you read the post title correctly – SharePoint 2007, Microsoft Office SharePoint Server.  Good ol’ MOSS.

I’ve been working on a project recently where MOSS is in place.  Lot’s of MOSS.  In total over 30 farms, something like 300,000 users dependent on who you ask.  A ton of MOSS.

I like MOSS.  It was a simpler thing from a simpler time.  Sure, it has problems but doesn’t everything?

Anyway, enough of the philosophising.

A number of the farms in the estate were exhibiting issues with broken webs.  These broken webs would cause all kinds of oddities.  Timer jobs would croak, user experience would be impacted, Search was having kittens.  You get the problem.

With tens of thousands of webs in some of the farms, locating the broken ones was proving challenging and was being managed through case-by-case analysis of inbound helpdesk calls.  Not ideal.

Unsurprisingly, PowerShell, even with MOSS, would be a good way to uncover all of the webs that were exhibiting problems so they could then be analysed protectively – a better approach all round.

All up, it’s not too complex, load the assembly, instantiate a farm object and walk through it.  The key is in the scripts ability to ignore web applications that don’t contain content as they’re SSP web applications or the Central Admin web app.  It keeps the output clean and uncluttered, just the way I like it.

See the comments for more information about what’s going on and as always, use with caution and test, test, test! 🙂

more to follow…

Leave a Reply

Your email address will not be published. Required fields are marked *