Handling async ASMX web service exceptions?

Yes, the generic error deals with security. The idea being that if an attacker does find a fault in the page etc. The person doesn't know what the cause of the error was.

Yes, the generic error deals with security. The idea being that if an attacker does find a fault in the page etc. The person doesn't know what the cause of the error was. Have you turned on remote debugging in the serviceDebug tag?

mostlydevelopers.com/mostlydevelopers/bl... This should return a less general error.

Ahh, thought so, thanks for the link, but this seems to be dealing wiht WCF services, not plain ol' asmx (ones with the WebMethod atttribute). Not sure it it would work! – Andy Apr 16 '10 at 10:50.

I think you may actually be getting a 404 error here. If there were an exception in the service but includeDetailsInException were set to false, then you'd get a FaultException with nothing but the Exception.Message. I think you need to go look on the machine the service is running on to see if there were any errors or warnings at around the time your client received the exception.In particular, if the service is running on .

NET 2.0 or above, then the default configuration of ASP. NET Health Monitoring will log a warning message to the Application event log when an unhandled exception occurs.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.