System.Web.Services.Protocols.SoapException
-
:omg:Help! I am getting the following error message when trying to retrieve data using a web service in a C# app. At first before getting this error message, I was able to retrieve data at times (not changing any of the code) and then now it is only giving me this error message when trying to retrieve any of the data. Does anyone know why I am now getting this error message? ---------- Error Message ------------- An unhandled exception of type 'System.Web.Services.Protocols.SoapException' occurred in system.web.services.dll Additional information: Server was unable to process request. --> Catastrophic failure
-
:omg:Help! I am getting the following error message when trying to retrieve data using a web service in a C# app. At first before getting this error message, I was able to retrieve data at times (not changing any of the code) and then now it is only giving me this error message when trying to retrieve any of the data. Does anyone know why I am now getting this error message? ---------- Error Message ------------- An unhandled exception of type 'System.Web.Services.Protocols.SoapException' occurred in system.web.services.dll Additional information: Server was unable to process request. --> Catastrophic failure
Check the server trace log, if enabled. If not, enable it by setting
<trace enabled="true" />
in your Web.config file. Look for the exact exception that is occuring in /trace.axd (rooted from whatever your web application is). This will give you more details. For one thing, make sure you're disposing anyIDisposable
implementations when you're done and that your closing connections, files, etc. Your problem may have nothing to do with those scenarios, but they are common. Just because objects are GC'd automatically doesn't mean that all resources (i.e., native resources like file handles) are released.Microsoft MVP, Visual C# My Articles
-
Check the server trace log, if enabled. If not, enable it by setting
<trace enabled="true" />
in your Web.config file. Look for the exact exception that is occuring in /trace.axd (rooted from whatever your web application is). This will give you more details. For one thing, make sure you're disposing anyIDisposable
implementations when you're done and that your closing connections, files, etc. Your problem may have nothing to do with those scenarios, but they are common. Just because objects are GC'd automatically doesn't mean that all resources (i.e., native resources like file handles) are released.Microsoft MVP, Visual C# My Articles