Maybe it's too late. Have you checked this file:

C:\WINDOWS\SchedLgU.Txt

It should give some clue. 1sep09 records may already been trimmed.

On Tue, 13 Oct 2009 12:29:23 -0400, Nathaniel Wooding <nathaniel.wooding@DOM.COM> wrote:

>Guys > >To switch the discussion, did either of you encounter problems with the windows scheduler starting around Sept. 1. I have a job that runs daily and started having problems with the job failing. I eventually had to delete the scheduled job and then build a new entry. I do not recall the error code but I did find some internet references to it from several years ago when MS pushed out a security update that fouled up scheduled jobs. > >Nat Wooding > >-----Original Message----- >From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of Terjeson, Mark >Sent: Tuesday, October 13, 2009 12:23 PM >To: SAS-L@LISTSERV.UGA.EDU >Subject: Re: Windows scheduler stop running due to change to password > >Hi Ya, > >Either way. (It's totally up to you and your folks there.) > >Mark > > > >-----Original Message----- >From: Huang, Ya [mailto:Ya.Huang@amylin.com] >Sent: Tuesday, October 13, 2009 9:18 AM >To: Terjeson, Mark; SAS-L@LISTSERV.UGA.EDU >Subject: RE: Windows scheduler stop running due to change to password > >Thanks Mark, > >I have two PCs. One is dedicated for the routine run. Another is for my >daily work. >Of course I only have one login account. Does this mean I have to ask >the admin >to set my account to NOT expire? That means my regular PC will not ask >me to >change the password? > >Sounds like I should ask admin to create one special account for the >scheduler box? > >Ya > >-----Original Message----- >From: Terjeson, Mark [mailto:Mterjeson@russell.com] >Sent: Tuesday, October 13, 2009 9:12 AM >To: Huang, Ya; SAS-L@LISTSERV.UGA.EDU >Subject: RE: Windows scheduler stop running due to change to password > >Hi Ya, > >Yes, whoever has administrative capabilities can set the special >username's password to NOT expire. >(if they are so inclined to let you talk them into it) > > >Hope this is helpful. > > >Mark Terjeson >Investment Business Intelligence >Investment Management & Research >Russell Investments >253-439-2367 > > >Russell >Global Leaders in Multi-Manager Investing > > > > > > > >-----Original Message----- >From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of Ya >Huang >Sent: Tuesday, October 13, 2009 8:34 AM >To: SAS-L@LISTSERV.UGA.EDU >Subject: Windows scheduler stop running due to change to password > >Hi there, > >I have a routine SAS run via windows xp scheduler. The way it was set up >is to have username and password specified, so that even when the PC is >logged off, it still can run. But the problem is that every 3 months, >system force us to change the password. Most time after I change the >password, I forget to change the password in the scheduler, which lead >to failed SAS run. I wonder if there is way to not specifying the >username and password, and the scheduler still run even when the PC is >logged off. > >Thanks > >Ya >CONFIDENTIALITY NOTICE: This electronic message contains >information which may be legally confidential and or privileged and >does not in any case represent a firm ENERGY COMMODITY bid or offer >relating thereto which binds the sender without an additional >express written confirmation to that effect. The information is >intended solely for the individual or entity named above and access >by anyone else is unauthorized. If you are not the intended >recipient, any disclosure, copying, distribution, or use of the >contents of this information is prohibited and may be unlawful. If >you have received this electronic transmission in error, please >reply immediately to the sender that you have received the message >in error, and delete it. Thank you.