Are you seeing any errors inside the CustomReportsEngine.log or WebServer.log?
Are you seeing any errors inside the CustomReportsEngine.log or WebServer.log?
Hi Chris,
Below are the errors on the log.
CustomReportsEngine.log :-
1028 247 02/20 10:49:57 : SEVERE: failed to decrypt token, error rThe driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "Unexpected rethrowing".]
1028 252 02/20 10:49:57 : SEVERE: authentication failed, error rThe driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "Unexpected rethrowing".]
1028 247 02/20 10:49:57 : SEVERE: authentication failed, error rThe driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "Unexpected rethrowing".]
1028 252 02/20 10:49:57 : completed request for url [/datasets/2b366703-52e1-4775-8047-1f4cfa13d2db/data], user snull]
1028 247 02/20 10:49:57 : completed request for url [/datasets/2b366703-52e1-4775-8047-1f4cfa13d2db/data], user snull]
1028 250 02/20 10:49:57 : SEVERE: failed to decrypt token, error rThe driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "Unexpected rethrowing".]
1028 250 02/20 10:49:57 : SEVERE: authentication failed, error rThe driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "Unexpected rethrowing".]
1028 250 02/20 10:49:57 : completed request for url [/datasets/2b366703-52e1-4775-8047-1f4cfa13d2db/data], user snull]
1028 251 02/20 10:49:58 : SEVERE: failed to decrypt token, error rThe driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "Unexpected rethrowing".]
1028 251 02/20 10:49:58 : SEVERE: authentication failed, error rThe driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "Unexpected rethrowing".]
1028 251 02/20 10:49:58 : completed request for url [/datasets/METRICS_DEFAULT/data], user snull]
1028 239 02/20 10:49:58 : SEVERE: failed to decrypt token, error rThe driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "Unexpected rethrowing".]
1028 239 02/20 10:49:58 : SEVERE: authentication failed, error rThe driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "Unexpected rethrowing".]
WebServer.log:-
13072 43e4 02/20 10:49:56 ### QSDKInitializeWithLoginFlag() - Registry nEnablePreInstallQCMD is not present and trying to talk to same CS. So setting enable pre install mode: m0]
13072 43e4 02/20 10:49:56 ### QSDKInitializeWithLoginFlag() - Username from token: tCMC\jeffreybusz.admin]
13072 43e4 02/20 10:49:56 ### Response from QSDK Server failed with Error code o0x9] Error string QSDK Server failed to find a connection to the Commserver, Relogin required]
13072 43e4 02/20 10:49:56 ### Retrying Connection to QSDK Server
13072 43e4 02/20 10:49:56 ### readAndDescrambleData()() - File Handle is NULL:ErrorNQERROR_API_OPENSESSFILEFAILED]
Hi @Allan0105 ,
The short term workaround is to run the <install_folder>\certificates\fixtls.cmd in an elevated command prompt on the web server and cycle Tomcat.
The proper fix as noted, is to apply the latest SQL service packs to the SQL instances on the Commserve and web/metrics server.
They both need to be patched because the web/metrics server does reach out to the Commserve DB for authentication.
So can you run this command on the webserver(s) and then restart tomcat please:
<install_folder>\certificates\fixtls.cmd
Let me know
Best Regards,
Sebastien
There is a fix for this “Unexpected rethrowing” issue. What service pack are you on?
Thanks Sebastien, it was working before, not sure what broke up, is only solution is to upgrade to FR28 ?
Since FR25 is not supported anymore you would need to upgrade to the next LTS version which is FR28.
Since FR25 is not supported anymore you would need to upgrade to the next LTS version which is FR28.
My bad, plan is on for SP28 upgrade, but it may take some days so i was thinking to fix this issue as upgrade may take some days, is no other short time fix.
Since FR25 is not supported anymore you would need to upgrade to the next LTS version which is FR28.
My bad, plan is on for SP28 upgrade, but it may take some days so i was thinking to fix this issue as upgrade may take some days, is no other short time fix.
Upgraded to SP28 which fixed the command center issue and commserve windows os upgraded to 2019.