Interested in creating and selling training? You pick the price, 50/50 revenue share, and you own the content. Find out more at
I am working with NAV 2018, installed windows server 2012 R2 standard.
I have created a a few years ago an integraion with an external webService. it is working perfectly, but they are changing the security protocol to use TLS 1.2 or 1.3. The system administrators from the webService gave me a new UOLR fortesting that we can connect via TLS1.2 or higher. I'm jsut changing the URL in my development, and I get this error(filtering traffic with fiddler):
This is the error in NAV:
"Error in call System._ComObjectSend with the message: Cannot finde the specified resource"
The code is like this:
ServicePointManager.SecurityProtocol := SecurityProtocolType.Tls13;
IF ISCLEAR(XMLHTTP) THEN
XMLHTTP.setRequestHeader('Content-Type: ', 'application/x-www-form-urlencoded');
XMLText := 'xml_in=' + XMLDocDotNet.OuterXml;
It worries me that may be it will be an issue with the server, or any setting of it..
Any hint? Thank you all
I've changed the develompnet to use DOTNET instead of automation. This is the new code:
HttpWebRequest := HttpWebRequest.Create('https://express5.xxxx.com/expressconnect/shipping/ship');
credentials := credentials.NetworkCredential(User,PSWD);
HttpWebRequest.Credentials := credentials;
HttpWebRequest.Accept := 'application/x-www-form-urlencoded';
HttpWebRequest.ContentType := 'application/x-www-form-urlencoded';
StreamWriter := StreamWriter.StreamWriter(HttpWebRequest.GetRequestStream);
HttpWebResponse := HttpWebRequest.GetResponse;
response := HttpWebResponse.ToString;
And I get this error:
"...cannto create a secure channel..."
I'm starting to get quite desperate...
Maybe do you need to receive a secure token first (based on login & password because I can see the "https://e..")? like below :
AuthorizationString := STRSUBSTNO(AuthTemplate, Login, Password);TempBlob.WriteAsText(AuthorizationString, TEXTENCODING::UTF8);AuthorizationString := TempBlob.ToBase64String();WebRequestMgt.AddHeader('Authorization', 'Basic ' + AuthorizationString);
Thanks for your answer. I've just asked to the sysetm providor about this issue, but the authentication remains he same as before, user and password. They've jsut changed TLS 1.0 and 1.1, to 1.2 and 1.3