SAS VA: Autoload and Manual Import do not work.

[DWhite]

On 1/24 the vmware host that houses our VA server crashed. After bringing it back up VA had a fatal error and had to be recovered from our backups. After all of that, everything seemed to work and come back ok. However, it was realized that autoload and manual import are no longer working. Attached is the AutoLoad log.  Below is the Manual Import log from VA. We have signature files in the proper location. Additionally, we are unable to restart SAS LASR Public from the Administrator panel. Thus we are not confident that SAS LASR is running as there is no PID for that process.

---------- SAS VA Manual Import Log --------------------------------

2 The SAS System 14:02 Thursday, January 30, 2020

4 Options VALIDVARNAME=ANY VALIDMEMNAME=EXTEND;
5 %macro deletedsifexists(lib,name);
6 %if %sysfunc(exist(&lib..&name.)) %then %do;
7 proc datasets library=&lib. nolist;
8 delete &name.;
9 quit;
10 %end;
11 %mend deletedsifexists;
12
ERROR: The signature is not valid, access denied.
13 /* Remove target data table from Library */
14 %deletedsifexists(LASRLIB, reading_recovery_master_test_csv);
15
16

 -----------------------------------------------------------------------------

[alexal · Accepted solution]

@DWhite ,

A /opt/sasinside/sasconfig/Lev1/AppData/SASVisualAnalytics/VisualAnalyticsAdministrator/AutoLoad/Logs/autoload.sas7bdat is corrupted. You need to remove that file.

[DWhite]

After a couple of restarts of the SAS service stack that did not fix the issue. We rebooted the server after deleting the /opt/sasinside/sasconfig/Lev1/AppData/SASVisualAnalytics/VisualAnalyticsAdministrator/AutoLoad/Logs/autoload.sas7bdat file and the old PID file that was located in /opt/sasinside/sasconfig/Lev1/Applications/SASVisualAnalytics/VisualAnalyticsAdministrator/Monitoring/PIDs. This resolved the issue. We restarted the services with Autoload turned off. Once all of the services were online, AutoLoad was turned back on.