topic SAS Visual Analytics 7.5 Sort Execution Failure | Cannot execute Visual Data Query in SAS VA in SUGA

SAS Visual Analytics 7.5 Sort Execution Failure | Cannot execute Visual Data Query in SAS VA

vfarmak — Wed, 04 Mar 2026 09:42:09 GMT

Greetings everyone,

We are experiencing the following problem: Our SAS LASR libraries were down so we performed the following steps:

Performed a restart on the linux machine
Cleared all the logs
Start the SAS LASR Libraries (we have two: the public LASR and the LASR)
Executed a visual data query on a very large dataset
The below problem occurred

Sort execution failure. Do you have a guideline on how to process these types of errors?

Thank you very much for your time.

Vasileios

Re: SAS Visual Analytics 7.5 Sort Execution Failure | Cannot execute Visual Data Query in SAS VA

sbxkoenk — Wed, 04 Mar 2026 11:15:24 GMT

Is this a VA Data Builder query?

I think the "Sort execution failure" error is caused by a resource issue, such as (disk) space in WORK or UTILLOC.

Can also be due to a lack of memory.

This SAS Note: http://support.sas.com/kb/39/705.html has some good information on how to trouble-shoot.

BR, Koen

Re: SAS Visual Analytics 7.5 Sort Execution Failure | Cannot execute Visual Data Query in SAS VA

sbxkoenk — Wed, 04 Mar 2026 11:28:10 GMT

You can also check:

system quotas
process limits

To check the process limits, ... please have the user (that runs into Sort Execution Failure) submit this code from their SAS session:

data _null_ ;
infile  "/proc/&sysjobid/limits";
input ;
put _infile_ ;
run ;

This will print the effective process limits for the SAS session to the log.

One of the limits is for the largest file size the user can create, another is the maximum number of files the process can have open. Either one of these could lead to the error.

BR, Koen

Re: SAS Visual Analytics 7.5 Sort Execution Failure | Cannot execute Visual Data Query in SAS VA

vfarmak — Mon, 23 Mar 2026 09:18:48 GMT

Hi @sbxkoenk

After long troubleshooting we have figured out the following:

The head node was restarted but the data nodes were not. Therefore we took the following actions:

Restarted the data nodes
Restarted the head node

Afterwards everything went to normal.

Thank you for the article you shared.

Best Regards,

Vasileios