Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K 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
- 262 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 SQL Performance
- 33 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
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
NAV 2013 - .Net Integration SSL/TLS Error
remco_rausch
Member Posts: 68
Hi,
We integrate with Hermes Courier Services from NAV using a home written C# project that communicates with a Hermes SOAP Web Service. It is called on warehouse shipment release.
This runs on 3 NAV services:
Service 1: Client Service - Windows Credential Type
Service 2: Client Service - NavUserPassword
Service 3: NAS Service - Windows Credential Type
All service run on the same machine and all have the same service account setup against them.
This solution has been working fine for around 2 months but stopped working last Tuesday. We restarted all the NAV Services and rebooted the machine. The result being:
Service 1: Works fine for a period but will then stop working
Service 2: Has been fine since, no reported problems
Service 3: Works for around 5 shipments and then falls over
The error message that it is falling over on for all services is as follows:
Event Viewer:
"A fatal alert was received from the remote endpoint. The TLS protocol defined fatal alert code is 40."
Message from Hermes Web Service Class (i.e. code running on our side of things):
'Error in Communication: Could not establish secure channel for SSL/TLS with authority 'www.hermes-europe.co.uk'.'
The checks we have done so far:
1. Install the NAS on a separate server, result is the same
2. Check over all the code for modifications, nothing has been modified for the last month. Either NAV code or the C#
3. Check the Server for Windows Updates, none installed since September (I know.....)
4. Checked with Hermes to see if they had any other customers with problems but they have had not.
It is not a data issue as when a shipment falls over on the NAS it can be immediately released manually using the standard client.
My question is as follows, the SSL/TLS error we receive has normally got to do with certificates, we have checked these and they seem to be fine, also not changed for about a month. What is the difference between how the different service run, is there some sort of caching that could take place against services and certificates? It just seems very weird that one service falls over nearly straightaway, another falls over randomly and the third has been stable the whole time.
Does anyone have any ideas as I am ](*,) .
Thanks!
Remco
We integrate with Hermes Courier Services from NAV using a home written C# project that communicates with a Hermes SOAP Web Service. It is called on warehouse shipment release.
This runs on 3 NAV services:
Service 1: Client Service - Windows Credential Type
Service 2: Client Service - NavUserPassword
Service 3: NAS Service - Windows Credential Type
All service run on the same machine and all have the same service account setup against them.
This solution has been working fine for around 2 months but stopped working last Tuesday. We restarted all the NAV Services and rebooted the machine. The result being:
Service 1: Works fine for a period but will then stop working
Service 2: Has been fine since, no reported problems
Service 3: Works for around 5 shipments and then falls over
The error message that it is falling over on for all services is as follows:
Event Viewer:
"A fatal alert was received from the remote endpoint. The TLS protocol defined fatal alert code is 40."
Message from Hermes Web Service Class (i.e. code running on our side of things):
'Error in Communication: Could not establish secure channel for SSL/TLS with authority 'www.hermes-europe.co.uk'.'
The checks we have done so far:
1. Install the NAS on a separate server, result is the same
2. Check over all the code for modifications, nothing has been modified for the last month. Either NAV code or the C#
3. Check the Server for Windows Updates, none installed since September (I know.....)
4. Checked with Hermes to see if they had any other customers with problems but they have had not.
It is not a data issue as when a shipment falls over on the NAS it can be immediately released manually using the standard client.
My question is as follows, the SSL/TLS error we receive has normally got to do with certificates, we have checked these and they seem to be fine, also not changed for about a month. What is the difference between how the different service run, is there some sort of caching that could take place against services and certificates? It just seems very weird that one service falls over nearly straightaway, another falls over randomly and the third has been stable the whole time.
Does anyone have any ideas as I am ](*,) .
Thanks!
Remco
0
Comments
A possible solution may be here
http://www.zdnet.com/article/microsoft-warns-of-problems-with-schannel-security-update/
hope this helps
There are several articles about this phenomenon on the internet. Simply search for "The TLS protocol defined fatal alert code is 40"
Oki
I had already googled the message and come across this article, that update came out in November and we have not installed updates since September.