> If you could enable more verbose logging on your end that might help explain what is going on,
this is essential, in order to see the exact failure code for the https/tls connection failure. without it you simply cannot debug any further. and the original logs does not show it. but it is a critical information. if that was an application log, then either the app needs to switch on more logging, or you need to delve into windows event logger world. to see if the underlying library / api callout had gotten logged those error properly.
this is essential, in order to see the exact failure code for the https/tls connection failure. without it you simply cannot debug any further. and the original logs does not show it. but it is a critical information. if that was an application log, then either the app needs to switch on more logging, or you need to delve into windows event logger world. to see if the underlying library / api callout had gotten logged those error properly.