Windows XP - Task Scheduler

J

Joe

Task Scheduler Jobs Will Not Run

I receive the following error in a Window Pop Up:
0x8007007a: The data area passed to a system call is too
small.

I find the following in the Task Scheduler Log for the
two tasks I attempted to change/run.

"McAfee.com Update Check (D8NGZ131-Owner).job"
(mcupdate.exe) 2/3/2004
9:54:00 AM ** ERROR **
The attempt to retrieve account information for
the specified task failed; therefore, the task did not
run. Either an error
occurred, or no account information existed for the task.
The specific error is:
0x80070534: No mapping between account names and
security IDs was done.
"Backup.job" (Program) 2/3/2004 9:54:17 AM ** ERROR **
The attempt to retrieve account information for
the specified task failed; therefore, the task did not
run. Either an error
occurred, or no account information existed for the task.
The specific error is:
0x8004130f: No account information could be found
in the Task Scheduler security database for the task
indicated.

I already tried deleting files in C:\Documents and
Settings\All Users\ApplicationData\Microsoft\Crypto\RSA\S-
1-5-18. Same symptoms persist.

Any ideas on how to clear this up?

Thanks
 
D

Doug Knox MS-MVP

Are you running the Tasks with the credentials of an account that has a password? Scheduled Tasks must run under a username that has a password, as well as sufficient rights to actually execute the program.
 
J

Joe

I created an "Admin" account with full privilege. When I
attempt to change the account name and/or password is
when I get the error.

Its my sisters computer, so I don't get to do a lot of
trial and error without traveling. Do you think it would
help if I deleted all Scheduled Tasks and started over?

Thanks,
Joe
-----Original Message-----
Are you running the Tasks with the credentials of an
account that has a password? Scheduled Tasks must run
under a username that has a password, as well as
sufficient rights to actually execute the program.
--
Doug Knox, MS-MVP Windows XP/ Windows Smart Display
Win 95/98/Me/XP Tweaks and Fixes
http://www.dougknox.com
--------------------------------
Per user Group Policy Restrictions for XP Home and XP Pro
http://www.dougknox.com/xp/utils/xp_securityconsole.htm
--------------------------------
Please reply only to the newsgroup so all may benefit.
Unsolicited e-mail is not answered.

"Joe" <[email protected]> wrote in
message news:[email protected]...
 
M

Mike Reed

I have encountered the same problem with Task Scheduler at DOZENS of
client sites over the years, where tasks may run flawlessly for days
or weeks, then magically - they stop running (listing Could Not Start
for the status). I simply have to edit the task by REENTERING the
SAME password - that was there in the first place - and we're off and
running for several more days/weeks! This has been a problem in
Windows NT 4.0(sp6a) SERVERs AND XP Prof workstations. And no
surprise, since XP probably uses some of the same underlying code as
NT! I have talked with other consultants - and we've all concluded
that Microsoft's task scheduler is "unreliable at best". I would love
to find out the real cause of the problem and solve this once and for
all!!!! More info: generally a single domain exists, YES user
account associated with task ALWAYS has/had a password...

SchedLog1.txt reports: The attempt to retrieve account information
for the specified task failed; therefore, the task did not run. Either
an error occurred, or no account information existed for the task.
The specific error is: 0x8004130f: No account information could be
found in the Task Scheduler security database for the task indicated.

How does Windows lose the "account information"? I can log in as this
user without a problem!

Thanks to all,

-Mike
 
S

Stewart

I just posted this today. Hope it helps.

While this makes little sense, I was able to resolve
the "0x8007007a: The data passed to a system call is too
small" issue by completing the following steps:

1. Run msconfig.
2. Under General, select "Selective Startup".
3. Under Services, select "Hide all Microsoft Services"
then disable all 3rd party services.
4. Reboot.
5. Verify that the error no longer occurs. If the error
still occurs then this solution will not work.
6. Run msconfig.
7. Under General, select "Normal Startup".
8. Under Services, select "Hide all Microsoft Services"
then enable all 3rd party services.

My guess is that XP was somehow caching some corrupt
information that was reset/cleared by disabling/enabling
3rd party services. All I know is that this worked for me
after trying everything else I could think of and placing
a call to Microsoft. The person I spoke to was tier 1 and
simply following his checklist and had no idea why it
worked.

On the bright side, I did receive a full refund after
repeatedly stating how ridiculous it was to charge me for
a solution that they were not aware of and could not
explain.

Anyway, I noticed a fair amount of people were
experiencing this same issue and I hope this "resolution"
works for you.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top