Task Scheduler Error

[Kim]

Has anyone encountered this problem - I have installed sp2 and when I try to
schedule a task - I get the error described in Article 264522. I have tried
the fix a couple of times to no avail.

This does not occur on sp1.

Any suggestions are greatly appreciated.

Kim

 

[Pegasus \(MVP\)]

Has anyone encountered this problem - I have installed sp2 and when I try to
schedule a task - I get the error described in Article 264522. I have tried
the fix a couple of times to no avail.

This does not occur on sp1.

Any suggestions are greatly appreciated.

Kim

It would be helpful to provide details of the error in this thread
instead of expecting everyone to look up KB 264522.

 

[Kim]

<cut>
SYMPTOMS
When you try to schedule a job with user credentials so that the task runs
as if it were started by the user, you may receive the following error
message:
The new task has been created, but may not run because the account
information could not be set. The specific error is:
0x8007007a: The data area passed to a system call is too small.

CAUSE
This behavior occurs because the buffer that stores the account information
for all scheduled tasks is limited; the buffer puts a limit on the number of
jobs that you can schedule with user credentials. There is no limit on the
number of jobs that you can create without user credentials.
RESOLUTION
To work around this behavior, stop and start the task scheduler service,
wait for 10 to 15 minutes, and then schedule jobs.

There is a scavenger tool in task scheduler that runs 10 minutes after the
service is started. This tool frees the memory that is still being used by
deleted or scheduled jobs.

<paste>

Sorry - didn't realize I needed to do that - here's the info.

Kim Stansel
Public Defenders Office

 

[Pegasus \(MVP\)]

See below.

<cut>
SYMPTOMS
When you try to schedule a job with user credentials so that the task runs
as if it were started by the user, you may receive the following error
message:
The new task has been created, but may not run because the account
information could not be set. The specific error is:
0x8007007a: The data area passed to a system call is too small.

CAUSE
This behavior occurs because the buffer that stores the account information
for all scheduled tasks is limited; the buffer puts a limit on the number of
jobs that you can schedule with user credentials. There is no limit on the
number of jobs that you can create without user credentials.
RESOLUTION
To work around this behavior, stop and start the task scheduler service,
wait for 10 to 15 minutes, and then schedule jobs.

There is a scavenger tool in task scheduler that runs 10 minutes after the
service is started. This tool frees the memory that is still being used by
deleted or scheduled jobs.

I haven't come across this problem but seeing that the cure
prescribed by Microsoft did not work, I suggest you try
walking around the problem by doing this:
- Set the Task Scheduler service account to the account name
you wish to use.
- Schedule your tasks from the Command Prompt with at.exe.

Sorry - didn't realize I needed to do that - here's the info.

You don't "need" to this, but seeing that all contributors to
these newsgroups are volunteers, helping you in their free
time, you would want to make it as easy as possible to
get their advice. Many get turned off when they have to dig
up your references before they know what your post is
all about!

 

[Kim]

Thank you for the info Pegasus but that doesn't really make any sense to
me - I am logged on as administrator and I am trying to setup DiskCleanup to
run when the PC starts up - how will this work running the program from the
command prompt - it would not be a scheduled event then - it would just be
the program running - right?

Kim

 

[Pegasus \(MVP\)]

I do not understand your question.

Your initial problem was that your scheduled jobs
would not run when using the Task Scheduler.

I suggested that you should use at.exe instead of
the Task Scheduler.

I also suggested that you should change the Service
Account for at.exe so that the jobs had the appropriate
access rights.

All this has nothing to do with you logging on as
administrator. Please clarify.