WSS 3.0 / MOSS 2007 .. Troubleshoot Unexpected error ...

July 13, 2008 · 1 min read

Been a while since i last posted - I guess its because of my recent engagement with sharepoint focusing on various Moss 2007 focusing on Enterprise Search and BDC and some WSS.

I must say Moss 2007 has come a long way from its predecessor, however, What is the most frustrating issue is the "unexpected error" that you get when you deploy anything. Offcourse, I immediately look for the logs and event viewer the configuration analyzer etc.,

I can now reproduce this error on demand on any webpart - that's may way of getting even with this error in sharepoint.

  1.  Forgetting public keyword
  2. typo in webpart file and safe control registration

When i continue to get the problem, Adding this to GAC helps in solving this. offcourse, there are instances where i have to deploy this on both GAC and on the bin folder.

Following changes to the web.config file helped a lot...

 
    <SafeMode MaxControls="200" CallStack="true" DirectFileDependencies="10"
     TotalFileDependencies="50" AllowPageLevelTrace="true">

Change the CallStack from "false" to "true" and  AllowPageLevelTracing.  Also, remember change the CustomErrors Off and enable debug mode.

This definetly accelerated my debugging time with sharepoint.

Readers, please continue to share your experience and additional recomendation to troubleshoot this issue with moss & wss.

This article is part of the GWB Archives. Original Author: Mahesh Anandan

New on Geeks with Blogs

  • We Won The One Award I Actually Care About

    Full Scale made the Inc. 5000 for the fifth year straight, the 12th listing across my three companies. Here is why the one award you cannot buy is worth stopping for.

  • Your Customers Build the Features Now

    I let a tool I liked sit dead for a year rather than build the features I wanted. An MCP server meant I never had to, and your customers can do the same to your product.

  • Get the Size of a Directory in Linux the Easy Way

    du -sh for the quick answer, ncdu for the cleanup, df for the disk itself: every command for checking directory size in Linux, plus why du and df never agree.

  • Vim Search and Replace: The Ultimate Guide

    One :%s command replaces every match in a file before a find dialog would even open. The Vim substitute patterns worth the muscle memory: flags, ranges, capture groups, and multi-file edits.