Thanks for moving this info over to the forums where we can track it.
Based on the error, I suspect that the error is actually happening earlier during the server connection process. Then the attempt to read/write is failing because none of the connections are functioning.
To trace this, we're probably going to need to get logging working. Unfortunately, since we're still in development we haven't yet tried to get logging working in a .Net Core environment, so it might take some experimentation. Any assistance you can provide is greatly appreciated.
We are using the Common.Logging framework, which is a logging abstraction layer, just like we do for the .Net Desktop SDK. Unfortunately, the core version of this logging framework doesn't support config files, and must be configured in code. Also, we normally log via NLog or log4net, which I don't think are .Net Core compatible.
Do you have a logging framework setup already in your application? Any does it have an adapter for Common.Logging?