Hi,
We have an ASP.NET web application hosted on a development server, that
invokes web services hosted on an offshore server in India, both being
on the same intranet domain.
The default page of the application makes a call to a service and is
painted successfully. Navigation to any other application page, which
invokes the same service throws the error, "Underlying connection was
closed. An unexpected error occurred on receive". When the default page
itself is refreshed repeatedly, the error does not appear and the page
loads successfully every time.
We then tried hosting the application on other machines and found that
the entire app. was functioning smoothly. The only difference between
the dev box and the others is that the dev server is SSO ENABLED, and
is monitored through SiteMinder.
Several tries later, we noticed yet another discrepancy in behaviour on
the dev server. Occasionally, the other pages of the application also
load successfully without the error, but the immediate next action once
again throws the exception.
There is no pattern or consistency in the appearance of the error, so
we are unable to trace the problem. We tried all the suggested fixes
with KeepAlives, proxy settings, connection timeouts etc. but nothing
worked.
Does anyone know if SSO protection interferes with web service calls,
and if yes, how it should be overridden?
This is holding up project deployment, so require help urgently!!!
Thanks,
Tharika
