As the name suggests this exception in Java occurs when JVM tries to load a particular class and doesn't found the requested class in the classpath you specified. This means that, your classpath is broken. Java ClassNotFoundException thrown when an application tries to load in a class through its string name using:   The forName method in class Class. The findSystemClass method in class ClassLoader . The loadClass method in class ClassLoader.   When you get a ClassNotFoundException , it means that the Java Virtual Machine has traversed the entire classpath you specified and not found the class you've attempted to reference. The one and only solution is to check your classpath carefully.   Verify the name of the requested class is correct and the specified .jar file exists in your classpath. If not, you must explicitly add it to your application’s classpath.   If it's present in your classpath then there is high chance that your classpath is getting overridden or application is using classpath specified in jar file or start-up script and to fix that you need to find the exact classpath used by your application.   ... View more

@huntdoug has given the correct answer. You can either install / configure the auditing and logging / EM service architecture - which records much more detailed information, or you can look at the metadata server log for basic connection info.   I had to do this for someone just a few days ago and they didn't have the the full auditing and logging installed, so I analysed the metadata server log. using this simple program - it may not be perfect, so check your results:   *reads in metadata server log and attempts to determine who connected.; filename mdlog "/Path to the metadata server log/sasmeta......log" ; data connections; length userid $32; format time time. date date.; infile mdlog ; input @1 date yymmdd10. @12 time time8.; userid=scan(_infile_,4,':'); userid=strip(scan(userid,1,'-')); /* Sample data 2021-03-29T23:43:35,642 INFO [133178522] :sastrust@saspw - Request made to cluster SASMeta - Logical Metadata Server (A5L3816M.AX000001). 2021-03-29T23:43:35,642 INFO [133178522] :sastrust@saspw - Redirect client in cluster SASMeta - Logical Metadata Server (A5L3816M.AX000001) to server SASMeta - Metadata Server (A5L3816M.AZ000001) at sasmeta.xyz.co.nz:8561. 2021-03-29T23:43:35,652 INFO [133178526] :sasevs@saspw - New client connection (6181722) accepted from server port 8561 for SAS token user sasevs@saspw. Encryption level is Everything using encryption algorithm AES. Peer IP address and port are [10.123.456.789]:56444 for APPNAME=/SASAuthorizationServices - Web Infra Platform Identity Services 9.4. */ if userid not in('svc_sas_prod','sasevs@saspw','sasadm@saspw','sastrust@saspw','svc_lasradm_prod'); run; *unique users; proc sort data=connections out=uniqueusers nodupkey; by userid; run;   And I only had to report on connections for one week, so I just ran this 7 times to analyse the 7 daily metadata log files, so clearly this could be enhanced to automate processing of a range of logs. Unfortunately, it only reports who connected to the SAS System, not what they did.   To implement more comprehensive auditing and logging can be a reasonable amount of work to set up. If you set up workspace server logging (for example, every EG session has the log saved to disk), this can consume lots of disk space, so you need to consider retention periods, automated archiving etc. Typically a dedicated log disk volume is set up of maybe 100 or 200GB in size just to store logs. Auditing and logging seems to be a requirement more and more these days. I've had to set this up for a number of government sites to comply with increased security requirements.             ... View more

I am assuming that you are the SAS administrator if you are getting alerts and have taken some SAS admin training, that being said you need to provide more information about your problem. You need to find the cause of the excess CPU consumption that is setting off this alert.  When the alter happens check the running processes and see which process is using all the CPU.   It could be that there are a few individuals that are using all the resources and this has nothing to do with the data.   It could be a wide range of things from your current system not being able to handle the load or users that are running long resource-intensive jobs. There is a simple solution to those, one upgrade your systems or get your users to start submitting those long-running jobs in the evening.   If you know who is causing the issue and want to separate them or limit their resources. There isn't anything that is easily done to accomplish this. You cannot limit the number of resources a SAS session can have but you can put those users on their own machine. You could add a new application server with a new workspace server on a separate machine(this will definitely affect your licensing agreement - $) but allow you to redirect these users to those resources on that machine and not affect anyone else. I would not have this documentation off hand and you would need to contact your Sales rep and then sas tech support for how to include a new Workspace server in your environment.   Hope this helps.   Carmine     ... View more

For SAS/Access to TD you will need following client installed. You can refer the system requirements doc based on your OS: https://support.sas.com/documentation/installcenter/en/ikfdtnwx6sr/66390/PDF/default/sreq.pdf https://support.sas.com/documentation/installcenter/en/ikfdtnlaxsr/66396/PDF/default/sreq.pdf Search for section:  SAS/ACCESS Interface to Teradata SAS/ACCESS Interface to Teradata Base SAS is required for the installation of SAS/ACCESS Interface to Teradata. SAS has extended SAS/ACCESS and SAS In-Database Technologies support to selected cloud and database variants of supported data sources. For a list of the supported variants, see https://support.sas.com/en/documentation/third-party-software-reference/9- 4/support-for-database.html. DBMS Products Required: • Teradata Database version 13.10 or later • Teradata CLIv2 client libraries, TTU 13.10 or later for Windows (64-bit libraries) For SAS 9.4M3 DBMS Products Required: • Teradata Database version 14.10 or later • Teradata CLIv2 client libraries, TTU 14.10 or later for Windows (64-bit libraries) For SAS 9.4M4 – 9.4M6 DBMS Products Required: • Teradata Database version 15.10 or later • Teradata CLIv2 client libraries, TTU 15.10 or later for Windows (64-bit libraries) For SAS 9.4M7 and Later DBMS Products Required: • Teradata Database version 16.20 or later • Teradata CLIv2 client libraries, TTU 16.20 or later ODBC and JDBC are industry standard. Difference between them is the technology used for the driver. General difference here: https://www.geeksforgeeks.org/difference-odbc-jdbc/ In SAS perspective configuration will be different based on what you use ODBC or JDBC. You can refer the above shared system requirements document for the configuration. Kindly note JDBC is supported only from Nov 2018 release onwards. ... View more

Hi @ksuman    Check this KB article: https://support.sas.com/kb/58/599.html   ... View more

Hi @ksuman    If the database access was not setup during initial deployment, you can follow the steps in below links to perform the configuration again.   https://go.documentation.sas.com/?cdcId=calcdc&cdcVersion=3.4&docsetId=dplyml0phy0lax&docsetTarget=p03m8khzllmphsn17iubdbx6fjpq.htm&locale=en#n1t88616q5ef1zn16zalddlehg63   https://go.documentation.sas.com/?cdcId=calcdc&cdcVersion=3.4&docsetId=dplyml0phy0lax&docsetTarget=p03m8khzllmphsn17iubdbx6fjpq.htm&locale=en#n06ccdjy3d11dln1a3k80hfh2ifw   ... View more

Sorry, I can't help there, never used that sort of Linux. But looking at version numbers on the MariaDB website I don't think it's any of those. I think they're for installing the DB package. But you probably need the MariaDB Connector/ODBC package if you can find it, or download it from their site. Latest version is 3.1. ... View more

It might require some reading, but the following documentation link might help, which also includes some examples:   https://documentation.sas.com/?docsetId=casref&docsetTarget=n09w43elndibwun1q5iy7wae5yy5.htm&docsetVersion=3.4&locale=en     Amir. ... View more

Do you intend on exposing an internal SAS Viya based deployment to the Internet using a reverse proxy on the public Internet? Is that what you are asking for help with? ... View more

@ksuman ,   Yes, that is possible.    SAS® Viya® 3.4 Administration / Authentication: How To ... View more

Hi,   According to the system requreiments, SAS CI Studio 6.4 conforms to the general SAS Platform 9.4 web application browser requirements, which are outlined here:   So IE (9-11), Firefox and Chrome are supported.  But you must have Adobe Flash Player installed and enabled.         ... View more

Hi @ksuman,   as @Madelyn_SAS mentioned, everything is explained on the Administration Guide. Did you had the chance to read it? Did it helped?   Just in case, a summary: - For the general SAS Services, there are instructions on the sas.servers script (on your Lev1 folder) - For the Public LASR server, it will be automatically started if the server is off, as soon as one of the Autoload scripts will be triggered. Do you have any Autoload folder? - For the "private" LASR server, you can attach an Autoload folder, use the Reload on Start functionality... and, worst case scenario, you can script the start fo the server and schedule the script.   ... View more