Asked by:
HPC client caught error when connecting to HPC 2016 Head node: ... An unexpected error occurred on a send ...

Question
-
The error is:
"An error occurred while sending the request: The underlying connection was closed: An unexpected error occurred on a send. "
HPC head node version is HPC Pack 2016: 5.1.6086.0
HPC client uses SDK 5.1.6124.
Actually we have test environment and works fine.
But the production environment has this issue.
May I know how to understand and diagnose since the error is blocking us.
Thanks.
Friday, March 1, 2019 10:01 PM
All replies
-
Hi Daniel, would it be possible to upgrade the cluster to update 2 at least?
And do you have the call stack when this error happens? Is this error happens on the headnode if you put the client app on the headnode?
Qiufang Shi
Sunday, March 3, 2019 8:20 AM -
Hi Qiufang,
As you suggested, we got the stack trace.
<EventData>
<Data>MyApplicationName.exe[13640] (ERROR): {21180004} Error when creating the Windows HPC Server service session: Microsoft HPC Server QuIC Network Engine caught an error: System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
at System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult)
--- End of inner exception stack trace ---
at System.Net.TlsStream.EndWrite(IAsyncResult asyncResult)
at System.Net.ConnectStream.WriteHeadersCallback(IAsyncResult ar)
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
--- End of inner exception stack trace ---
at Microsoft.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at Microsoft.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccess(Task task)
at Microsoft.Hpc.Scheduler.Session.Session.CreateSession(SessionStartInfo startInfo, Binding binding)
at QneHpcClrClient.HpcApi.InitSession(String headNode, String serviceName, Dictionary`2 serviceParms)
at QNetworkEngineClientMsHpcServerClrBridgeImplGc..ctor(basic_string<char\,std::char_traits<char>\,std::allocator<char> >* headNode, basic_string<char\,std::char_traits<char>\,std::allocator<char> >* serviceName, map<QString\,QString\,std::less<QString>\,std::allocator<std::pair<QString const \,QString> > >* params, basic_string<char\,std::char_traits<char>\,std::allocator<char> >* configurationNode)
at QNetworkEngineClientMsHpcServerClrBridgeImpl.{ctor}(QNetworkEngineClientMsHpcServerClrBridgeImpl* , basic_string<char\,std::char_traits<char>\,std::allocator<char> >* headNode, basic_string<char\,std::char_traits<char>\,std::allocator<char> >* serviceName, map<QString\,QString\,std::less<QString>\,std::allocator<std::pair<QString const \,QString> > >* params, basic_string<char\,std::char_traits<char>\,std::allocator<char> >* configurationNode)</Data>
</EventData>Second, this error happened on the head node too if we put the client app on the headnode. Only happened on production environment not testing environment.
So far we did not upgrade to update 2 since the error did not happen on the testing environment.
Please let us know your suggestions.
Thanks.
- Edited by danieljzhang Monday, March 4, 2019 11:05 PM
Monday, March 4, 2019 11:00 PM -
Hi danieljzhang,
Since it is SOA session job, could you run the built-in EchoClient.exe on the client and the head node to see the issue reproes?
The exception looks a failure when the session client was initiating HTTPS connection to the naming service on the head node. Is there any firewall blocking HTTPS at port 443?
Regards,
Yutong Sun
Tuesday, March 5, 2019 7:36 AM -
Hi Yutong,
Thanks for your suggestions.
We are able to run EchoClient.exe both on compute node and head node.
But our app failed on compute node and head node on production environment.
port 443 is listening too. See:
Active Connections
Proto Local Address Foreign Address State PID
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 900
TCP 0.0.0.0:383 0.0.0.0:0 LISTENING 3376
TCP 0.0.0.0:443 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:1801 0.0.0.0:0 LISTENING 2404
TCP 0.0.0.0:1856 0.0.0.0:0 LISTENING 2684
TCP 0.0.0.0:2103 0.0.0.0:0 LISTENING 2404
TCP 0.0.0.0:2105 0.0.0.0:0 LISTENING 2404
TCP 0.0.0.0:2107 0.0.0.0:0 LISTENING 2404
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING 96
TCP 0.0.0.0:4445 0.0.0.0:0 LISTENING 3192
TCP 0.0.0.0:4750 0.0.0.0:0 LISTENING 5484
TCP 0.0.0.0:5800 0.0.0.0:0 LISTENING 2412
TCP 0.0.0.0:5802 0.0.0.0:0 LISTENING 2412
TCP 0.0.0.0:5969 0.0.0.0:0 LISTENING 2412
TCP 0.0.0.0:5970 0.0.0.0:0 LISTENING 2412
TCP 0.0.0.0:5974 0.0.0.0:0 LISTENING 2692
TCP 0.0.0.0:5985 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:5999 0.0.0.0:0 LISTENING 2412
TCP 0.0.0.0:6730 0.0.0.0:0 LISTENING 6396
TCP 0.0.0.0:7997 0.0.0.0:0 LISTENING 2412
TCP 0.0.0.0:7998 0.0.0.0:0 LISTENING 2684
TCP 0.0.0.0:8089 0.0.0.0:0 LISTENING 2900
TCP 0.0.0.0:8677 0.0.0.0:0 LISTENING 2668
TCP 0.0.0.0:9087 0.0.0.0:0 LISTENING 3552
TCP 0.0.0.0:9090 0.0.0.0:0 LISTENING 2392
TCP 0.0.0.0:9092 0.0.0.0:0 LISTENING 2392
TCP 0.0.0.0:9093 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:9094 0.0.0.0:0 LISTENING 2392
TCP 0.0.0.0:9095 0.0.0.0:0 LISTENING 3552
TCP 0.0.0.0:9096 0.0.0.0:0 LISTENING 4716
TCP 0.0.0.0:9182 0.0.0.0:0 LISTENING 20844
TCP 0.0.0.0:9794 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:9893 0.0.0.0:0 LISTENING 2424
TCP 0.0.0.0:47001 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:49664 0.0.0.0:0 LISTENING 564
TCP 0.0.0.0:49665 0.0.0.0:0 LISTENING 516
TCP 0.0.0.0:49837 0.0.0.0:0 LISTENING 1276
TCP 0.0.0.0:49838 0.0.0.0:0 LISTENING 724
TCP 0.0.0.0:49850 0.0.0.0:0 LISTENING 1216
TCP 0.0.0.0:49872 0.0.0.0:0 LISTENING 2404
TCP 0.0.0.0:49911 0.0.0.0:0 LISTENING 2644
TCP 0.0.0.0:49958 0.0.0.0:0 LISTENING 724
TCP 0.0.0.0:49959 0.0.0.0:0 LISTENING 716
TCP 0.0.0.0:50089 0.0.0.0:0 LISTENING 11916
TCP xxx.xxx.xx4.238:139 0.0.0.0:0 LISTENING 4
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.200:54375 ESTABLISHED 4
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.200:54376 ESTABLISHED 4
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.200:54397 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.200:54398 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.200:54401 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.200:54402 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.200:54405 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.200:54411 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.200:54412 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.238:49899 ESTABLISHED 4
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.238:61163 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.238:61164 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.238:61165 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.238:61168 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.238:61171 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.238:61172 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.238:61182 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.238:61183 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.238:61185 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.238:61188 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.238:61193 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.238:61194 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.238:61195 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.238:61212 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.238:61218 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.238:61219 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.238:61220 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.238:61224 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.238:61227 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.238:61228 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.238:61229 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.238:61232 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.238:61245 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.238:61246 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.238:61247 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.238:61252 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.238:61253 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.238:61254 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.238:61257 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.238:61258 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.238:61264 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.246:49863 ESTABLISHED 4
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.246:52389 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.246:52391 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.246:52392 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.246:52393 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.246:52394 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.246:52396 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.246:52398 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.246:52400 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.246:52401 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.246:52403 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.246:52404 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.246:52420 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.246:52423 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx4.246:52427 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.7:57528 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.7:57534 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.7:57535 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.7:57536 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.7:57537 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.7:57538 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.7:57543 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.7:57545 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.7:57551 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.7:57553 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.7:57574 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.7:57577 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.7:57578 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.7:57579 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.7:57580 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.7:61745 ESTABLISHED 4
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.8:60502 ESTABLISHED 4
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.8:63840 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.8:63845 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.8:63846 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.8:63847 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.8:63848 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.8:63849 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.8:63850 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.8:63854 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.8:63855 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.8:63858 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.8:63877 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.8:63880 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.8:63885 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.8:63886 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.8:63887 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.9:53109 ESTABLISHED 4
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.9:60209 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.9:60216 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.9:60217 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.9:60218 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.9:60219 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.9:60221 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.9:60222 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.9:60225 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.9:60226 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.9:60228 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.9:60249 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.9:60253 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.9:60258 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.10:56364 ESTABLISHED 4
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.10:56618 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.10:56619 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.10:56620 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.10:56623 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.10:56625 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.10:56627 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.10:56628 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.10:56629 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.10:56630 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.10:56631 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.10:56632 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.11:54234 ESTABLISHED 4
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.11:63749 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.11:63754 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.11:63755 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.11:63756 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.11:63758 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.11:63759 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.11:63760 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.11:63765 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.11:63767 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.11:63784 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.11:63785 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.11:63786 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.11:63788 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.11:63789 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.11:63794 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.11:63797 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.11:63798 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.12:50821 ESTABLISHED 4
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.12:65133 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.12:65134 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.12:65135 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.12:65136 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.12:65137 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.12:65139 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.12:65140 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.12:65141 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.12:65142 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.12:65145 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.12:65165 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.12:65180 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.12:65181 TIME_WAIT 0
TCP xxx.xxx.xx4.238:443 xxx.xxx.xx6.12:65182 TIME_WAIT 0
TCP xxx.xxx.xx4.238:445 xxx.xxx.xx4.200:54391 ESTABLISHED 4
TCP xxx.xxx.xx4.238:445 xxx.xxx.xx4.200:54392 ESTABLISHED 4
TCP xxx.xxx.xx4.238:445 xxx.xxx.xx4.200:54393 ESTABLISHED 4
TCP xxx.xxx.xx4.238:445 xxx.xxx.xx4.200:54394 ESTABLISHED 4
...
...
TCP 127.0.0.1:1169 0.0.0.0:0 LISTENING 2956
TCP 127.0.0.1:4000 0.0.0.0:0 LISTENING 3228
TCP 127.0.0.1:4000 127.0.0.1:49985 ESTABLISHED 3228
TCP 127.0.0.1:17473 0.0.0.0:0 LISTENING 11732
TCP 127.0.0.1:49985 127.0.0.1:4000 ESTABLISHED 3244
TCP 127.0.0.1:59949 0.0.0.0:0 LISTENING 7792
...
Anything else can be wrong?
Next step we will try to compare the loaded dlls for our application on test environment and production environment.
But if you have other diagnosing methods, please let us know.
Thank you very much.
Tuesday, March 5, 2019 11:33 PM -
Hi danieljzhang,
If your application is targeting .Net Framework version 4.5.2 or earlier, you may try to add the following registries for the error could be caused by TLS version mismatch between your application and the service on the production server. Refer this doc for details.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]
"SystemDefaultTlsVersions"=dword:00000001
"SchUseStrongCrypto"=dword:00000001[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319]
"SystemDefaultTlsVersions"=dword:00000001
"SchUseStrongCrypto"=dword:00000001Regards,
Yutong Sun
Wednesday, March 6, 2019 2:10 AM -
Hi Yutong and Qiufang,
Thank you very much for your helps. The registry changes that Yutong suggested works!
May I ask how we can check the default of version of TLS on Windows Server 2016? Since our testing and production environment has different behaviors. We need document it for future reference.
Again, thank you very much. Your helps are deeply appreciated.- Edited by danieljzhang Thursday, March 7, 2019 10:57 PM
Wednesday, March 6, 2019 10:46 PM