topic Re: error message: user does not have appropriate authorization level for library WORK in SAS Procedures

error message: user does not have appropriate authorization level for library WORK

EvaVDG — Mon, 26 Mar 2012 11:34:10 GMT

Dear all,

When I run a macro, I often get the error message 'user does not have appropriate authorization level for library WORK'.

Does anyone has had a similar problem and knows how to solve this?

Many thanks,

Eva

error message: user does not have appropriate authorization level for library WORK

Doc_Duke — Mon, 26 Mar 2012 12:25:10 GMT

not the usual. You probably need to provide the log to show the error in context.

error message: user does not have appropriate authorization level for library WORK

EvaVDG — Mon, 26 Mar 2012 13:07:00 GMT

Thanks for you response but the log is not very enlightening. It simply states the error message I wrote and consequently states problems renaming datasets in the work library, which SAS cannot get access too so it places that file in temp...

Problem is that it doesn't happen allways but once in a while (and at the moment, I cannot get an error so no log to attach).

error message: user does not have appropriate authorization level for library WORK

alisoft — Tue, 27 Mar 2012 16:20:38 GMT

You need to modify the policies in SASWork folder.this depend in your setup..

Re: error message: user does not have appropriate authorization level for library WORK

PaigeMiller — Fri, 29 Jun 2012 14:45:30 GMT

Now I am having the same problem. Yes, I have checked, I have write permission to the appropriate WORK folder.

If I run the same program and use a server location as my WORK folder, the problem goes away. But this is not a good solution to constantly be writing temporary files across the network to a server location.

Has anyone found a solution to this problem?

Re: error message: user does not have appropriate authorization level for library WORK

PaigeMiller — Fri, 29 Jun 2012 15:21:19 GMT

Okay, browsing the web using that new-fangled Google thing, I found the following solution which seems to have fixed the problem

http://support.sas.com/kb/40/459.html