N
Nithin Sinkaran
Dear All,
we have a web web application which calls an external web-service to consume data which is now failing. Please see the error message below.
The message could not be processed. This is most likely because the action is incorrect or because the message contains an invalid or expired security context token or because there is a mismatch between bindings. The security context token would be invalid if the service aborted the channel due to inactivity. To prevent the service from aborting idle sessions prematurely increase the Receive timeout on the service endpoint's binding.
We have tried adding TLS1.2 compatibility code on our application and even tried changing the framework to 4.7.2 but nothing seems to work from code or our deployed server.
Thanks
Nithin
Nithin
Continue reading...
we have a web web application which calls an external web-service to consume data which is now failing. Please see the error message below.
The message could not be processed. This is most likely because the action is incorrect or because the message contains an invalid or expired security context token or because there is a mismatch between bindings. The security context token would be invalid if the service aborted the channel due to inactivity. To prevent the service from aborting idle sessions prematurely increase the Receive timeout on the service endpoint's binding.
We have tried adding TLS1.2 compatibility code on our application and even tried changing the framework to 4.7.2 but nothing seems to work from code or our deployed server.
Thanks
Nithin
Nithin
Continue reading...
