Create and Print docs from DNG not working - Handshake Error
When trying to "Create and Print Microsoft Word document" from Doors Next Gen, we are getting this error the WebUI:
An error has occurred while processing a server request. The server returned this error code: 500
In the expanded error box, we get these errors: CRRRW7553E - A message that was received from the server indicates and error with no specific handler CRRRS6523E - Unable to print artifact module. Response https/1.1 200 (More info found at entry [xxx] in the RM application server log) In rm.log, we see this error: ibm.rdm.fronting.server.rrs.publish.PublishService - com.ibm.rational.rpe.common.template.api.TemplateException: Could not load template <PUBLICURL>/rm/publish/templateLibrary.printModuleBook. Error is <javax.net.ssl.SSLHandshakerException: Received fatal alert: handshake_failure> In rrdg.log, we get this message: CRRPE3005E The template could not be loaded.. Received fatal alert: handshake_failure We configured debugging using the info in https://www-01.ibm.com/support/docview.wss?uid=swg21694314 and got more messages in rrdg.log but no more detail about the problem.
What is DNG trying to communicate with over SSL? We recently upgraded our Jazz environment to use TLSV1.1. Could that have triggered this problem?
We are using Doors Next Gen V6.0.2. This error occurs when Jazz is hosted on both Windows 2012 and RedHat Linux. |
Accepted answer
When you say the Jazz environment uses TLSv1.1, I understand that it means TLSv1.1 and TLSv1.2. Is it correct? TLSv1.1 only just does not make sense. In this case, I believe you miss a parameter in the configuration - -Dcom.ibm.rational.rpe.tls12only=true. Don't let the name confuse you - rpe is just rrdg in this context.
-Djazz.connector.sslEnabledProtocols="TLSv1.1,TLSv1.2" Rosa Naranjo selected this answer as the correct answer
|
One other answer
Ian Barnard (1.9k●6●13)
| answered Sep 18 '19, 9:29 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
On 6.0.6.1 this problem gives a slightly different error like:
Happily the same solution fixes it :-) but note it's recommended to only use TLSv1.2 these days, so remove TLSv1.1
Comments We've suddenly started receiving this error in both 6.0.6 (PROD) and 6.0.6.1 (CERT environment). We updated to using TLSV1.2 and the problem appears to have occurred a few days later (which was likely the first time anyone attempted to print a report). My research led me to https://www.ibm.com/support/pages/crrpe3005e-sslhandshakeexception-exporting-artifacts-pdf-or-word-ibm-doors-next-generation-was <o:p> </o:p> and we tried that in CERT but it didn't solve the problem. Any other suggestions?
Thank you,
Carol
Hi Carol
You should create a support case.
Regards
Ian
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.