About AnandVyas

AnandVyas · ‎10-30-2020

Hi @Tarunsai How are you starting the LASR server? Using the new SAS EVM UI or using code?

AnandVyas · ‎10-29-2020

Since all the STP session are triggered by STP account 'sassrv' I don't think there is any OOTB feature that can create a mapping or audit trail to the actual end-user. You can write custom code to filter these information from the application server logs, may be. But the STP can be triggered in a number of ways, catering to all of that could be tedious. If have exposed STP as BI service, I think you can check the number of requests in the Web Server logs.

AnandVyas · ‎10-28-2020

Hi @RupaJ Yes, you are correct for points 1 and 3. For point 2, I checked the SAS Software upgrade guide for Effect on customization and it doesn't mention anything for IWA. I don't think the configuration will be reverted, but if you are looking for a official confirmation you can drop an email to SAS Technical support at support@sas.com It is recommended to take full backups of the system in-case there is a situation where we need to revert back. Effect on Customizations

AnandVyas · ‎10-28-2020

Hi @StefanM You can use pgAdmin to monitor different aspects of the PostgreSQL database. It has a Dashboard with different metrics, out of which there is one for 'Server Activity' which has a section for sessions. Could you also please clarify what do you mean by technical user? In SAS to run stored process there is a managed account 'sassrv' (also called service or system accounts. Default is 'sassrv' can vary at your site) which is the owner of the SAS stored process session and if required it can make a connection to the DB which is normal. You will see the connection with this user itself.

AnandVyas · ‎10-28-2020

Hi @AMUMOR_SAS You will have to check with SAS Admin team if the encoding was changed in SASv9.cfg file in the old platform. During upgrade some settings are overridden and updated to default and have to be reverted back. If for any reason they want the default SAS Session encoding to be default then there are different options that you can choose to override it at your individual session level. You can use the encoding= system option to override the default session value. Some reference links below: https://documentation.sas.com/?cdcId=pgmsascdc&cdcVersion=9.4_3.5&docsetId=nlsref&docsetTarget=n08gwe43ne71imn1oz7se05kthxi.htm&locale=en https://documentation.sas.com/?cdcId=pgmsascdc&cdcVersion=9.4_3.5&docsetId=nlsref&docsetTarget=n0utx4w7x4exijn1wt7pk0srrxz5.htm&locale=en

AnandVyas · ‎10-20-2020

Hi @Madhan_cog1 Glad that you were able to get to the root cause after enabling workspace server logs and resolve the issue.

AnandVyas · ‎10-20-2020

Hi @Madhan_cog1 Thanks for sharing the logs. I can see that the request was submitted and LSF did try to launch a session however it failed. Since you have confirmed that the connection works from EG/Studio I am ruling out below issues: - User Home directory exist on the all compute nodes. - LSF process are running as required on all the compute nodes. Do you have workspace server logs enabled on the compute nodes? Could you please check and advise if the workspace server log was generated or not? If generated, are there any errors reported in that? Also, Was this setting working before? Did you try restarting object spawner?

AnandVyas · ‎10-20-2020

Hi @Madhan_cog1 Can you confirm you are using same "sasdemo" ID and password which you are using from EG/Studio? If the connection works from client, it should work from SMC as well. If it's still the same, I would advise to enable debugging for object spawner logs and capture the results to analyze it further. https://documentation.sas.com/?cdcId=bicdc&cdcVersion=9.4&docsetId=bisag&docsetTarget=p1cu1oogaxct6jn1w9yv4wz03qwz.htm&locale=en

AnandVyas · ‎10-20-2020

Hi @SAS_LuisBolivar Could you please share more details on what scenario are you getting this error? Were there any recent changes to Web Server after which this error is reported in logs?

AnandVyas · ‎10-20-2020

Hi @Madhan_cog1 Clear the credentials cache from SMC and try again. Also, "sassrv" should not be used to validate workspace server. You can use "sasdemo". https://documentation.sas.com/?cdcId=bicdc&cdcVersion=9.4&docsetId=bisag&docsetTarget=p0ekp61ix06nsnn1qcn49a3p03cx.htm&locale=en

AnandVyas · ‎10-18-2020

Hi @PriitL Are you able to perform the backup manually using the UI without any failure? Is the SAS Deployment agent service up and running on the hosts?

AnandVyas · ‎10-18-2020

Hi @klroesner Check this blog post for using code snippets in Viya. https://blogs.sas.com/content/sgf/2019/04/16/using-code-snippets-in-sas-viya/

AnandVyas · ‎10-15-2020

Also, the certificate chain should be root, followed by intermediate and then the host. I think you have done it in reverse order.

AnandVyas · ‎10-15-2020

Hi @Nigel_Pain SMC uses the workspace server application context tagged to the library. You can view the log from the SMC wizard after running the update table metadata step. IMO don't think there is any explicit option added for SMC.

AnandVyas · ‎10-15-2020

Hi @Hacko Check if the steps in this KB article help: https://support.sas.com/kb/52/670.html