12-28-2011 02:16 PM
Here is a bit from a link I found on SAS's website: http://support.sas.com/documentation/cdl/en/hostwin/63285/HTML/default/viewer.htm#winperform.htm
Sixty-four bit processing in Windows operating environments uses 16 terabytes (TB) of virtual address space, so in these environments, extended memory is not needed. SAS uses the conventional memory that is available to support the MEMLIB and MEMCACHE options.
In 32-bit environments starting with Windows XP Professional and above, the Lock pages in memory security setting must be set, so that each user who is running SAS has access to the extended memory. If a user does not have the correct permissions, then SAS will issue a warning message to the log.
Note: In the Local Security Policy window, you might see two check boxes: the Local Security Setting check box and the Effective Policy Setting check box. If the Effective Policy Setting check box is not selected for the users that you added, you will need to reboot your computer so that the new security settings will take effect.
01-02-2012 10:40 PM
This doesn't work on my system (9.3 on Win7x64). I get the following error message in the log even after I have changed the lock pages in memory option. (I recall that I previously got it work by disabling UAC, but I don't want to do that).
options memcache=4 ;
proc means data=hes.hes10bh;run;
ERROR: Cannot adjust the token privileges with error 1300. User probably does not have the right
to lock pages in memory.
WARNING: Some installed physical memory may not be accessible. This may cause unexpected out of
01-13-2012 02:34 PM
Same issue here.
The first time in a session when I create a table in a memlib library I get the same:
libname myMemLib "c:\temp" memlib;
ERROR: Cannot adjust the token privileges with error 1300. User probably does not have the right to lock pages in memory.
WARNING: Some installed physical memory may not be accessible. This may cause unexpected out of memory conditions.
<no error or warning>
libname myMemLb2 "c:\temp\2" memlib;
<no error or warning>
Error message appears after modifying security policy and also after running as admin.