DATA Step, Macro, Functions and more

WARNING: Unable to copy SASUSER registry to WORK registry.

Accepted Solution Solved
Reply
New Contributor
Posts: 4
Accepted Solution

WARNING: Unable to copy SASUSER registry to WORK registry.

I am trying to start a second SAS v9.4 session on Windows 7. I get the following warning nin the log at startup:

 

WARNING: Unable to copy SASUSER registry to WORK registry. Because of this,
WARNING: you will not see registry customizations during this session.

 

I would like to have the same customizations in all sessions. I read that adding the -RSAUSER option to the command line would cause the SASUSER registry to be read-only and alleviate this problem. I changed the shortcut from:

 

"C:\Program Files\SASHome\SASFoundation\9.4\sas.exe" -CONFIG "C:\Program Files\SASHome\SASFoundation\9.4\nls\en\sasv9.cfg"

to

"C:\Program Files\SASHome\SASFoundation\9.4\sas.exe" -CONFIG "C:\Program Files\SASHome\SASFoundation\9.4\nls\en\sasv9.cfg" -RSAUSER

 

Then I get an error at startup:

 

ERROR: Unrecognized SAS option name RSAUSER.
ERROR: (SASXKRIN): KERNEL RESOURCE INITIALIZATION FAILED.
ERROR: Unable to initialize the SAS kernel.

 

Any suggestions?

 

Thanks,

Matt

 


Accepted Solutions
Solution
a month ago
Super User
Posts: 10,500

Re: WARNING: Unable to copy SASUSER registry to WORK registry.

If the command line you show is the one you actually used, which seem likely given the error text, then you misspelled RSASUSER.

View solution in original post


All Replies
Solution
a month ago
Super User
Posts: 10,500

Re: WARNING: Unable to copy SASUSER registry to WORK registry.

If the command line you show is the one you actually used, which seem likely given the error text, then you misspelled RSASUSER.

New Contributor
Posts: 4

Re: WARNING: Unable to copy SASUSER registry to WORK registry.

Thanks! Yes that was it, I kept reading it as RSA USER instead of R SAS USER.
☑ This topic is SOLVED.

Need further help from the community? Please ask a new question.

Discussion stats
  • 2 replies
  • 154 views
  • 2 likes
  • 2 in conversation