I noticed this morning when going to force AutoLoad to run and upload a recently developed data set, that another AutoLoad process was running already. Looking at the logs I noticed that the process in place still was from 4:00 PM on the previous day. There is hardly any information in the log files, as it is getting stuck after writing ~6 KBs of information. I tried killing the hung process and starting again, but same thing...the process gets hung a second and a third time. I checked the PID log files as I know those can get rather large sometimes, but they were only a few KBs as well. Any suggestions on what is causing AutoLoad to hang or areas to investigate?
The problem has been resolved by cleaning up Logs folder inside your dropzone and cleaning up stale processes for the public LASR server.
In "Logs" directory of your autoload dropzone, do you have a autoload.sas7bdat file? If yes, remove it and restart the autoload process.
This is what I am seeing in Config/Lev1/Applications/SASV*/V*/AutoLoad/Logs - does not appear to be a autoload.sas7bdat file
Sorry...not Applications, but AppData as it is listed in the image.
SAS VA 7.4
SAS 9.4
The problem has been resolved by cleaning up Logs folder inside your dropzone and cleaning up stale processes for the public LASR server.
Registration is now open for SAS Innovate 2025 , our biggest and most exciting global event of the year! Join us in Orlando, FL, May 6-9.
Sign up by Dec. 31 to get the 2024 rate of just $495.
Register now!
See how to use one filter for multiple data sources by mapping your data from SAS’ Alexandria McCall.
Find more tutorials on the SAS Users YouTube channel.