Howdy, Stranger!
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
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 304 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Unusual behavior calling external web service NAV2013
jeighsohn
Member Posts: 14
Hi all,
I've written some functions to call a provider's web service from NAV2013 and process the response. Thanks to great examples found here on Mibuso, it all works... for the most part. Here is where it gets weird.
The first time I run either of the two functions I created after a NAV service restart, it always fails. The second time it is run, it works. The failure message is typically something like (it can vary between this and a more specific ssl/tls message).
Thanks to searching the forum, this appears to be related to TLS/SSL. I've tried adding the below line of code as suggested by other posts on this topic (to specify TLS 1.2), but it doesn't address the issue.
The calls always fail the first time they are run after a service is restart (we restart all of our services every night). Anyone have any other ideas as to what I could try?
One of the calls is initiated by a user (they click an action), and I suppose I could train them to "just try again" but that seems dumb. The other call is run via NAS and it seems to correct itself (since it's a recurring job).
I've written some functions to call a provider's web service from NAV2013 and process the response. Thanks to great examples found here on Mibuso, it all works... for the most part. Here is where it gets weird.
The first time I run either of the two functions I created after a NAV service restart, it always fails. The second time it is run, it works. The failure message is typically something like (it can vary between this and a more specific ssl/tls message).
Microsoft Dynamics NAV --------------------------- This message is for C/AL programmers: A call to System.Net.HttpWebRequest.GetResponse failed with this message: An existing connection was forcibly closed by the remote host --------------------------- OK ---------------------------
Thanks to searching the forum, this appears to be related to TLS/SSL. I've tried adding the below line of code as suggested by other posts on this topic (to specify TLS 1.2), but it doesn't address the issue.
ServicePointManager.SecurityProtocol := SecurityProtocolType.Tls12;
The calls always fail the first time they are run after a service is restart (we restart all of our services every night). Anyone have any other ideas as to what I could try?
One of the calls is initiated by a user (they click an action), and I suppose I could train them to "just try again" but that seems dumb. The other call is run via NAS and it seems to correct itself (since it's a recurring job).
0