Chris Day -- did you mean "is incorrect" when you say "is...WRONG!"? That is, did you mean that Brant Fallin's statement -- that "the customError [sic -- typo for customErrors] element is ignored by remoting architecture at the moment" -- is not correct?
The docn seems to agree that <customErrors mode="off"> is what you should put in the config file to get more exception details. That is somewhat contrary to the instruction in the error message that said "For more information, turn on customErrors in the server's .config file" !! Given that mode="off" seems to be what's needed, the error message is very misleading. Who do we tell so that the message can be corrected? At 08:21 AM 8/25/2003 +1000, Chris Day wrote >That remoting ignore's customErrors tag is in fact WRONG! > >People may have tried it but put the tag in the wrong place. It should >be like this > ><configuration> > <system.runtime.remoting> > <customErrors mode="off" /> > >HTH > >Chris > >> -----Original Message----- >> From: Brant Fallin [mailto:[EMAIL PROTECTED] >> Sent: Saturday, 23 August 2003 12:56 AM >> To: [EMAIL PROTECTED] >> Subject: [ADVANCED-DOTNET] Custom ServerTransportSink >> >> >> When calling _nextSink.ProcessMessage(...) from a custom >> server transport sink i am developing i get a ReturnMessage >> that contains an exception with the following text: >> >> "Error: Server encountered an internal error. For more >> information, turn on customErrors in the server's .config file" >> >> From what i have been able to find on the web, the >> "customError" element is ignored by remoting architecture at >> the moment so no luck finding a clue as to what i going wrong. [snip] J. Merrill / Analytical Software Corp =================================== This list is hosted by DevelopMentor� http://www.develop.com NEW! ASP.NET courses you may be interested in: 2 Days of ASP.NET, 29 Sept 2003, in Redmond http://www.develop.com/courses/2daspdotnet Guerrilla ASP.NET, 13 Oct 2003, in Boston http://www.develop.com/courses/gaspdotnet View archives and manage your subscription(s) at http://discuss.develop.com
