INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Member Login

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips now!

Talk With Other Members
Be Notified Of Responses
To Your Posts
Keyword Search
One-Click Access To Your
Favorite Forums
Automated Signatures
On Your Posts
Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

LINK TO THIS FORUM!

Tek-Tips LinkedIn^® Group

Join our
LinkedIn^® Group!

Hook up with past and present colleagues and classmates quickly.

Partner With Us!

"Best Of Breed" Forums Add Stickiness To Your Site

(Download This Button Today!)

Feedback

"...I wish I knew about this site years ago. It would have saved me a lot of heartaches..."

More...

Geography

Where in the world do Tek-Tips members come from?

Click Here To Find Out!

Tek-Tips Shirts!

Get your
Tek-Tips Forums
SWAG here!

Home > Forums > Programmers > Web Development > Microsoft: ASP.NET Forum

Web Service Exceptions

Read More Threads Like This One

LindaH (Programmer)

7 May 02 17:06

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.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Back To Forum

Back To Microsoft: ASP.NET