Scheduled Task (Could not be start)

[Wilson Cheung]

Hello all,

I recently configuring a task and it executes every Monday to Friday, from
9am - 5 pm, and it runs in every 1 minute. However, I found that the task
cannot be started every next day. The error said "Could not be start".

How can I resume the task again is re-input my password again in Scheduled
Task daily. Then the task may executes again in every 1 minute and stop @
5pm. But of course, I need to re-input again in the next day to resume again.

Does anyone know why? How can I solve this problem to prevent "re-input"
password daily in the morning? Please help me, with many thanks!

 

[Daniel Crichton]

Re: Scheduled Task (Could not be start)

Wilson wrote on Thu, 2 Aug 2007 02:52:02 -0700:

> Hello all,

> I recently configuring a task and it executes every Monday to Friday,
> from 9am - 5 pm, and it runs in every 1 minute. However, I found that
> the task cannot be started every next day. The error said "Could not
> be start".

> How can I resume the task again is re-input my password again in
> Scheduled
> Task daily. Then the task may executes again in every 1 minute and stop
> @
> 5pm. But of course, I need to re-input again in the next day to resume
> again.

> Does anyone know why? How can I solve this problem to prevent
> "re-input"
> password daily in the morning? Please help me, with many thanks!

I get this occassionally on my XP machine when I run out of virtual memory
and the Crypto store file seems to get partially corrupted - the only
solution is to edit every task and re-enter the password. I've taken to
backing up the Crypto file daily, at least now if it happens I can just copy
it over the flawed one and all my tasks work again. It was happening daily
when I had a process kicking off a large ZIP using the pkzip command line
version, since I replaced this with a VB6 app using the zlib library I've
had it recur only once (and that was this Saturday when I had a couple of
large month end processes kick off and eat up all the virtual memory, I've
changed the schedules to try to ensure this doesn't happen again).

On my XP PC here the location for the file is

C:\Documents and Settings\All Users\Application
Data\Microsoft\Crypto\RSA\S-1-5-18\

I'm not sure if it's the same place on 2000/2003, but it's worth looking.

Dan

 

[Wilson Cheung]

Re: Scheduled Task (Could not be start)

Thanks Daniel. Do you mean there is only one solution is re-enter password
everyday?

"Daniel Crichton" wrote:

> Wilson wrote on Thu, 2 Aug 2007 02:52:02 -0700:
>
> > Hello all,
>
> > I recently configuring a task and it executes every Monday to Friday,
> > from 9am - 5 pm, and it runs in every 1 minute. However, I found that
> > the task cannot be started every next day. The error said "Could not
> > be start".
>
> > How can I resume the task again is re-input my password again in
> > Scheduled
> > Task daily. Then the task may executes again in every 1 minute and stop
> > @
> > 5pm. But of course, I need to re-input again in the next day to resume
> > again.
>
> > Does anyone know why? How can I solve this problem to prevent
> > "re-input"
> > password daily in the morning? Please help me, with many thanks!
>
> I get this occassionally on my XP machine when I run out of virtual memory
> and the Crypto store file seems to get partially corrupted - the only
> solution is to edit every task and re-enter the password. I've taken to
> backing up the Crypto file daily, at least now if it happens I can just copy
> it over the flawed one and all my tasks work again. It was happening daily
> when I had a process kicking off a large ZIP using the pkzip command line
> version, since I replaced this with a VB6 app using the zlib library I've
> had it recur only once (and that was this Saturday when I had a couple of
> large month end processes kick off and eat up all the virtual memory, I've
> changed the schedules to try to ensure this doesn't happen again).
>
> On my XP PC here the location for the file is
>
> C:\Documents and Settings\All Users\Application
> Data\Microsoft\Crypto\RSA\S-1-5-18\
>
> I'm not sure if it's the same place on 2000/2003, but it's worth looking.
>
> Dan
>
>
>

 

[Daniel Crichton]

Re: Scheduled Task (Could not be start)

No, make a copy of the file in the Crypto folder and when you get problems
just copy that backup over the existing one - I did mention that in my
reply. However, long term you will want to find out what is causing the
problem - from my own experiences I had programs run that would cause my PC
to run out of virtual memory causing this file to become corrupted. You will
want to try to find out what is causing your issue and either workaround it
or report it to MS as a bug.

Dan

Wilson wrote on Thu, 2 Aug 2007 06:16:05 -0700:

> Thanks Daniel. Do you mean there is only one solution is re-enter
> password everyday?

> "Daniel Crichton" wrote:

>> Wilson wrote on Thu, 2 Aug 2007 02:52:02 -0700:

>>> Hello all,

>>> I recently configuring a task and it executes every Monday to
>>> Friday, from 9am - 5 pm, and it runs in every 1 minute. However, I
>>> found that the task cannot be started every next day. The error
>>> said "Could not be start".

>>> How can I resume the task again is re-input my password again in
>>> Scheduled
>>> Task daily. Then the task may executes again in every 1 minute and
>>> stop @
>>> 5pm. But of course, I need to re-input again in the next day to
>>> resume again.

>>> Does anyone know why? How can I solve this problem to prevent
>>> "re-input"
>>> password daily in the morning? Please help me, with many thanks!

>> I get this occassionally on my XP machine when I run out of virtual
>> memory and the Crypto store file seems to get partially corrupted -
>> the only solution is to edit every task and re-enter the password.
>> I've taken to backing up the Crypto file daily, at least now if it
>> happens I can just copy it over the flawed one and all my tasks work
>> again. It was happening daily when I had a process kicking off a
>> large ZIP using the pkzip command line version, since I replaced
>> this with a VB6 app using the zlib library I've had it recur only
>> once (and that was this Saturday when I had a couple of large month
>> end processes kick off and eat up all the virtual memory, I've
>> changed the schedules to try to ensure this doesn't happen again).

>> On my XP PC here the location for the file is

>> C:\Documents and Settings\All Users\Application
>> Data\Microsoft\Crypto\RSA\S-1-5-18\

>> I'm not sure if it's the same place on 2000/2003, but it's worth
>> looking.

>> Dan