topic Error Message out of no where! in New SAS User

Error Message out of no where!

anweinbe — Fri, 18 Oct 2019 22:11:25 GMT

Good evening all...

I'm quite frustrated and clueless on what to do. I'm using SAS studio through WRDS and have been running the same 900 lines of code without issue for weeks. Tonight I went to run it and I'm getting hundreds of errors.

 ERROR: A lock is not available for TEMP.BIOTECHLIST.DATA.

I'm an getting this error on pretty much everything. Anyone have a clue what is going on? Literally nothing has changed in 3 weeks to the code. I've tried prior versions too and the same issue comes up.

Re: Error Message out of no where!

ballardw — Fri, 18 Oct 2019 23:14:13 GMT

If WRDS data is accessed over a network you be having an issue with any of a number of things that are hopefully temporary.

The next would be if you are working in an environment where multiple people can access the same data and one of your coworkers is using the set in a manner that prevents you from doing anything that doesn't work when the set is locked.

Re: Error Message out of no where!

VDD — Fri, 18 Oct 2019 23:25:41 GMT

One big issue I run into is when I don't have modify or update permission to the files I can create on shared networks/servers.

SAS creates a temp file than it renames the file after the process completes, and if you don't have modify permissions you can not even delete the locked version of the file. While it seems that the file would be in your temp or work folder when it is being created the file may be getting created across the network.

Re: Error Message out of no where!

SASKiwi — Sat, 19 Oct 2019 01:56:02 GMT

How does the TEMP library get defined? Is that done in your code or by WRDS when it creates your SAS session?

Does TEMP point to the same folder location for every SAS session? It will if you define it. If WRDS is defining it then it may or may not point to the same folder every time.

The most likely explanation for your problem is that a previous run of your program crashed leaving a rogue SAS process still locking that dataset in TEMP. Only the SAS administrators at WRDS can fix this type of problem. Is there a help desk you can log this problem with?