Phidiax Tech Blog

Issue

Recently, we were updating our client's BizTalk application to use AssureSign. We ran into an error which occurred during the schema generation step:

System.ServiceModel.CommunicationException: An error occurred while making the HTTP request to https://[ServerAddress]/Services/DocumentNOW/v2/documentnow.svc.
This could be due to the fact that the server certificate is not configured properly with HTTP.SYS in the HTTPS case. This could also be caused by a mismatch of the security binding between the client and the server.

This is due to the TLS version used in the AssureSign service, which is not supported in BizTalk server.

There are two options to resolve this issue:

Option 1 - Create an additional registry keys to support TLS 1.2 in BizTalk Server. Please see link BizTalk: TLS 1.2 Issue During Integration with AssureSign Service

Option 2 - Open the AssureSign service in the browser and save the WSDL to a physical file (ex: DocumentNow.wsdl). Now you can generate schema using the WSDL file instead of MEX endpoint. There will be couple missing reference in some schemas.  You will need to review each schema and add one or more missing import statements, as seen below.

 <xs:import schemaLocation=".\DocumentNowWcfService_microsoft_com_wsdl_types.xsd" namespace="http://microsoft.com/wsdl/types/" />

<xs:import schemaLocation=".\DocumentNowWcfService_www_assuresign_net_Services_DocumentNOW_Submit.xsd" namespace="https://www.assuresign.net/Services/DocumentNOW/Submit" />