I get this message from time to time on mailsends, and I can trace it back to me outputting a variable that i have not written anything too.

Today, however, i get this message on EVERY mailsend, and I can verify that all variables are there & populated, and all files are available.

a typical line would read:

mailsendwithattachment "from@me.com","",emailList,subject,message,filelist

where emaillist, subject, & message are populated strings, and file list is a string containing a comma sperated list of files.

Everything has worked wonderfuly up until today, and I have rebooted the box, removed temp files, etc. I have also moved 24x7 & the job .dat file to another machine and get the same error.

Insight ?

Maybe it is trying to resend some old message. Can you reproduce the problem after restarting the scheduler?

: I get this message from time to time on mailsends, and I can trace it back to
: me outputting a variable that i have not written anything too.

: Today, however, i get this message on EVERY mailsend, and I can verify that
: all variables are there & populated, and all files are available.

: a typical line would read: mailsendwithattachment
: "from@me.com","",emailList,subject,message,filelist

: where emaillist, subject, & message are populated strings, and file list
: is a string containing a comma sperated list of files.

: Everything has worked wonderfuly up until today, and I have rebooted the box,
: removed temp files, etc. I have also moved 24x7 & the job .dat file to
: another machine and get the same error.

: Insight ?

: Maybe it is trying to resend some old message. Can you reproduce the problem
: after restarting the scheduler?

Yes ... restarted scheduler & rebooted the machine repeatedly. This was consistant across two different servers.

I have tracked it down to being related to the holiday check (20th, being a holiday, and those programs contained @dl)

Not all programs failed, just those 2-3 email sends .. while others were fine after a reboot.

Where does 24x7 create temp files for email sends ? I thought I cleared them all out ..

It creates them in the directory pointed by TEMP environment variable for the user account running 24x7. Yes, I am sure the problem is not there. Deleting temp files will not help if you have a job it keeps retrying and creating new empty emails again.

: Yes ... restarted scheduler & rebooted the machine repeatedly. This was
: consistant across two different servers.

: I have tracked it down to being related to the holiday check (20th, being a
: holiday, and those programs contained @dl)

: Not all programs failed, just those 2-3 email sends .. while others were fine
: after a reboot.

: Where does 24x7 create temp files for email sends ? I thought I cleared them
: all out ..

: It creates them in the directory pointed by TEMP environment variable for the
: user account running 24x7. Yes, I am sure the problem is not there.
: Deleting temp files will not help if you have a job it keeps retrying and
: creating new empty emails again.

It was not creating empty emails. This was how I could get this error in the *usual* sense. In this case it was crating perfectly valid emails, just giving this error.