Thank goodness for MS Professional Support. As a novice WSSv3 developer/site definition creator, I have found myself constantly frustrated by the fact that when things break you have to look at the text log files to try and figure out what the heck happened. In a call on a seperate issue to MS Support, I was told of a nifty configuration change to enable the stack trace to be sent to the browser. Here are the particulars.
Update your web.config in the respective wss application directory:
<SafeMode MaxControls="200" CallStack="false" ...>
< !-- Becomes-- >
<SafeMode MaxControls="200" CallStack="true" ...>
<customErrors mode="On" />
< !-- Becomes-- >
<customErrors mode="Off" />
<compilation batch="false" debug="false">
< !-- Becomes-- >
<compilation batch="true" debug="true">
Now the next time you hit it instead of that friendly USELESS error message, you can really see what is going on. Of course now you will have to decypher what it is that the stack trace means but that is for a different day.
Hope this helps you as much as it has me.