Well, my network username was entered on both tasks.  I hadn't previously
entered any password on the task that runs the VB app, and it's been
running fine.   But anyway, now I entered my network password in both
tasks... can
hardly wait till tomorrow morning to see whether they run tonight!

> From: "Rich" 
> This is a multi-part message in MIME format.
> ------=_NextPart_000_0418_01C2E97A.87172C80
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
> The task scheduler uses the user name and password to log in when =
> creating the batch session in which the job runs.  You need a valid =
> account and password.
> Rich
> "Ellen Kronick"  wrote
in message =
> news:c09ff4.6d7729{at}harborwebs.com...
> Being that I happily discovered I can get to Dale's mirror from work, =
> here I am
> with a question.
> I have a VB standalone executable set to run every night at 10:30.  =
> It's been
> running fine for weeks.  It processes a file that gets previously =
> ftp'd down
> from a unix box by another app.  We decided it would be more efficient =
> for me
> to set up the ftp download to run independently instead of depending =
> on the
> other process.   So I made a batch file that calls a little script, =
> and set
> Task Scheduler to run it every night at 10:00.   (The ftp piece only =
> takes a
> few seconds.)=20
> This morning I came in and found no log file or error file from my VB =
> process,
> so I went and looked in Task Scheduler and saw the status of both =
> tasks was
> "Could not start".  The Task Scheduler log reports as follows:
> "ftpPD.job" (ftpPD.bat) 3/12/2003 10:00:00 PM ** ERROR **
> The attempt to log on to the account associated with the task =
> failed,
> therefore, the task did not run.
> The specific error is:
> 0x8007052e: Logon failure: unknown user name or bad password.
> Verify that the task's Run-as name and password are valid and =
> try again
> .
> "WritePDInfoToConsultas.job" (WritePDInfoToConsultas.exe) 3/12/2003 =
> 10:30:00 PM
> ** ERROR **
> The attempt to log on to the account associated with the task =
> failed,
> therefore, the task did not run.
> The specific error is:
> 0x8007052e: Logon failure: unknown user name or bad password.
> Verify that the task's Run-as name and password are valid and =
> try again
> .
> I leave my box turned on and myself logged into it 24/7, I just use =
> the logon=20
> screensaver.   As noted above, this problem has never occurred before. =
> I did
> not have to boot up or log on when I came in this morning, and in fact =
> the
> familiar Novell message about the drives I got kicked off at 2:30 a.m. =
> was
> there, so it's not a power outage or something.
> It was my understanding that the password dialog in Task Scheduler is =
> for an
> APP that needs a password, therefore I never put my logon password =
> into it for
> the VB app, and as noted it's been running fine for weeks.
> HELP!
> TIA
> ------=_NextPart_000_0418_01C2E97A.87172C80
> Content-Type: text/html;
> charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
> 
> 
>  charset=3Diso-8859-1">
> 
> 
> 
> 
>    The
task scheduler uses =
> the user name=20
> and password to log in when creating the batch session in which the job=20
> runs.  You need a valid account and password.
>  
> Rich
>  
>  style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
> BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
> "Ellen Kronick" < =
>
href=3D"Ellen.Kronick{at}harborwebs.com=">mailto:Ellen.Kronick{at}harborwebs.com">Ellen.Kronick{at}harborwebs.com=
> >=20
> wrote in message  =
>
href=3D"news:c09ff4.6d7729{at}harborwebs.com">news:c09ff4.6d7729{at}harborwebs.=
> com...Being=20
> that I happily discovered I can get to Dale's mirror from work, here I =
> amwith a question.I have a VB standalone
executable set to =
> run=20
> every night at 10:30.  It's beenrunning fine for
weeks.  =
> It=20
> processes a file that gets previously ftp'd downfrom a unix box by =
> another=20
> app.  We decided it would be more efficient for meto set up =
> the ftp=20
> download to run independently instead of depending on theother=20
> process.   So I made a batch file that calls a little =
> script, and=20
> setTask Scheduler to run it every night at
10:00.   (The =
> ftp=20
> piece only takes afew seconds.) This
morning I came in and =
> found=20
> no log file or error file from my VB process,so I went and looked =
> in Task=20
> Scheduler and saw the status of both tasks was"Could not =
> start".  The=20
> Task Scheduler log reports as
follows:"ftpPD.job" (ftpPD.bat)=20
> 3/12/2003 10:00:00 PM ** ERROR=20
>
**       
The attempt to log on =
> to the=20
> account associated with the task failed,therefore, the task did =
> not=20
>
run.       
The specific error=20
>
is:       
0x8007052e: Logon =
> failure:=20
> unknown user name or bad=20
>
password.       
Verify that =
> the task's=20
> Run-as name and password are valid and try=20
> again."WritePDInfoToConsultas.job" =
> (WritePDInfoToConsultas.exe)=20
> 3/12/2003 10:30:00 PM** ERROR=20
>
**       
The attempt to log on =
> to the=20
> account associated with the task failed,therefore, the task did =
> not=20
>
run.       
The specific error=20
>
is:       
0x8007052e: Logon =
> failure:=20
> unknown user name or bad=20
>
password.       
Verify that =
> the task's=20
> Run-as name and password are valid and try
again.I leave =
> my box=20
> turned on and myself logged into it 24/7, I just use the logon=20
> screensaver.   As noted above, this
problem has never =
> occurred=20
> before.   I didnot have to boot up or log
on when I came =
> in this=20
> morning, and in fact thefamiliar Novell message about the drives I =
> got=20
> kicked off at 2:30 a.m. wasthere, so it's not a power outage or=20
> something.It was my understanding that the
password dialog in =
> Task=20
> Scheduler is for anAPP that needs a password, therefore I never =
> put my=20
> logon password into it forthe VB app, and as noted it's been =
> running fine=20
> for
weeks.HELP!TIA

--- BBBS/NT v4.01 Flag-4