WebServices

  • Thread starter Thread starter Sergio M
  • Start date Start date
S

Sergio M

Hello

I have a problem with my web services (in C #), it happened that in
some cases the client invoking methods with parameters, not with
example the data type and the WS generates an exception that I would catch.

In debugging I realized that these exceptions are handled
probably by IIS (version 6).

Is there a way to intercept them?

Thanks in advance
 
Sergio M said:
Hello

I have a problem with my web services (in C #), it happened that in
some cases the client invoking methods with parameters, not with
example the data type and the WS generates an exception that I would catch.

In debugging I realized that these exceptions are handled
probably by IIS (version 6).

Is there a way to intercept them?

The client call should have a try/catch around the code to catch execptions
when the call is made. Exceptions are sometimes handled by IIS, but those
type of exceptions would be catastrophic to IIS where IIS would recycle
itself. It's most likely not happeing in your case.

However, you can look at the IIS log to see any errors it might be record
due to a possible exception. You can use Google to find out how to view the
IIS log.
 
I have a problem with my web services (in C #), it happened that in
some cases the client invoking methods with parameters, not with
example the data type and the WS generates an exception that I would catch.

In debugging I realized that these exceptions are handled
probably by IIS (version 6).

Is there a way to intercept them?

My assumption would be that the exception happens
within ASP.NET somewhere in the generated code.

For how to handle it see:

http://www.codeproject.com/KB/aspnet/ASPNETExceptionHandling.aspx
http://www.codeproject.com/KB/XML/ExceptionalSoapExtension.aspx
etc.

Arne
 
The client call should have a try/catch around the code to catch execptions
when the call is made. Exceptions are sometimes handled by IIS, but those
type of exceptions would be catastrophic to IIS where IIS would recycle
itself. It's most likely not happeing in your case.

However, you can look at the IIS log to see any errors it might be record
due to a possible exception. You can use Google to find out how to view the
IIS log.

Hi as well as the IIS logs the Event Viewer found in the administrative tools section of the control panel might also be able to shed some light on your errors.

Hope this helps.
 
Back
Top