Hello @jbond007  When the database name has changed , then in essence it is a new connection. The connection is being made to a new server/database. So prima facie yes. Details of registering tables could be found here https://documentation.sas.com/doc/en/bicdc/9.4/bidsag/n0g5t6jbzorstsn18d5e9h7ngdkw.htm Typically SAS Administrators would be able to handle this situation with ease. ... View more

Hello @js5  When one logs in to another machine using SSH it is as good as logging into that machine. With your error being  'Could not create object named "SASEGObjectModel.Application.8.1" '  there are two things that need to be checked 1.SAS EG 8.1 is installed on that machine. 2.Make sure that SAS EG executible and the cscript file locations are in your path.  This can be verified using echo %PATH% command in the command shell. If not then add the paths to the environment variables.     ... View more

Hello @viswmmo  Please pay attention to the I/O error as mentioned in the message I/O error on POST request f... Your job must be performing and I/O (Read / Write) and that is not happening. Are you connecting to some external database OR reading/Writing to a shared drive? If yes please look into it. ... View more

Hello @freshstarter  There are multiple approaches to address your issue depending upon your environment and practices. One approach would be to create an authentication domain. This is typically done at the admin level. Please refer to the following references. 38204 - Using the AUTHDOMAIN= option with SAS/ACCESS® 9.2 engines  (For SAS 9.x) creating domains and credentials using the sas-viya CLI (SAS Viya) The other approach would be to create a libref in the autoexec.sas or use encoded passwords as suggested by @Patrick  ... View more

Hello @GuidoG  I think the "Personal Way" in Part 1 of this article gives you a hint. One should be able to create a libref using libname statement referring to an accessible physical location. ... View more

Hello I see this in the log " <hostnameX> Failed to connect to the host via ssh: Shared connection to hostnameX closed   Looks like this issue needs resolution. ... View more

Hello @SASExpo On rereading your posts, I see one important point you have mentioned and something   that should have been taken a note off earlier. "Our users open a RDP session to a Windows terminal server that hosts the SAS client software, their user profiles for Windows are mapped to a share via group policy." This makes it clear why a large number of temp files are created at one location, why they accumulate over time and why profiles are stored on a shared server. My understanding is that Windows OS retains these .tmp  files for   the default duration. The first option would be to make configuration changes to delete files older than "a set duration" if that is feasible (Not a windows expert). Alternatively write a PowerShell script to take care of this. I have used the term "a set duration" because in my experience SAS EG users keep their EG projects open for days together, and it is not an easy task to get this workflow changed.  Deleting the tmp file for the session in use could create issues for the user. Therefore this "set duration " has to be agreed upon by all stake holders. The smaller the better. If this approach is not workable for any reason, then the other feasible option would be to move the EG client to the user's local machine. ... View more

I suggest you open a ticket with SAS Tech Support. ... View more

Hello @anandas  In your scenario I would agree with @sys-halt  and go for the default option " Generate credentials to secure the connection". Make sure   you have the backups so that roll back can be done should it be needed. ... View more

Hello @W1ndwaker  When you say this "the thing is that there are users that are not in the group of the folder that can map it and work on it.", it's time that these users be added to the appropriate groups both at the LDAP, SASMC and the OS level if they need access. Typically, SAS Administrators handle these scenarios with ease. If there is something weird OR complicated, it's time that a support ticket is created with SAS Tech Support for assistance. ... View more

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