About AnandVyas

AnandVyas · ‎09-25-2020

I am not sure if I got it right, but your main software was installed using depot of version 9.4 M7 and you are adding SAS/IML using a depot of version 9.4 M6? If that's the case it won't work. You will need to have a depot of same release and usually when any components are added or removed, it has to be done on the same order and the software depot has to be downloaded again to reflect the correct products.

AnandVyas · ‎09-25-2020

Open the certificate in windows machine and export it to the required format. Just google on the steps or check this link if it helps: https://community.tenable.com/s/article/How-to-export-certificate-in-PEM-format-for-import-from-Windows

AnandVyas · ‎09-25-2020

Under connection details instead of default login as none you should click on more logins and search for the user id that you have defined under DB2 Auth and select it. After that when ever you make a connection to this library and you are part of the SMC group where this ID is defined you should be able to connect it with out being asked for ID/Pass.

AnandVyas · ‎09-23-2020

openssl x509 -outform der -in your-cert.pem -out your-cert.crt Try this

AnandVyas · ‎09-22-2020

Are the root and intermediate certificates imported in compute server?

AnandVyas · ‎09-22-2020

Usually the process is first you generate a key using which CSR is generated. CSR is then shared to certificate signing authority CA which generates the cert chain: root - intermediate - host cert and shares it back. In the SDM you need to provide the CA signed cert and key generated in first step. If your web server and web app server are on different hosts or use alias mention them in CSR under SAN field in order to avoid any errors due to host or alias mismatch.

AnandVyas · ‎09-22-2020

Is this question for VA on Viya platform or SAS9? Based on the platform steps could vary.

AnandVyas · ‎09-22-2020

SSL issues can be tricky. Just try to check where the macro is getting triggered and what’s the Java path being used during the startup. This will give an better understanding to troubleshoot.

AnandVyas · ‎09-22-2020

Hi Knut, As per the snap in the document attached SAS deployment wizard has detected few components in current sashome to be of latest version to what is available in the software depot you are using to install. That is the reason it gives an warning. Please advise if the software depot you are using is of recent download? If not, you will have to download the latest one. You can generate deployment registry to get the version currently installed to compare it with the version in the software depot. If the version of any components in software depot is lower than that of currently installed you will have to request for a latest software depot.

AnandVyas · ‎09-22-2020

I saw the snap in the attached document. You will have to provide full path along with the ssl certificate file name in the first box and full path along with the key file name in the second box.

AnandVyas · ‎09-22-2020

You don't need to change permissions of the utility itself, you need to just run it using root or sudo ID. sudo <path-to-clean-work>/cleanwork <path-to-sas-work>

AnandVyas · ‎09-22-2020

Was there any alias or load balancer used for web applications in the initial configuration? If yes, you will have to update those entries manually. For hyperic.keystore, yes it has to be generated again with new certificates. I think the steps are documented in the guide you have shared. As part of updating hostnames there is a file generated for some manual changes which has some steps to be done in the agent configuration, have you performed them? There is a manual step on the compute server where EVM datamart is hosted to change the hostname manually in the sasev.properties file. Have you performed that as well? I had a similar issue after cloning of environment and it got resolved after all the required manual steps and flushing data folders.

AnandVyas · ‎09-22-2020

My bad, I didn't notice you mentioned that just before the log snap. Can you try the steps provided in this KB link? https://support.sas.com/kb/58/621.html

AnandVyas · ‎09-22-2020

Hi @Madhan_cog1 Please follow the steps shared by @JuanS_OCS . Also I would advise in the future it's good to enable HTTPs during configuration phase itself as you can avoid a lot of manual changes and errors caused due to it. Depending upon the web applications deployed at your site it will only add to the complexity.

AnandVyas · ‎09-22-2020

Can you try the example provided in this link: https://documentation.sas.com/?docsetId=casref&docsetTarget=n0s9iuu3d4cxjzn1st0z33ik35if.htm&docsetVersion=3.5&locale=en#p16mu1n10ys6ksn1xjegisphikhj caslib oralib datasource=(srctype='oracle', username='myuser1', password='myPwd', path="myORAdata");