Hi Acácio,
I'm having exactly te same error as the one reported by Chris (see below). 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). Is there a way to enfrce the usage of TLS1.1 or 1.2?
Thanks,
Pedro
Error:
Message: The underlying connection was closed: An unexpected error occurred on a send.
Environment Information
eSpaceVer: 354 (Id=120008, PubId=169933, CompiledWith=9.0.1.50)
RequestUrl: https://127.0.0.1/Ind_Integration/_TimerHandler.asmx (Method: POST)
AppDomain: /LM/W3SVC/1/ROOT/Ind_Integration-700-131051900176010862
FilePath: E:\...\PS\running\Ind_Integration.01560225457\
Locale: en-US
DateFormat: dd-MM-yyyy
PID: 49436 ('w3wp', Started='29-03-2016 12:42:23', Priv=2126Mb, Virt=26611Mb)
TID: 2421
Thread Name:
.NET: 4.0.30319.34209
Stack:
[1] The underlying connection was closed: An unexpected error occurred on a send.
at ssInd_Integration.WRefVcmDirectWebService.WRefVcmDirectWebService.DoeFunctie(String inWSfunctie, Boolean inWSfunctieSpecified, WORCVcmBerichtRecord inWSinvoer, Boolean inWSinvoerSpecified, WORCVcmBerichtRecord& outWSDoeFunctieResult)
at ssInd_Integration.ExtendedActions.WebRefVcmDirectWebService_DoeFunctie(HeContext heContext, Boolean[] optionalValuesBitMask, String inWSfunctie, RCVcmBerichtRecord inWSinvoer, RCVcmBerichtRecord& outWSDoeFunctieResult)
at ssInd_Integration.Actions.ActionANVA_DoeFunctie(HeContext heContext, String inParamFileNumber, String inParamPK_DATA, Int32 inParamElementId, Int32 inParamElementType, Boolean inParamSkipTransactionIdValidation, Object& outParamReturn, String& outParamErrorMsg, Int32& outParamErrorCodeId, Boolean& outParamResumeOnError)
[2] Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.FixedSizeReader.ReadPacket(Byte[] buffer, Int32 offset, Int32 count)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.ConnectStream.WriteHeaders(Boolean async)
[3] An existing connection was forcibly closed by the remote host
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)