SAS jobs fail between after 5PM.

[jdeisenm]

Some users I support report their SAS jobs are failing between 5pm and 9pm. Apparently the jobs run just fine at all other times.

One usere reports, "SAS could not access to those directories in the middle of running the programs and was not able to delete those "temporary" libraries at the end of the run."

F:\TEMP\TEMP\_TDxxxx

The box is a windows 2000 server running terminal services and the server guys say windows is working fine.

Can this be a windows or SAS memory issue or what??? Any help would me much appreciated.

 

[klaz2002]

jdeidenm,
I would have the IT guys look over the box and the network that they are on. I had the same issue with a server and found that a backup app started up at 11pm every night. Guess what time I had set my SAS job to run, yup 11pm. When the IT guys informed me that the backup app started at 11 I simply moved up my SAS job to 10:30pm as it was a very short program.

I bet that there is a conflict with another application that is locking the folders that your SAS program needs to run.

Let us know what you find.
Klaz

 

[jdeisenm]

The server guys say the backups start at 11pm. Additionally they disabled antivirus on the box. That didn't help. This is a windows 2000 terminal server. Are they any sas specific config options to check or windows settings for a sas box?

 

[ChrisW75]

Post your log file, we have issues like this all the time.

One thing to watch for is other processes running at the same time. For instance, we once had a user submit a job which used results from another SAS program. However, the other SAS program was still running so their program failed as the datasets were locked.

Generally it's some sort of conflict or some other process which is hogging resources. Post the log (or at least the errors, make sure you take out any passwords and anything that might be a bit sensitive) and I'll have a look.