Here's my story:
Win10x64 system, multiple users, lab environment, AD-bound. All can log and launch the application, but the person who has installed it (and has local administrative rights, of course) gets this:
ERROR: Invalid physical name for library SASUSER.
NOTE: Unable to initialize the options subsystem.
ERROR: (SASXKINI): PHASE 3 KERNEL INITIALIZATION FAILED.
ERROR: Unable to initialize the SAS kernel.
The same happens when he tries to elevate the execution by "run as administrator". I assume it's something ins \UserProfile\AppData that is causing it, but what? I am not that eager to change any paths pointing to a shared directory since it works for others.
SAS 9.4 software has downloaded and been installed properly. Previously this system had 9.3, which was acting the same way.
Suggestions would be very appreciated. Thanks in advance!
Try this as a test from the Windows Run prompt:
sas -sasuser "c:\temp"
If there is no c:\temp directory then create it before running the test. If this starts SAS successfully then the current SASUSER directory has likely been corrupted and needs to be cleared. The folder used by the SASUSER library is defined in sasv9.cfg - search the hard drive to find this.
Do all your users have a local SAS installation?
If "all users" means more than three, you should seriously consider switching to a server-based setup, as that reduces the maintenance effort drastically.
Edit: from a later post I take it that you do have a server, so that sasuser.v94 should be under the "home" directory of that particular user.
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.
Learn how to install the SAS Viya CLI and a few commands you may find useful in this video by SAS’ Darrell Barton.
Find more tutorials on the SAS Users YouTube channel.