Archives / 2009 / July
  • My favorite new quick fix: MS Office Diagnostics

    Rebooting cures a multitude of ills.

    Over the past two years I've come to realize that the SharePoint server equivalent is to run the SharePoint Products and Technologies Configuration Wizard (what a mouthful that is).  However, my latest discovery is that there is a client equivalent as well.

    If a user complains of JavaScript errors (e.g. "Library not registered"), of Excel 2007 documents opening in Excel 2003, or a handful of other SharePoint-related client-side issues, I now point them directly to the MS Office Diagnostic Tool.  Here's the basic procedure:

    1.      Open Word 2007 (or Excel 2007).
    2.      Click the Office button.
    3.      Click the Word Options (or Excel Options) button on the resulting menu.
    4.      Select the Resources tab on the left.
    5.      Click the Diagnose button.
    6.      Start the diagnostic tests and follow the prompts.

  • Hiding the Recycle Bin

    The SharePoint Recycle Bin is a very useful feature, but due to the lack of a separate permission structure, sometimes product owners want to hide it from their users.  This can be done in a variety of ways, but I've found that the simplest is to create a new master page (usually from a downloaded copy of the one you currently use on your site) and find the following tag:

  • SPTraceView: One step closer to unscrewing the inscrutable

    We still don't have good SharePoint debugging, but today I came across a tool that gets us closer.  Essentially it works off of the SP logging mechanism, and alerts you when messages come up that meet your predefined filters.  This has the advantage of (a) keeping you from having to go through the log files line by line, and (b) filtering at a higher level, allowing you to keep all that log information rather than excluding some events from being logged.