Desktop productivity for business analysts and programmers

Access to the path denied in SAS Enterprise Guide

Reply
Contributor
Posts: 24

Access to the path denied in SAS Enterprise Guide

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.   


Community Manager
Posts: 2,693

Re: Access to the path denied in SAS Enterprise Guide

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

N/A
Posts: 1

Re: Access to the path denied in SAS Enterprise Guide

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.

Contributor
Posts: 24

Re: Access to the path denied in SAS Enterprise Guide

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.

Occasional Contributor slg
Occasional Contributor
Posts: 6

Re: Access to the path denied in SAS Enterprise Guide

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)

Re: Access to the path denied in SAS Enterprise Guide

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.

Contributor
Posts: 24

Re: Access to the path denied in SAS Enterprise Guide

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.

Contributor
Posts: 24

Re: Access to the path denied in SAS Enterprise Guide

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.

Ask a Question
Discussion stats
  • 7 replies
  • 1410 views
  • 1 like
  • 5 in conversation