RE: MossMenu Error

Tech-Archive recommends: Fix windows errors by optimizing your registry

For those who may run into the same issue, I have found a solution:

First of all, the error was that I was placing the MossMenu outside of the
scope of the DataSource that I was referencing. I didn't realize aspx pages
used scope. Seems that if you want to reference a DataSource that lives
inside an asp:ContentPlaceHolder, you need to have the other control in that
ContentPlaceHolder as well.

How I figured it out: Inside MossMenu I am overriding the OnInit and OnLoad
methods of the base class and doing some simple logging inside a try-catch.
Guess what? I logged an exception in the OnLoad, telling me that my control
couldn't find the datasource I was looking for. Thanks MOSS for eating that
exception.....

Joe
--
www.xcomplica.com


"Joe C" wrote:

Hi Wei Lu,

I understand that the MossMenu code is not supported, that's not my question
however. I am asking how I can get sharepoint to stop eating errors.
Obvously there is an exception being thrown somewhere that MOSS translates
into a nice and friendly and utterly useless "An Unexpected Error Has
Occured" message. Since I can't find anything in the MOSS log files, am I to
assume that I am out of luck? Or is there a way I can make MOSS be more
verbose in its error logging etc.

Regardless of the code I am using (be it my own code or the MossMenu), I
don't see how it's acceptable for MOSS to give me such a useless error
without logging the actual real problem somewhere. I'd be perfectly happy if
I got an error page similar to aspx when I set <customErrors mode="Off" />.

Thanks,

Joe
--
www.xcomplica.com


"Wei Lu [MSFT]" wrote:

Hello Joe,

I understand that you could not get the MossMenu work which is a resource
kit provide from the Sharepoint team.

Due to our support policy, we did not provide the support for the following:

Debugging of source code itself, reading memory dumps or lab setup of
complex scenarios.
Beta product and products that no longer have Extended support from MS.
Third party software or non-HCL hardware.
Resource Kit Utilities.
Licensing issues.
Non-English software or hardware.
Performance issues in a production environment.

I suggest you contact the Sharepoint Team directly to check whether there
are any suggestion.

Thank you for your understanding!

Sincerely,

Wei Lu
Microsoft Online Community Support

==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================
This posting is provided "AS IS" with no warranties, and confers no rights
.