My web service calls a class, the class throws an encoded error back to the web service, which throws the error back to the aspx.vb page. I'm throwing an encoded error so I can handle specific error codes in the aspx.vb page. My problem is the soap information that prefixes my "real" error message. Is there a way to get rid of the soap "header" (shown in red, below)?
System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Exception: #F:200:User already exists.
And sometimes I just get:
Server was unable to process request. ---> #F:200:User already exists.
System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Exception: #F:200:User already exists.
And sometimes I just get:
Server was unable to process request. ---> #F:200:User already exists.