SAS err msg ？！

[hellohere]

anyone knows  the one below?

ERROR:  Windows error code: 21 in hc_disk_normal_read for
                          E:\sastemp\_TD16080_LAPTOP-LF4NQTV2_\sastmp-000000005.sas7butl

Work with pc/sas, ever session to restart sas, get this and need reboot sas.

[yabwon]

Do you have any backup program working in the background? The "hc_disk_normal_read" sounds like a lock, or something similar. 

But I guess SAS team can give you more insights. 

Bart

[Kurt_Bremser]

To which type of device does the drive letter E: point?

[ChrisHemedinger]

Assuming E: is a network drive or an occasionally connected drive (like an external drive), the error message usually indicates that SAS cannot reach the location. Maybe that drive that became unmapped or unavailable for some reason...

[Quentin]

Weird.  Can you show more of your log?  Is it just one step that causes this error message?  Is it a SORT step, PROC SQL step, DATA step....

When you restart do you get this error every time the first step runs that reads from disk, or does it change as to which step throws an error?

[DaveHorne]

Hi, a couple of comments/suggestions:

From the path, this looks like the SASWORK location, and it's strongly recommended to be on a fast local drive for best performance and reliability (NVME, SATA SSD, striped RAID array even).  The SAS utility files are heavy on I/O and having saswork on the network can lead to a performance bottleneck (and dependence on other potential network "issues").

On Windows, I tend to avoid mapped drives in general (use the full path to the network location which is less sensitive to Windows drive mapping reliability).  Plus, your SAS job will be more "portable" if run on a different PC or server.  If it's a long path, perhaps set a macro variable at the beginning of your program to make it easier in subsequent libname or file path locations.

Depending on your code, there may be other options to reduce or minimize I/O.

Hope this helps.