Anyone using Tradeshift with NAV2017?
pdj
Member Posts: 643
I have tried to setup NAV2017CU10 and NAV2017CU14 to a Tradeshift sandbox account, as described here:
https://community.dynamics.com/nav/b/navvideos/archive/2015/12/22/how-do-i-use-document-exchange-service-to-send-amp-receive-invoices-in-microsoft-dynamics-nav
However, I keep getting this error when trying to test my connection:
"Authentication failed because the remote party has closed the transport stream."
When I try using NAV2018RTM and NAV2018CU1 and DevPreview it works fine.
Anyone with an idea on how to solve this issue? (without upgrading to NAV2018)
(My guess is that due to lacking support of TLS1.2 in NAV2017, but I'm unable to find any documentation)
https://community.dynamics.com/nav/b/navvideos/archive/2015/12/22/how-do-i-use-document-exchange-service-to-send-amp-receive-invoices-in-microsoft-dynamics-nav
However, I keep getting this error when trying to test my connection:
"Authentication failed because the remote party has closed the transport stream."
When I try using NAV2018RTM and NAV2018CU1 and DevPreview it works fine.
Anyone with an idea on how to solve this issue? (without upgrading to NAV2018)
(My guess is that due to lacking support of TLS1.2 in NAV2017, but I'm unable to find any documentation)
Regards
Peter
Peter
0
Best Answer
-
The problem is fixed in the 2018 May CUs, but you will need to add this line to the CustomSettings.Config:
<add key="SecurityProtocol" value="Tls12"/>Regards
Peter0
Answers
-
Yes, i could connect using NAV2017CU13 NL, but the problem with this version is the layout of the xml. Which could not be uploaded.0
-
Really? I never get this far. Can you do at successful TestConnection to the sandbox API (https://api-sandbox.tradeshift.com/tradeshift/rest/external) or are you connecting to the Tradeshift production URL?
I can see Tradeshift has announced they are switching from TLS1.0 to TLS1.2 by the beginning of 2018 (https://nhssbs.support.tradeshift.com/knowledgebase/article/115000877644) but I don't know if they have done it yet. I thought they might only have done it for the sandbox environment.Regards
Peter0 -
with sandbox i got the same error as you have.
i use: https://api.tradeshift.com/tradeshift/rest/external0 -
Thank you - I will contact Tradeshift and hear if they both are upgraded til TLS1.2 or if only the sandbox is upgraded.Regards
Peter0 -
Microsoft has accepted this problem, and it will be fixed in the May CU.Regards
Peter0 -
The problem is fixed in the 2018 May CUs, but you will need to add this line to the CustomSettings.Config:
<add key="SecurityProtocol" value="Tls12"/>Regards
Peter0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions