Web service on Windows 2008 Server/IIS 7.0: error pages instead of SOAP fault exceptions?

Discussion in 'ASP .Net' started by sqlman, May 15, 2009.

  1. sqlman

    sqlman Guest

    I have a working ASP.NET 1.1 web service, which I had no problems with
    on Windows 2003 server.

    Recently, I moved the web service to a Windows 2008 Server box (IIS
    7.0), configured it to run in a NET 1.1 classic application pool. The
    web service runs fine, however there is one major difference: any
    exception raised by the web service causes the IIS to return a HTTP
    500 Internal Server error page, instead of a SOAP fault. As the
    result, the clients cannot handle exceptions anymore.

    I suspect this behavior is controlled via configuration somehow, but I
    am not sure where to look. Any ideas?

    Thank you!
    sqlman, May 15, 2009
    1. Advertisements

  2. sqlman


    Nov 25, 2011
    Likes Received:
    Did you ever manage to stop IIS7 from suppressing the SOAP fault?
    I've got exactly the same problem, so would appreciate some help.
    Soapy, Nov 25, 2011
    1. Advertisements

  3. sqlman


    Nov 30, 2011
    Likes Received:
    Me too

    Me too.
    I also have this problem
    me2, Nov 30, 2011
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.