Are you throwing SoapExceptions? I think it requires SoapExceptions on the server with the proper Exception type to get only the message. From there the SoapException client handles parsing the message correctly.

On the server you should be doing somehting like this:

if (!wwUtils.SerializeObject(Item,writer)) 
  throw new SoapException("Unable to serialize object",
                          SoapException.ServerFaultCode);

+++ Rick ---

>Weird... When I have "RemoteOnly" set in my customErrors setting, I get a message with
>
>--->
>
>as the message separator and when I set customErrors to On, the message
>separator is
>
>-->
>
> ?
>
>That's no big deal but it's still kinda weird to get this kind of inconsistency.