Hi,
I have SAS 9.4 and Enterprise guide 7.15 HF3. When I try to make encrypted data, I get error message pop-up window with text:
"The open data operation failed. The following error occured.
[Error] Invalid ENCRYPTKEY value for WORK.SALARY.DATA."
There is no errors in log.
I use example from sas support data step pages, option ENCRYPTKEY.
data salary(encrypt=aes encryptkey=green);
input name $ yrsal bonuspct;
datalines;
Muriel 34567 3.2
Bjorn 74644 2.5
Freda 38755 4.1
Benny 29855 3.5
Agnetha 70998 4.1
;
run;
If I do run same code in basic SAS, there isn't any errors.
Is this bug in Enterprise Guide or something else?
Regars,
Harri S
Enterprise guide does not yet support aes-encrypted data sets. It is on our list to add in a future release. A workaround is to create a view based on the encrypted data set, which will allow you to open it in Eguide.
data encrypt_salary(encrypt=aes encryptkey=green);
input name $ yrsal bonuspct;
datalines;
Muriel 34567 3.2
Bjorn 74644 2.5
Freda 38755 4.1
Benny 29855 3.5
Agnetha 70998 4.1
;
data encrypt_salaryV / view=encrypt_salaryV;
set encrypt_salary(encryptkey=green);
run;
Enterprise guide does not yet support aes-encrypted data sets. It is on our list to add in a future release. A workaround is to create a view based on the encrypted data set, which will allow you to open it in Eguide.
data encrypt_salary(encrypt=aes encryptkey=green);
input name $ yrsal bonuspct;
datalines;
Muriel 34567 3.2
Bjorn 74644 2.5
Freda 38755 4.1
Benny 29855 3.5
Agnetha 70998 4.1
;
data encrypt_salaryV / view=encrypt_salaryV;
set encrypt_salary(encryptkey=green);
run;
The error happens because EG tries to open the dataset for display, but does not have the key value. You need to run proc print to see the data:
proc print data=work.salary (encrypt=aes encryptkey=green);
run;
It might be a good idea if EG gleaned the encryptkey from the log (as it retrieves the dataset name anyway) and used it to open the dataset.
(note that EG does not have a direct viewtable window like Base SAS, which asks for the key, but actually sends a SQL request - or similar - via the IOM bridge).
Possible material for a SASWare Ballot request: "Add the ability to open encrypted datasets by asking for the key"
try setting encrypt = yes.
data salary(encrypt=aes encryptkey=green);
Good news: We've extended SAS Hackathon registration until Sept. 12, so you still have time to be part of our biggest event yet – our five-year anniversary!
Check out this tutorial series to learn how to build your own steps in SAS Studio.
Find more tutorials on the SAS Users YouTube channel.
Ready to level-up your skills? Choose your own adventure.