server encountered an internal error. for more information, turn off customErrors in the server's .config file.

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Ray Stevens - 26 Aug 2005 19:12 GMT

That is not a particularly useful error message. this is being thrown by a
remoting server accessing the bll/dal layers from a web. I turned off
customErrors in the remote config file, but still get this error.

Anyone have a clue as to what to do about it?

Reply to this Message

Beth Massi [Architect MVP] - 26 Aug 2005 22:04 GMT

In your Web.config, make sure you also set the typeFilterLevel attribute to
"Full" if you're passing any custom exceptions:

<channels>
<channel ref="http">
<serverProviders>
<formatter ref="binary" typeFilterLevel="Full" />
</serverProviders>
</channel>
</channels>

Also, the settings are case sensitive so make sure you specified the
customErrors mode like:

<customErrors mode="Off" />

note the capitalized "O"

HTH,
-B

> That is not a particularly useful error message. this is being thrown by a
> remoting server accessing the bll/dal layers from a web. I turned off
> customErrors in the remote config file, but still get this error.
>
> Anyone have a clue as to what to do about it?

Reply to this Message

Ray Stevens - 26 Aug 2005 22:14 GMT

The remoting application is not running in asp.net. It is a bll/dal
application layer running as a service and is of the form:
FloodRemoteHostService.exe.config. Is customErrors supported here?

> In your Web.config, make sure you also set the typeFilterLevel attribute
> to "Full" if you're passing any custom exceptions:
[quoted text clipped - 22 lines]
>>
>> Anyone have a clue as to what to do about it?

Reply to this Message

Beth Massi [Architect MVP] - 26 Aug 2005 22:28 GMT

Gotcha. So in your case ASP.NET is the client which calls the remote
components, right? You should still be able to see the exception being
caught in your ASP.NET app by setting the customErrors attribute in the
Web.config to "Off". Otherwise try triggering the exception by running a
browser on the same machine as the ASP.NET application.

> The remoting application is not running in asp.net. It is a bll/dal
> application layer running as a service and is of the form:
[quoted text clipped - 26 lines]
>>>
>>> Anyone have a clue as to what to do about it?

Reply to this Message

server encountered an internal error. for more information, turn off customErrors in the server's .config file.

Free Magazines