About RupaJ

RupaJ · ‎08-10-2018

Hello, I am working on install and configuring SAS 9.5 M5 on a windows server(windows 2012 R2 - physical). It's a single machine install with both server and clients installed on the same machine. Now the previous install of SAS 9.4 M3 was done on a different machine by a different person and I have to find what components were installed. I tried looking for Lev1 folder and I surprisingly did not find that. How do I know what tiers (meta/compute/midtier) were installed. Now I understand meta and compute are the ones that run SAS programs. How can I find out if there is a mid-tier too was installed. Another surprising factor is that the previous install was not done with a deployment plan. It was just running the setup.exe and going next ...next ...next in windows (By choosing "Install SAS foundation and the related software" option). Now I read another post that says if the SOE says "deployment type as planned", then we need a deployment plan. Are there any exceptions to this (like single machine install does not need a deployment plan?)? Can I stick to the same option and proceed with the installation? Here is everything that order has. SAS Analytics Pro, including the products: • Base SAS • SAS/GRAPH • SAS/STAT SAS Enterprise Guide SAS/ACCESS Interface to PC Files SAS/IML Thanks

RupaJ · ‎08-10-2018

Hello @PaulHomes Thanks much for sharing the article. I do see everything is in place. However still I get the error. I am checking with SAS support.

RupaJ · ‎08-09-2018

Hi @PaulHomes Yes, I am launching SASMC from the same server where I imported the certs.

RupaJ · ‎08-08-2018

I see this one which is more specific to SAS 9.4 M3 and higher releases. http://support.sas.com/kb/52/099.html I did import the certs with SDM and they were successful. I have configured the mid-tier and able to launch SAS studio/SAS EM. Only validating content server is failing with the mentioned error.

RupaJ · ‎08-08-2018

I see this KB. http://support.sas.com/kb/39/690.html But I don't see the path /usr/jdk/jdk1.5.0_12/jre/lib/security I am installed,configured 9.4 M5

RupaJ · ‎08-08-2018

Hello, I have successfully installed and configured the SAS meta, compute and mid-tier on Rhel 7 virtual server. While validating the content server, I am getting the below error. [8/8/18 3:18 PM] INFO: Starting simple validation for WebDAV server (level 1) - ping [8/8/18 3:18 PM] INFO: Ping successful! [8/8/18 3:18 PM] INFO: Starting extended validation for WebDAV server (level 1) - Making a connection [8/8/18 3:18 PM] INFO: Path: 'https://abcd:8343/SASContentServer/repository/default/sasfolders/' [8/8/18 3:18 PM] SEVERE: Exception accessing https://abcd:8343 (sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target) Any idea, how do I get past this error? Thank you.

RupaJ · ‎08-03-2018

Hello, So SAS support resolved my issue. What had happened was I had imported one of PKCS7 cert file which actually messed up the trustedcerts.jks/trustedcerts.pem file in the /opt/sas/sashome/SASSecurityCertificateFramework/1.1/cacerts directory. Due to which even when I trying the import the right certs, I was getting an error. The reason is SDM actually saves all the certs that we import and so it was constantly throwing an error. SAS support mentioned it as a defect in SDM and are planning to correct it. So as a workaround, we removed the trustedcerts.jks and trustedcerts.pem file and removed all the unwanted/bad certs from the directory and re-imported the right certs again and that did the trick. Here are the command to check the certs that your IT provides. Would save a lot of time, keytool -printcert -file ca-chain.pem openssl x509 -text -noout -in <your-server>.cer openssl verify -CAfile ./ca-chain.pem <your-server>.cer Thanks

RupaJ · ‎08-03-2018

Hello @alexal Sorry for the delayed response. Could you explain the tracing options or provide a link that explains it? Apart from "options msglevel=i" , I did not understand the rest. Also we figured what the issue was on our end. Our IT team disabled the LDAP service account thinking it's not used. Hence the issue. once we enabled that , the connectivity was fine.

RupaJ · ‎07-30-2018

Hello, I am having a bunch of users having this issue all of sudden. They are trying to connect to Teradata from SAS and hitting this issue. Users connect to Teradata using their LDAP account and none of their windows password expired.I asked them to logoff from their RDP session and log back in and that did not help either. What else could I check? Could the issue be on the Teradata side? For now I gave a temporary workaround to avoid ldap and directly use their Teradata accounts to connect. Thanks!

RupaJ · ‎07-30-2018

Hello @PaulHomes, Thanks! So I reached out to SAS support and they are suspecting an issue with trustedcerts.pem file. We launched the SDM with -loglevel 2 option and gathered more logs (including the SDM logs which I wasn't aware until then). I shall post the solution once it's resolved.

RupaJ · ‎07-25-2018

Ahh, thanks! So I tried the tool and checked the "trustedcerts.jks" keystore and I got "connection successful". So looks like the keystore is working. Not sure why I am getting the error while importing them.

RupaJ · ‎07-25-2018

Hello @JuanS_OCS Thanks for the response. I am not able to locate the trustcerts.jks file on the server I am installing. I don't see this file even on my production server where SAS 9.4 M3 is up and running. I am using sasinstaller user to launch the SDM.

RupaJ · ‎07-24-2018

Hello @PaulHomes Thank you for all the details. Yes I was using SDM to import the certificates and we also verified the certs using the below command openssl verify -CAfile ./ca-chain.pem sastest.cer sastest.cer: OK I checked the file and it just has "BEGIN CERTIFICATE....END CERTIFICATE and no other text. But it just keeps throwing that error. I have raised this with SAS support now.

RupaJ · ‎07-23-2018

Sorry, I failed to mention that I am trying to configure SAS mid tier on RHEL 7 environment.

RupaJ · ‎07-23-2018

Just some additional details. I got two certs from my IT guys (root.cer and local.cer). When I tried applying root.cer(It was in pem format), I get an error BUILD FAILED : Failed generate trustedcerts.jks: null I also changed the root.cer to root.pem extension and still received the same error.

Taking a long time to validate SASApp server

Re: SAS/Access to snowflake Error

SAS/Access to snowflake Error

SAS Architecture diagram explaining ports

Re: /opt/sas/ restore

/opt/sas/ restore

Re: How to take a good tar backup of SAS config directories

How to take a good tar backup of SAS config directories

Re: To create a keytab file for SAS IWA

Re: To create a keytab file for SAS IWA

Re: To create a keytab file for SAS IWA

Re: To create a keytab file for SAS IWA

Re: To create a keytab file for SAS IWA

Re: NTLM authentication is not supported

Re: SAS Deployment Backup

SAS 9.4 M5 windows installation

Re: Error validating the SAS Content server

Re: Error validating the SAS Content server

Re: Error validating the SAS Content server

Re: Error validating the SAS Content server

Error validating the SAS Content server

Re: certs required for SSL configuration

Re: SSO logon failed by gateway.

SSO logon failed by gateway.

Re: certs required for SSL configuration

Re: certs required for SSL configuration

Re: certs required for SSL configuration

Re: certs required for SSL configuration

Re: certs required for SSL configuration

Re: certs required for SSL configuration