Hello @SASExpo  The general practice is to install the SAS client (SAS EG) on the user's local machine and the SAS   Server software   on the remote server. User's profiles are typically local to their machines. With the arrangement you have SAS EG on a remote machine and all 50-70 users starting their session on the same machine would cause what you are facing. Definitely not an ideal scenario. ... View more

Hello @SASExpo  From your posts what I understand is that (1) user profiles are being stored on a remote SMB server (2) The tmp files in the users %APPDATA% folder is crashing the SMB server. (3) Your question is whether the i/o guidelines apply to the user data too. I am using that  SAS is installed on the server and SAS EG on the users/client  machine As far as my understanding goes the i/o guidelines apply to the i/o throughput of executing  SAS code  on the server.(.) SAS EG is Windows IDE for SAS and the temp files that you have shown are those created at the client end and not by the running SAS code. In my experience these tmp files have no long term value. Typically a SAS EG user has a number of sessions open and along with the code, there may be windows with logs, open reports  and SAS datasets. These temp files may be outcome of this action at the user level.  At the end of the session or the day the tmp files should go away OR may be safely removed.  (Something like tmp files created when somebody opens for example a word document for editing). Admins typically do not have any role in the users workflow and in your scenario, as an admin, I would recommend keeping the users profile locally on the users machine. ... View more

Hello @kumarsandip975  This is an interesting question. I would appreciate if somebody from SAS   can answer this question for the benefit of the community, particularly the number after P in Current version: 9.04.01M7P080520.  There must be a purpose for this.   ... View more

The documentation says "If you are running the February 15, 2022, release of SAS 9.4M7, you must rebuild the Windows definition to apply any changes made to its configuration." Thus if you are using the February 15, 2022, release of SAS 9.4M7, then you would need the steps as mentioned in the documentation. It is clear in the documentation that "If you are running a release prior to the February 15, 2022, release of SAS 9.4M7, configuration is complete and no further changes are necessary." Thus it depends on what release of 9.4M7 you are using. The reason is that February 15,2022 releases use Apache Tomcat in place of pivotal TC Server. These reside on the Midtier. In case of a doubt I suggest that you open a track with SAS Tech Support. Enclose the output of Proc Setinit in your track.   ... View more

One can reference the details in $deploy/sas-bases/examples/data-access/README.md for your installation. The ODBC clients/drive need to be installed in a Persistent Volume storage.  One should typically be able to access with ssh. There must be a jump box to access this. I would prefer creating a separate folder for each ODBC driver Select a driver that could be extracted and used (tar.gz extension) rather that that needs installation (rpm) The video I referred to above and the readme file as above are helpful and the process pretty straight forward. ... View more

Hello @Jed_Klei  When you say, "If the code is run by another user, data is returned with no issue."  then this is an issue specific to you. It could possibly be due to your access, networking or the like. Difficult to pinpoint without investigation. As rightly said by @ballardw, posting a log would be helpful. However, IMHO, the appropriate approach would be to seek assistance from local IT support and the SAS Administrator at your place.   ... View more

Hello @JimmyJoeBob  I see this in the first post "ERROR: CLI error trying to establish connection: [Microsoft][ODBC Driver 18 for SQL Server][SQL Server]Login failed for user 'NTAUTHORITY\ANONYMOUS LOGON'." This is an expected behavior. SQL server needs credential to  allow connection. ... View more

The Content under the Content Server is stored in the Web Infrastructure Data server and the content server itself  is a part of the Web Infrastructure data server, typically PostgreSQL. WinSCP is not a tool to connect to it. While in principle one can use pgAdmin , but better avoid it. It is advisable to reach SAS Tech Support for resolving any issues. ... View more

That is something doable using a script . What is the OS? In case you want to use SAS have a look here https://support.sas.com/resources/papers/proceedings17/1136-2017.pdf https://www.lexjansen.com/pharmasug/2006/TechnicalTechniques/TT04.pdf ... View more

- Do we need to install ODBC drivers in Viya access clients mount path? Yes MSSQL odbc client driver  for 64 bit Linux would be needed (unless it is built in to Viya 4) - Do we need to open port of MSSQL database to k8s cluster nodes of sas viya? well the Viya4 environment and the SQL server should be able to connect to each other. You can contact SAS Tech Supports to get  assistance appropriate to your case. Have a look at this video https://video.sas.com/detail/video/6234732546001/sas-demo-%7C-how-to-configure-a-sas-access-interface-in-sas-viya-4 Though it is for Oracle, the concepts apply to your case. You will find answers to your questions.   ... View more

Hello @Maicfel  Did you get a chance to look here SAS Help Center: %MDSECDS Security Report Macro in particular please see if this macro can help you. %mdsecds(identitynames="sasdemo", identitytypes="Person", membertypes="Library", perms="ReadMetadata"); ... View more

Hello @John_Wick  SAS event processing has an Apache Kafka Connector. SAS Help Center: Using the Kafka Connector and Adapter. This is also another option Stream SAS Data Sets Data into Apache Kafka Topics (cdata.com) I would appreciate if you can share your success story in connecting to Kafka from SAS. ... View more

Hello @stove  if any user is running the sas-viya cli on a machine (e.g. laptop, desktop etc.)  behind the proxy/firewall, then the connection has to be allowed between the source and destination in the firewall.  This may be the case in your situation. Please make a request to your local admins to assist. ... View more

Hello @Spachai  Your question is "We got an requirement to encrypt the dataset outside SAS 9.4. ...." Well in IMHO it should not matter what approach one uses to encrypt data when it is outside SAS. When the encrypted data is to be used in SAS again, Then it should be decrypted. I recommend approaching SAS Tech Support for this issue. ... View more