Date:         Wed, 21 Sep 2005 09:02:34 -0700
Reply-To:     "Pardee, Roy" <pardee.r@GHC.ORG>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         "Pardee, Roy" <pardee.r@GHC.ORG>
Subject:      Re: Scheduled Task Could not start
Comments: To: Connor <jboland@NYISO.COM>
Content-Type: text/plain; charset="US-ASCII"

Is the scheduled task service definitely starting?

Is there anything interesting in your system or application event logs
around the time of these failures?

Any difference if you delete these old tasks & create new, equivalent
ones?

I vaguely recall having a problem w/that service starting b/c somehow
the SYSTEM account's "full control" permission to my c: drive was broken
at some point in the folder heirarchy.  If you think that's what's going
on, say so & I'll try and dig up the KB article.

HTH,

-Roy

-----Original Message-----
From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of
Connor
Sent: Wednesday, September 21, 2005 7:05 AM
To: SAS-L@LISTSERV.UGA.EDU
Subject: Scheduled Task Could not start

I had my computer , which is running on Windows XP with SAS 9.1.3 and
Enterprise Guide 3.0 , reimaged.
Prior to the reimaging I had four(4) scheduled tasks running from
Enterprise Guide with a VB script and all was well.
After the reimaging I am forced to apparently reset the password , which
has not changed , each day in order to get any of the tasks to run.
When I check the scheduled tasks in the morning I see the message "could
not start" for each of the tasks . I set the password , which I do not
change , again and the click run and each task runs successfully. I
called SAS and included cscript in front of the location of the VB
script location and the problem still is the same.
The problem does not occur when I schedule the tasks on my other desktop
computer which is also running on Windows XP with SAS 9.1.3 and
Enterprise Guide 3.0 .
Any help would be greatly apprecaited.