SAS for Windows 10 I/O error when writing log file externally

[achansen]

When I run my program using SAS for Windows 10 and write the log file to an external file (.log), I get an I/O error when the log is at least 97,000 rows. When I run the same program and the same data using a machine with Windows 7, I have no I/O errors. The successful log is 5.4 MB. Is there a limit on the external log files in SAS for Windows 10?

Here is my log routing code:

%let tmstmp = %sysfunc( putn( %sysfunc( date() ), yymmddn8. ))_%sysfunc( compress( %sysfunc( putn( %sysfunc( time() ), tod5. )), ':' ));
filename mylog "M:\2019\SAS-DailyRun\Logs-DailyRun\DailyRun_&tmstmp..log";
proc printto log=mylog; run;

/*and then the code that processes the data*/

proc printto LOG =LOG;RUN;

[ballardw]

---

@achansen wrote:

When I run my program using SAS for Windows 10 and write the log file to an external file (.log), I get an I/O error when the log is at least 97,000 rows. When I run the same program and the same data using a machine with Windows 7, I have no I/O errors. The successful log is 5.4 MB. Is there a limit on the external log files in SAS for Windows 10?

What error do you get?

Some details may help.

Does the Windows 7 job write to the exact same location? If not, it may be something about the location such as available space, permissions or a setting from your IT folks limiting your use. If it is the exact same location are the user permissions exactly the same?

[SASKiwi]

It looks like you are writing to a file server based folder. Is this an intermittent problem or does it always occur for this job? Do you have another Win 10 PC you can test this on? If so does it have the same problem. If not it could be a hardware problem with your PC. If yes, then I suggest it is a problem specific to Windows 10, not necessarily a SAS problem.

I suggest you check your Windows 10 event log to see if the error is recorded. 

[Ksharp]

Could you use BATCH process(a.k.a  use OS command run   .bat  file    ) to get that LOG file ?