Mr Cemper,
Thank you again for your prompt and informative response. I was able to resolve this issue with 2 simple steps: 1. add a self signed cert to the windows server 2016 IIS Manager virtual site; and 2. specify the $domain.$tld in the https url. Previously, I only had $site. And yes, you are correct again, the code I sent you is actually the asmx file which I import to ScriptLink to create the available objects from the WSDL response. The wsdl xml is generated by the web server in response to the application level wsdl import so that I do not need to see the wsdl xml. I realized all too late that this thread should never had been posted on the InterSystems site. My new wsdl import which is working is: https://$site.$domain.$tld/$virtualServer/$WS.asmx. Where the asmx is what I sent you. Think of asmx as pseudo xml. Microsoft claims it is an xml format, but obviously we know it is not.
Thank you again for your prompt advise and assistance, Chris
Thank you Robert for your prompt response, below is my wsdl, please review and provide further advise. Thank you Chris
<%@ WebService Language="C#" CodeBehind="ESPFormsWS.asmx.cs" Class="SSMHAWS.ESPFormsWS" %>
Time zone is an environment level variable. The intersystems data server response is at the application level, so likely returning gmt is correct. The application can adjust based on the environment (geolocation).