Server was unable to process request. --> etc.

R

Ray Stevens

I am getting sporadic errors on a web service call:

"Server was unable to process request. --> An existing connection was
forcibly closed by the remote host."

followed by a series of error messages of the form:

"Server was unable to process request. --> No connection could be made
because thee target machine actively refused it."

This came about when a batch job began using this web service for geocoder
calls and appears to be bursty and random. I suspect the web service is
being overloaded with requests. Is that possible?
 

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. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
473,744
Messages
2,569,484
Members
44,903
Latest member
orderPeak8CBDGummies

Latest Threads

Top