Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Web Service Exceptions

Status
Not open for further replies.

LindaH

Programmer
Dec 12, 2001
42
US
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.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top