Skip to main content

SAS massive debug log file

Question:
Our client machine has ran out of space on his workstation due to SAS creating a whopping 500GB log file.

The log file is located under AppData and the file name is Aria-debug-5800.log. The file got created during the time the client had licensing issues. We fixed the licensing issue by simple reapply of the license file. I assume these issues are correlated.

I wanted to know if the log file safe to delete and how can avoid this event to happen again? I assume it doesn't contain very critical information since the log file is created only couple of days back, but I would prefer to have a confirmation first.

Answer:
It looks like it is not related to SAS software. Googling the log name aria-debug log suggests this may be an issue with Microsoft OneDrive.

Just check if the log in the generic %AppData% directory, or the SAS specific %AppData%\SAS. SAS related file will be stored under %AppData%\SAS.

Comments

Post a Comment

Popular posts from this blog

Insufficient authorization to access PIPE error in SAS EG

Issue: When I tried to run SAS code in SAS Enterprise Guide it throws following errors: ERROR: Insufficient authorization to access PIPE. ERROR: Error in the FILENAME statement. Screenshot of error: Solution: This error occurs when you try to run OS commands in SAS code. To run the OS commands in SAS code you need to enable XCMD option. You check it in SAS Management Console by following below steps.   Open SMC -> Expand Servers -> Expand   In SASApp , expand Logical Workspace Server -> right click on Workspace Server. Click properties -> option tab -> advanced options -> launch properties. Check whether Allow XCMD is checked. The issue arises if the Allow XCMD is not checked. In above image, Allow XCMD option is not checked. It should be checked to run OS commands from SAS code. In Unix /Linux machines, this XCMD option can be enabled by using system option XCMD in sasv9 config file or workspaceserver.sh script f...
2 comments
Read more

SAS - CLI error trying to establish connection

Issue: User asked me to make a database connectivity to SQL Server. They provided following details SQL server hostname and ip address Database/DSN name Username Password I made entry in ODBC.ini file. You know, SQL Server entries were made in ODBC.ini and Oracle entries were made in TNS.ora file. Everything went fine, took back up of odbc.ini, made entry and saved the file. So to test this connection I ran the libname statement in SAS Enterprise Guide 6.1. It throwed following error. Error Message: My DB team showed that they are able to login   14 GOPTIONS ACCESSIBLE; 15 LIBNAME test ODBC DATASRC=SGE_DS SCHEMA=VST USER=sales PASSWORD=XXXXXXXXX; ERROR: CLI error trying to establish connection: [SAS/ACCESS to SQL Server][ODBC SQL Server Legacy Driver][SQL Server]Login failed for user 'sales'. Solution: First I suspected that Login failed for user 'sales' meant the password provided by DB team was wrong. They responded that they were able to login wi...
2 comments
Read more

Insufficient authorization to access prgramname.lst

Issue: I had an issue with batch server. The code runs fine in SAS EG and SAS DI Studio but fails when I run with batchserver. Error seems to be ERROR: Insufficient authorization to access /opt/sasinside/Lev1/SASApp/Sas_Program.lst. NOTE: The SAS System stopped processing this step because of errors. Solution: When you execute on batch mode sas tries to save the output file (Sas_Program.lst) under /opt/sasinside/Lev1/SASApp where is no permission to write. We should add two system options to sasv9_usermods.cfg file to redirect this outputs to another directory. The options are following: -altprint <directory>  -print <directory> Where directory is a directory where you have access to write. You must provide this directory. The directory can be some shared location like: /share/sas/lst. If you decide to add this options these are the steps to follow: 1. Create or choose a driectory where your userid have write access. The userid is the ...
Post a Comment
Read more