I have no real idea what might be wrong, but if you've got control of the server code, you could potentially activate the trace code it has. (You should be able to just turn on the tracing -- via the config file for the assembly -- that was built into the code when it was written. However, it's certainly possible that the tracing code isn't there -- none of us knows how to do all of this stuff yet.)
At 10:41 AM 9/12/2003 -0400, Rebecca Lohr wrote >Richard et al, > > When the call fails, I get an exception saying that an internal error >occurred: > >System.Runtime.Remoting.RemotingException: Server encountered an internal >error. For more information, turn on customErrors in the server's .config >file. > >Server stack trace: >[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
