Yep and ULS Viewer is your best firend for real-time log viewing for this too. 
I'd add a few filters and search for the exception you get in the UI. E.g. set 
web.config to show debug info too.

From: [email protected] [mailto:[email protected]] On Behalf Of 
Matthew Cosier
Sent: Wednesday, 8 December 2010 11:54 AM
To: 'ozMOSS'
Subject: RE: Custom Field Control failed to render

What you need to do with debugging this sort of stuff generally is to set the 
logging output to 'error' or 'verbose' in diagnostics and logging, then cause 
the error (ie hit the page), then switch it back to normal (don't forget this 
or your logs will end up huge :)), then your error logs should expose more 
information about the crash.  (It's been a long time, but I'm pretty sure 
that's how you do it).

M

From: [email protected] [mailto:[email protected]] On Behalf Of 
Paul Noone
Sent: Wednesday, 8 December 2010 2:36 PM
To: ozMOSS
Subject: RE: Custom Field Control failed to render

Hi Matthew,

Unfortunately I don't have access to the source and am not finding anything in 
the event viewer or SharePoint logs. :|

Regards,

Paul

--
Online Developer/Administrator,
ICT Projects Team
CEO Sydney

From: [email protected] [mailto:[email protected]] On Behalf Of 
Matthew Cosier
Sent: Wednesday, 8 December 2010 2:15 PM
To: 'ozMOSS'
Subject: RE: Custom Field Control failed to render

You should check the logs for the detailed exception, it will probably unravel 
the underlying issue.  Or if you have the source code for the field control, 
attach to w3wp and turn on first chance exceptions in VS.

M

From: [email protected] [mailto:[email protected]] On Behalf Of 
Paul Noone
Sent: Wednesday, 8 December 2010 1:42 PM
To: ozMOSS
Subject: Custom Field Control failed to render

HI all,

I have a custom field control which works beautifully with default.master but 
fails to render when using our own, or any of the MS publishing masters.


Figure 1 - Custom masterpage
[cid:[email protected]]


Figure 2 - Using default.master
[cid:[email protected]]

I've compared the non-functioning masterpages against default.master but can't 
find anything missing.

Can anyone think how this might occur or what the cause might be?

Regards,

Paul

--
Online Developer/Administrator,
ICT Projects Team
CEO Sydney

<<inline: image001.jpg>>

<<inline: image002.jpg>>

_______________________________________________
ozmoss mailing list
[email protected]
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss

Reply via email to