topic Re: issue with the SAS Enterprise Miner 15.3 client version - Not opening in Administration and Deployment

issue with the SAS Enterprise Miner 15.3 client version - Not opening

siddhu1 — Mon, 21 Oct 2024 11:15:50 GMT

Hi,
Recently installed SAS E-Miner 15.3 client version in the Citrix windows machine and it was successfu.

But when trying to open it , the below screenshot appear.

The sas-environment URL was appearing fine, below is the screenshot of the same.

When checked in the em_* logs, below is the error found.

ERROR: ExeProc::ExeandDisplay::GetStdHandle::NULL=298
Thu Oct 17 07:58:04 2024
INFO: ExeProc::ReadFromPipe=Standard output
2024-10-17 07:58:16,547 [main] FATAL com.sas.svcs.environment.xml.XmlEnvironmentManager [] - Unable to properly initialize EnvironmentManager (IOException) using the provided URL (https://clrv0000290925.ic.ing.net:8343/sas/sas-environment.xml)javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at sun.security.ssl.Alert.createSSLException(Alert.java:131) ~[?:?] at sun.security.ssl.TransportContext.fatal(TransportContext.java:360) ~[?:?] at sun.security.ssl.TransportContext.fatal(TransportContext.java:303) ~[?:?] at sun.security.ssl.TransportContext.fatal(TransportContext.java:298) ~[?:?] at sun.security.ssl.CertificateMessage$T13CertificateConsumer.checkServerCerts(CertificateMessage.java:1357) ~[?:?] at sun.security.ssl.CertificateMessage$T13CertificateConsumer.onConsumeCertificate(CertificateMessage.java:1232) ~[?:?] at sun.security.ssl.CertificateMessage$T13CertificateConsumer.consume(CertificateMessage.java:1175) ~[?:?] at sun.security.ssl.SSLHandshake.consume(SSLHandshake.java:392) ~[?:?] at sun.security.ssl.HandshakeContext.dispatch(HandshakeContext.java:443) ~[?:?] at sun.security.ssl.HandshakeContext.dispatch(HandshakeContext.java:421) ~[?:?] at sun.security.ssl.TransportContext.dispatch(TransportContext.java:183) ~[?:?] at sun.security.ssl.SSLTransport.decode(SSLTransport.java:172) ~[?:?] at sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1511) ~[?:?] at sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1421) ~[?:?] at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:456) ~[?:?] at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:427) ~[?:?] at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:580) ~[?:?] at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:201) ~[?:?] at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1618) ~[?:?] at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1546) ~[?:?] at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:250) ~[?:?] at java.net.URL.openStream(URL.java:1165) ~[?:?] at com.sas.svcs.environment.xml.XmlEnvironmentManager.<init>(XmlEnvironmentManager.java:107) ~[sas.svcs.environment.jar:904800.0.0.20221221190000_v940m8] at com.sas.swing.login.negotiate.ValidatingNegotiator.getEnvironments(ValidatingNegotiator.java:72) ~[sas.swing.login.jar:904800.0.0.20221221190000_v940m8] at com.sas.swing.login.EnvironmentLogonManager.getLogonTargets(EnvironmentLogonManager.java:172) ~[sas.swing.login.jar:904800.0.0.20221221190000_v940m8] at com.sas.swing.login.visual.SwingEnvironmentLogonManager.fireLogon(SwingEnvironmentLogonManager.java:398) ~[sas.swing.login.jar:904800.0.0.20221221190000_v940m8] at com.sas.analytics.eminer.visuals.Main.handleApplicationSignon(Main.java:1368) ~[sas.analytics.emui.jar:1500300.1.0.20230111190000_d4dm153] at com.sas.analytics.eminer.visuals.Main.main(Main.java:735) ~[sas.analytics.emui.jar:1500300.1.0.20230111190000_d4dm153]Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:439) ~[?:?] at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:306) ~[?:?] at sun.security.validator.Validator.validate(Validator.java:264) ~[?:?] at sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:313) ~[?:?] at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:222) ~[?:?] at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:129) ~[?:?] at sun.security.ssl.CertificateMessage$T13CertificateConsumer.checkServerCerts(CertificateMessage.java:1341) ~[?:?] ... 23 moreCaused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at sun.security.provider.certpath.SunCertPathBuilder.build(SunCertPathBuilder.java:148) ~[?:?] at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:129) ~[?:?] at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:297) ~[?:?] at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:

Can someone help on this?

Thanks in Advance,
Siddhu

Re: issue with the SAS Enterprise Miner 15.3 client version - Not opening

JackMcGuire — Mon, 21 Oct 2024 12:02:23 GMT

Hi Siddhu,

From the error in the log file, it looks to me that your SAS Web Server is configured for HTTPS with a TLS certificate that is not trusted by the client machine where SAS Enterprise Miner is running.

Below are a couple of links with detailed steps for trusting the TLS certificates which will hopefully help:

Many thanks,

Jack

Re: issue with the SAS Enterprise Miner 15.3 client version - Not opening

JuanS_OCS — Mon, 28 Oct 2024 09:37:23 GMT

Hello @siddhu1 ,

on top of what was indicated by @JackMcGuire , the first error points to "Unable to properly initialize EnvironmentManager".

Is your environment manager deployed and tested properly? Also, please mind that Environment Manager has a different Certificate store file than the rest of the SAS platform. You might want to add your CA, Intermediate and final certificates there too.

Side note: you might want to edit and mask the hostname/dns in the shared log file, not only the screenshot

Re: issue with the SAS Enterprise Miner 15.3 client version - Not opening

siddhu1 — Tue, 19 Nov 2024 12:54:31 GMT

Hi,

Sorry for replying late.

Updated the certificates required, but getting some thing different error.

The Error is as follows:
INFO: Launcher::Run::start::classpath=-cp "O:\SASHome\SASVersionedJarRepository\eclipse\plugins\sas.launcher.jar"
Tue Nov 19 12:31:53 2024
INFO: Launcher::Run::start::mainclass=com.sas.analytics.eminer.visuals.Main
Tue Nov 19 12:31:53 2024
ERROR: ExeProc::ExeandDisplay::GetStdHandle::NULL=298
Tue Nov 19 12:31:53 2024
INFO: ExeProc::ReadFromPipe=Standard output
2024-11-19 12:33:38,483 [AWT-EventQueue-0] ERROR com.sas.swing.login.visual.SwingEnvironmentLogonManager [] - Unexpected exception when processing environment defaultorg.springframework.web.client.ResourceAccessException: I/O error on POST request for "https://xxxxxx.x.net:8343/SASLogon/v1/tickets": cannot retry due to server authentication, in streaming mode; nested exception is java.net.HttpRetryException: cannot retry due to server authentication, in streaming mode at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:791) ~[spring-web.jar:5.3.34] at org.springframework.web.client.RestTemplate.execute(RestTemplate.java:717) ~[spring-web.jar:5.3.34] at org.springframework.web.client.RestTemplate.exchange(RestTemplate.java:608) ~[spring-web.jar:5.3.34] at com.sas.svcs.security.authentication.client.AuthenticationClient.doLogon(AuthenticationClient.java:170) ~[sas.svcs.security.authentication.client.jar:904800.0.0.20221221190000_v940m8] at com.sas.svcs.security.authentication.client.AuthenticationClient.logon(AuthenticationClient.java:242) ~[sas.svcs.security.authentication.client.jar:904800.0.0.20221221190000_v940m8] at com.sas.swing.login.session.BasicLogonSessionHandler.logon(BasicLogonSessionHandler.java:163) ~[sas.swing.login.jar:904800.0.0.20221221190000_v940m8] at com.sas.swing.login.LogonUtil.logon(LogonUtil.java:146) ~[sas.swing.login.jar:904800.0.0.20221221190000_v940m8] at com.sas.swing.login.LogonUtil.logon(LogonUtil.java:177) ~[sas.swing.login.jar:904800.0.0.20221221190000_v940m8] at com.sas.swing.login.visual.SwingEnvironmentLogonManager$2.commit(SwingEnvironmentLogonManager.java:186) ~[sas.swing.login.jar:904800.0.0.20221221190000_v940m8] at com.sas.swing.login.visual.SwingLogon.okButtonPressed(SwingLogon.java:977) ~[sas.swing.login.jar:904800.0.0.20221221190000_v940m8] at com.sas.swing.login.visual.SwingLogon.access$300(SwingLogon.java:118) ~[sas.swing.login.jar:904800.0.0.20221221190000_v940m8] at com.sas.swing.login.visual.SwingLogon

Could someone help on this.
Thanks in Advance.

Kind Regards,

Siddhu1

Re: issue with the SAS Enterprise Miner 15.3 client version - Not opening

siddhu1 — Tue, 26 Nov 2024 10:29:02 GMT

Hi,
Any help on this issue, would be highly appreciated.

Kind Regards,

Siddhu1

Re: issue with the SAS Enterprise Miner 15.3 client version - Not opening

gwootton — Wed, 27 Nov 2024 14:42:04 GMT

Looks like you're failing to authenticate to SASLogon. Are you able to authenticate through a browser going to https://sas.example.com:8343/SASLogon?