HI, Also make sure that you have read and write permissions to the underlying folders in metadata that store the business context. Regards James ... View more

Hi there,   This is likely to be getting blocked by MS Outlook, if the same link works with other email clients.    Please open a track with SAS Technical Support if you need further help.   Thanks and best regards! ... View more

Hi Michal, please open a SAS Technical Support track with your local office, so that we can help you with this.   Thanks and regards! ... View more

I agree with Tech Support, don't uninstall or upgrade for that matter. That version of SAS is certified with a certain version of the third-party product, but by uninstalling/upgrading now, you run a real risk of introducing all sorts of issues, which you will be fixing in the end.   We are mindful that the customer don't want unsupported software, but now is not the time to pull the plug. They will just have to live with the current version until the upgrade. The customer must also take responsibility for waiting so long before upgrading. ... View more

In order to do this, you're really going to want to have a custom deployment plan that you can specify in the SAS Deployment Wizard.  You'll need to contact your SAS partner manager in order to get such a deployment plan which specifies only CM and RTDM.  Picking and choosing which products to install from a preexisting deployment plan (standard or custom) is not recommended as you can easily miss product dependencies.  Getting a custom deployment plan from SAS ensures that the right products/components will be included in your install. ... View more

Hello @miki7,   in short, it is all the steps that are related to the new certificates. Assuming that the SSL certificates are applied only to the SAS Web Server, the steps would be:   - Backup and then overwrite your certificate, the chain (and the private key, if it was also updated) on the ssl folder on the SAS Web Server, keeping the same names.   - Backup your jscerts from the SASPrivateJRE on your servers (all of them, and optionally you can also backup the cacerts, just to be sure).   - Restart and validate the SAS Web Server (httpd only)   - Deploy the newcertificates (Root, CA, the server certificate) into the jscerts with the SAS Deployment Manager (SAS servers)   - Deploy the new certificates (Root, CA, the server certificate) into the jscerts with the SAS Deployment Manager.(SAS clients)   - Restart the SAS services: generally it should be enough just with the middle tier, but I would ratther recommend all of the SAS Services, including the sas.exe for LASR.   - Validate the SAS Content Server   - Validate your VA application ... View more

Hi @Ksharp thanks for your fast reply. Yes, we did steps from https://support.sas.com/documentation/cdl/en/proc/65145/HTML/default/viewer.htm#p19qqqyq9te9u3n1oq8fbdta7dqt.htm   BUT did we do them right? at first i want to tell that it  Worked on my personal sas 9.3 but not in the sas installed in our company.   We are downloading sharable file from googledocs.  We have done this: downloaded google public certificate from browser. created truststore added certificate to truststore set jvm options reseted object spawner   still didnt work. Proc http said hostname not found and filename just stucked the sas execution.   BUT when we tried some file on standard HTTP it worked like a charm!   Is there something we could have done wrong? Thank you very much, Michal ... View more