02-28-2017 02:52 PM
I am having a problem with SAS University Edition. Whenever I am trying to run any proc i get the follwoing message and no results are displayed because of it.
02-28-2017 03:42 PM
Do you do imports/exports via SAS Studio instead of using the shared folder? They use the #LNxxxxx temporary files during the transfer. Those files are not removed by proc datasets.
Does the effect vanish with a restart of SAS UE?
And how large are your datasets? It might be that you only try to use more space than is provided by SAS UE.
02-28-2017 07:19 PM
I do use SAS studio to import and export. I tried restarting and shutting down VMware and SAS studio several times andI also tried using another pathway to save my dataset in some other folder like Chris suggested, I also tried PROC dataset =work kill no list run;
But nothing worked.
I presume that I cannot access the Work folder because I am usingVMware. But I really need another way to create space in SAS studio.
Guidance is very much appreciated.
03-01-2017 12:39 AM
SAS UE is in a very locked down state, and does not allow any advanced options (like XCMD) that would enable manual cleaning of the work location.
So you should start a fresh image of the UE VM.
Next, determine the sizes of the data you are working with. It might be that your data is simply too big for a learning tool; in that case, reduce it in size.
Next, avoid your method of import. Instead copy your files into the shared folder and run the import from there (write your data or proc import steps yourself); that prevents the creation of the #LN files in work.
Store all datasets in a library in the shared folder; use the compress=yes option to reduce dataset size
Also do not use the standard SAS Studio task method for export. Write data or export steps that create files in the shared folder.
By keeping as much data as possible in the shared folder, you always have the option to use desktop tools (Windows Explorer) for housekeeping.
03-01-2017 03:43 PM
If I reinstall the VMware, is there a possibility that all my data(datasets, SAS codes etc) would be lost too?
I am having the same trouble today even though I changed the dataset folder pathway to a physical locaiton on my laptop.
03-01-2017 03:56 PM
03-02-2017 03:46 AM
WORK is in /tmp, which is a filesystem inside the VM with no connection to the host(desktop) filesystem. If your SAS process crashes (or is hard-terminated, eg by you turning off your computer!), it does not clean up the WORK directory as it normally should. So you have no control over it, and if /tmp is full, ist stays that way, no matter where you store your datasets. WORK is still necessary for utility files or transfer files.
03-02-2017 09:30 AM
I tried uninstalling and reinstalling VMware hoping it could wipe out the temp files. But even that didn't work.
I tried increasing VMware disk space,even that didn't work.
I got the following error message
Any other way to solve this problem?
If uninstalling and reinstalling isn't working, please suggest me some other way to get SAS UE running without any space trouble.
03-02-2017 09:36 AM
What are you doing when the crash on a newly installed VM happens? Is this really the first operation you do?
03-02-2017 09:38 AM
03-02-2017 09:41 AM
I have the suspicion that your datasets are simply too large to be used in UE.
Run proc contents on the datasets and look at the physical size of the datasets.
Increasing disk size for the VM doesn't work because the filesystems are defined within the VM image with a given static size.
03-02-2017 09:49 AM