Undetermined I/O failure when sending email via Server

[Stu1979]

Dear all,

Need you help on the following: I am trying to send an email via SAS Base 9.2 (code below) from a server, which I connect remotely. The idea is to run this on a batch overnight.

The problem is that the code runs perfectly via batch when I am connected remotely, i.e., when I am logged in. However, when I am not, the email is not sent and the following error is generated on the log:

ERROR: Undetermined I/O failure.

NOTE: The SAS System stopped processing this step because of errors.

I really need the help of someone. I am using gmail via outlook. I look to all threats on the internet, already tried everything with no success whatesoever. Any help is appreciated. tks!

Code:

filename outbox email "xxx@gmail.com"

  to=("aaa@bbb")

  subject="SAS Routine - Batch";

data _null_;

  file outbox;

  put "Dear all, routine has successfully completed.";

run;

[rpillay_csumb_edu]

Hello there,

I am going through the same problem now. Were you able to resolve this issue? Thanks.

[TomKari]

How are you submitting the code when you are not connected?

[rpillay_csumb_edu]

I am running a batch job using Windows Powershell. I am connected but SAS fails in the final email step where I am trying to send an email with a summary. I have an email to SAS tech support but they seemed to be baffled themselves at the moment. When running the job in EG SAS sends the email without any problems.

[ChrisHemedinger]

When running in the batch job, do you know if SAS has the -EMAIL* options set properly? Check PROC OPTIONS GROUP=EMAIL; RUN; in EG and compare to the same in the batch process.

Chris

[TomKari]

Are you running SAS in batch from Powershell, or using Powershell to run Enterprise Guide using the scripting interface?

Tom

[rpillay_csumb_edu]

Yes THANK YOU   Proc Options Group=email; showed me that the batch job is setup for MAPI email system. - just need an Options statement for EMAILSYS=SMTP

[regulator]

This is an old thread but the thing that was causing the error  for us was the Windows Search and Indexing service. Turning off indexing on the drive and disabling Windows Search fixed the issue.