Is there a way to enfrce the usage of TLS1.1 or 1.2? After discussing and troubleshooting it with the service provider they concluded that we are negotiating on TLS1.0 and they have TLS1.0 disabled on their end (only 1.1 and 1.2 are enabled). I'm having exactly te same error as the one reported by Chris (see below). Other times, you need to read the lines starting with "at" (which show the lines of code where the problem happens - the "call stack"). Most of the times you get very valuable information just by reading the first part of each (meaning: the lines that don't start with "at"). This means the thing with the lowest number (the "outmost exception") is the error that was caused ultimately by the biggest number ("the inmonst exception"). "the remote party has closed the transport stream "īy the way, this is a generic mechanism you can use when reading such error messages: if you find things such as, in your error stacks, each bigger number is what is called an "inner exception". The base error is "connection was closed while sending information" Actually, your error message gives you some more details: Authentication failed because the remote party has closed the transport stream.Īt .StartReadFrame(Byte buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)Īt .StartReceiveBlob(Byte buffer, AsyncProtocolRequest asyncRequest)Īt .ForceAuthentication(Boolean receiveFirst, Byte buffer, AsyncProtocolRequest asyncRequest)Īt .ProcessAuthentication(LazyAsyncResult lazyResult)Īt (ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)Īt (ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)Īt (ExecutionContext executionContext, ContextCallback callback, Object state)Īt (LazyAsyncResult result)Īt (Byte buffer, Int32 offset, Int32 size)Īt (Boolean async)īy looking at the stack I'd say it's the exact same explanation. The underlying connection was closed: An unexpected error occurred on a send.Īt .WebClientProtocol.GetWebResponse(WebRequest request)Īt .SoapHttpClientProtocol.Invoke(String methodName, Object parameters)Īt 2BGetVehicleByVRM(String inWSstrUserName, Boolean inWSstrUserNameSpecified, String inWSstrPassword, Boolean inWSstrPasswordSpecified, String inWSstrClientRef, Boolean inWSstrClientRefSpecified, String inWSstrClientDescription, Boolean inWSstrClientDescriptionSpecified, String inWSstrKey1, Boolean inWSstrKey1Specified, String inWSstrVRM, Boolean inWSstrVRMSpecified, String inWSstrVersion, Boolean inWSstrVersionSpecified, XmlElement& outWSstrB2BGetVehicleByVRMResult) You may see errors in the remote server similar to this one (e.g. ![]() application pool recycling or crashes that interrupt logic that may be runnning.Ī network layer is cutting the network connection half-way. If another OutSystems Platform is on the receiving end (meaning: the web call is to an OutSystems Platform) you may want to look here. ![]() The request is taking too long to run and the server "times it out". If you are the other party or want to help: common causes on the other side for these errors are: Resolving such a problem cannot be done on the caller side (your application) - you need to work with the party that provides the service for you. ![]() While the application was waiting for the response, the remote server cut the connection. Your application (the caller) sent the request Errors like these happen because the remote server (to which the call was being made) did not deliver a response to your request and cut the connection before an answer could be sent.
0 Comments
Leave a Reply. |