{"id":50637,"date":"2022-03-22T23:48:46","date_gmt":"2022-03-23T06:48:46","guid":{"rendered":"https:\/\/ephesoft.com\/docs\/?p=50637"},"modified":"2022-03-22T23:48:46","modified_gmt":"2022-03-23T06:48:46","slug":"kb-failed-to-load-keystore-type-jks-with-path-error","status":"publish","type":"post","link":"https:\/\/ephesoft.com\/docs\/kb-failed-to-load-keystore-type-jks-with-path-error\/","title":{"rendered":"KB: Failed to Load Keystore Type [JKS] with Path Error"},"content":{"rendered":"
Applies to<\/strong>: All versions of Transact 2020.1 onward<\/p>\n Users may experience issues connecting to the Ephesoft Transact UI when using Secure Sockets Layer (SSL). The following error may appear in the dcma-all.log:<\/p>\n \u201cFailed to load keystore type [JKS] with path [D:\\Ephesoft\\Certs<\/strong><\/p>\n mydevssl.jks] due to [Illegal character in opaque part at index 2: D:\\Ephesoft\\Certs<\/strong><\/p>\n mydevssl.jks]<\/strong>”<\/p>\n This issue was caused by an extra slash between Certs<\/strong> and the .jks<\/strong> file in the server.xml<\/strong> file (\\Certsmydevssl.jks<\/strong>).<\/p>\n To resolve this issue, update the path of keystoreFile<\/strong> in the server.xml <\/strong>to D:\\Ephesoft\\Certs\\mydevssl.jks<\/strong>.<\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":" Applies to: All versions of Transact 2020.1 onward Issue Users may experience issues connecting to the Ephesoft Transact UI when […]<\/p>\n","protected":false},"author":93,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"yoast_head":"\n<\/a>Issue<\/h2>\n
<\/a>Root Cause<\/h2>\n
<\/a>Solution<\/h2>\n