Access to the path denied in SAS Enterprise Guide

[suncawy]

Hello,

     When I edit a SAS program in Enterprise Guide and try to save the program I get the error "Access to the path 'C:\Users\E716666\AppData\Local\Temp\SEG6712\SDSPID6712\

0f424283774e4ea988e04abde16467d.sas' is denied.  The version of Enterprise Guide is 4.3.   I have the SAS program saved on our UNIX server, but I don't know why when saving it that it tries saving the edit on the C drive.    The program on UNIX has the write/read attribute, but can't seem to save the edit in Enterprise Guide.   Anyone have any ideas ?

Thank you.   

[ChrisHemedinger]

I'm not sure why you're getting the error.  But I can say that EG caches a local copy of the program -- it does not edit it directly on your UNIX file system.  When you open it in EG, it makes a local copy for you to work on, then when you save it (or close it) it commits it back to the UNIX system.

Still, not sure what's going on in your particular case.  SAS Tech Support can help with diagnostics steps.

Chris

[Kolli]

I had the same problem earlier today. I am able to resolve it by uncheking the folders Read-only  and Hidden attributes.

In SASEG

1)  File -> Open -> Other

2) in Look in:  drop down

Go to C:\Users\E716666\

Right click on each fiolder and subfolder of your path  ,

      uncheck  Read-only  and Hidden attributes for each sub folder.

C:\Users\E716666\AppData\Local\Temp\SEG6712\SDSPID6712

I guess the error will go away. Try it and let us know.

Thanks.

[suncawy]

When I tried doing this, it did not help.   For some reason, it automatically went back to having the read only attribute checked again.  This being a machine that I don't have administrative privileges on, only our IT team does, might have something to do with it.   I think that I will try to recreate the directory altogether to see if that works.

[slg]

First, it appears you do not have r/w access to the location where you are trying to save (i.e., \AppData\Local\Temp\SEG6712\SDSPID6712\)... and unchecking "Read" may not be sufficient to allow you to write to the location. If you are in the admin group (or are admin) to your local OS (windows), you can give yourself r/w access to the location by modifying the folder property (using windows explorer)

Second I suggest you don't do the above and simply "save as" the file to somewhere else on your desktop (such as your local EG/SAS folder)

[DavidWard]

I just managed to recreate this on a new platform I've just built while setting up LDAP sync. 9.4M4 with EG7.13 on Linux. I'm recording the solution here so people can find it while googling for it.

The solution for this is that while EG says it's the %temp% file that the user doesn't have access to, it's actually the real/server file system that there's no access. I created the original file as sasdemo_cod which had 644 permission in Linux. I ended up deleting that user from metadata and switched to sasdemo_prod in EG. I triggered the error trying to save it.

On the filesystem, I changed it to 666, removed the file from the project, added it back, and all was well. The evidence can be shown in the EG log while set to debug (excerpt pasted below).

Cheers,

David. 

2018-02-07 13:56:14,937 [Main] DEBUG SAS.EG.SDS.Model.Creator [(null)] - Leave: CreateFile(). Successfully found file "LDAPsync.sas"
2018-02-07 13:56:14,937 [Main] DEBUG SAS.EG.ProjectElements.LinkedFile [(null)] - Attempting to Cache LinkedFile "/sasconfig/meta/Lev3/SASMeta/SASEnvironment/SASCode/Jobs/LDAPsync.sas" with mode 6 and local extension ".sas".
2018-02-07 13:56:14,937 [Main] DEBUG SAS.BI.SASComb.Method [(null)] - InvokeMethod::AssignFileref
2018-02-07 13:56:14,952 [Main] DEBUG SAS.BI.SASComb.Method [(null)] - Creating object 0x11.
2018-02-07 13:56:14,952 [Main] DEBUG SAS.BI.SASComb.Method [(null)] - IFileref::Represents an assigned fileref in the associated SAS Workspace.
2018-02-07 13:56:14,952 [Main] DEBUG SAS.BI.SASComb.Method [(null)] - Adding to VTBL::Parent(7,3), 1 parameters
2018-02-07 13:56:14,952 [Main] DEBUG SAS.BI.SASComb.Method [(null)] - Adding to VTBL::FilerefName(8,4), 1 parameters
2018-02-07 13:56:14,952 [Main] DEBUG SAS.BI.SASComb.Method [(null)] - Adding to VTBL::OpenTextStream(9,5), 3 parameters
2018-02-07 13:56:14,952 [Main] DEBUG SAS.BI.SASComb.Method [(null)] - Adding to VTBL::OpenBinaryStream(10,6), 2 parameters
2018-02-07 13:56:14,952 [Main] DEBUG SAS.BI.SASComb.Method [(null)] - Adding to VTBL::OpenTranscodedBinaryStream(11,7), 4 parameters
2018-02-07 13:56:14,952 [Main] DEBUG SAS.BI.SASComb.Method [(null)] - Adding to VTBL::ListMembers(12,8), 5 parameters
2018-02-07 13:56:14,952 [Main] DEBUG SAS.BI.SASComb.Method [(null)] - Adding to VTBL::AssignMember(13,9), 6 parameters
2018-02-07 13:56:14,952 [Main] DEBUG SAS.BI.SASComb.Method [(null)] - Adding to VTBL::DeleteFile(14,10), 0 parameters
2018-02-07 13:56:14,952 [Main] DEBUG SAS.BI.SASComb.Method [(null)] - Leaving for AssignFileref
2018-02-07 13:56:14,952 [Main] DEBUG SAS.BI.SASComb.Method [(null)] - InvokeMethod::OpenTextStream
2018-02-07 13:56:14,952 [Main] INFO SAS.BI.SASComb [(null)] - Error received from SAS:-1:4a661191-a58f-11d2-b95d-00c04f81bc00-<?xml version="1.0" ?><Exceptions><Exception><SASMessage severity="Error">Insufficient authorization to access /sasconfig/meta/Lev3/SASMeta/SASEnvironment/SASCode/Jobs/LDAPsync.sas.</SASMessage></Exception></Exceptions>-0-00000000-0000-0000-0000-000000000000-SAS.Fileref
2018-02-07 13:56:14,952 [Main] DEBUG SAS.BI.SASComb.Method [(null)] - Leaving for OpenTextStream
2018-02-07 13:56:14,952 [Main] DEBUG SAS.BI.SASComb.Method [(null)] - InvokeMethod::DeassignFileref
2018-02-07 13:56:14,952 [Main] DEBUG SAS.BI.SASComb.Method [(null)] - Leaving for DeassignFileref
2018-02-07 13:56:14,952 [Main] DEBUG SAS.EG.ProjectElements.LinkedFile [(null)] - Exception occurred when attempting to Cache LinkedFile.
SAS.EG.SDS.SDSException: <?xml version="1.0" ?><Exceptions><Exception><SASMessage severity="Error">Insufficient authorization to access /sasconfig/meta/Lev3/SASMeta/SASEnvironment/SASCode/Jobs/LDAPsync.sas.</SASMessage></Exception></Exceptions> ---> System.Runtime.InteropServices.COMException: <?xml version="1.0" ?><Exceptions><Exception><SASMessage severity="Error">Insufficient authorization to access /sasconfig/meta/Lev3/SASMeta/SASEnvironment/SASCode/Jobs/LDAPsync.sas.</SASMessage></Exception></Exceptions>
at SAS.IFileref.OpenTextStream(StreamOpenMode Mode, Int32 MaxLineLength)
at SAS.EG.SDS.Model.SASTextTransfer.GetFile(String remotePath, String localPath, eAccessMode mode)
--- End of inner exception stack trace ---
at SAS.EG.SDS.Model.SASTextTransfer.GetFile(String remotePath, String localPath, eAccessMode mode)
at SAS.EG.SDS.Model.SASFileService.GetFile(String remotePath, String localPath, eAccessMode mode)
at SAS.EG.SDS.Model.File.Cache(eAccessMode mode, eExtensionOption extFlag, String extension)
at SAS.EG.ProjectElements.LinkedFile.Cache()

[DavidWard]

don't you hate it when text is converted to emoticons? 😉 😛

[jeffrey_sarazin_ssc_spc_gc_ca]

Do you have a local copy of SAS installed on your workstation (PC SAS)?

Jeff

Message was edited by: jeffrey Sarazin We had similar issues here from the SAS users. We told the uses to rename the dataset when moving from PC SAS to EG because of libname naming issues.

[suncawy]

Yes, I have PC SAS.  So, when I do have to save,  I bring the program down to PC SAS and make the necessary change.  Then, after the change I put the program back onto the UNIX directory.   It's a pain because I'm having to do that.   Whats funny is I can run that program just fine, but I just can't save any edits when I'm in Enterprise Guide.

[suncawy]

Well, here is something that is strange...On the UNIX system, we have 2 folders in which we can store our programs.  The first one is  apps/sas/datasets/data47/COSMC, this is the directory that I can't save to with Enterprise Guide.   However, when I save the program to our other directory apps/sas/datasets/data48/COSMC, then it saves the program without problem.   So, for whatever reason, the data47 directory is either corrupted or I lack certain permissions to it.