Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a web application that talks to a web service. I get the following error if I try to connect to the web service.

System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: Server was unable to process request. 

The strange thing is it is working fine on one of the set of servers and on another set of servers, we get this error.

The only notable difference between the servers is in the authentication setting in IIS. The server where the it works fine we have the ASP.Net Impersonation disabled, but on the other server I get an error the moment I disable the ASP.Net Impersonation.

share|improve this question

Not sure how the receiving server is setup but it sounds like the application pool for the server that works is authorized to make web service requests while the other server's application pool identity account is not. Most likely impersonation was turned on and setup with an account that has permission to access the web service. Check the application pool identity account and see if it matches the server that currently works, if not change it, then disable impersonation.

share|improve this answer

You could try using .NET Process Explorer to find out why this exception was thrown. Attach to the process and when it throws you'll get a back trace.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.