G
Guest
Running on an HP Notebook with WINDOWS/XP HOME SP2 with all current WINDOWS
updates installed. The Notebook is on a network with two other WINDOWS/XP
HOME computers using file and printer sharing and sharing an internet
connection.
When I schedule a task through the system Task Scheduler I get an error
message "An error has occurred while attempting to set task account
information. The specific error is 0x8007007a: the data area passed to a
system call is too small". I've located some KB articles that seem to match
this and have applied (or tried to apply) the suggested fixes but that has
not changed the behavior.
I've tried booting with all non-Microsoft services disabled and with none of
the program I usually start up at WINDOWS startup. The only non-Microsoft
service that is running -- because I am unable to disable it via msconfig --
is the ZoneAlarm TrueVector service. I'm looking into why the ZoneAlarm
service cannot be disabled. The reason I discount the probability of
ZoneAlarm being "the culprit" is that I am running ZoneAlarm on one of the
other computers in this network and it does not exhibit the problem behavior
with Task Scheduler.
Any suggestions or observations will be appreciated.
TIA,
Phil
updates installed. The Notebook is on a network with two other WINDOWS/XP
HOME computers using file and printer sharing and sharing an internet
connection.
When I schedule a task through the system Task Scheduler I get an error
message "An error has occurred while attempting to set task account
information. The specific error is 0x8007007a: the data area passed to a
system call is too small". I've located some KB articles that seem to match
this and have applied (or tried to apply) the suggested fixes but that has
not changed the behavior.
I've tried booting with all non-Microsoft services disabled and with none of
the program I usually start up at WINDOWS startup. The only non-Microsoft
service that is running -- because I am unable to disable it via msconfig --
is the ZoneAlarm TrueVector service. I'm looking into why the ZoneAlarm
service cannot be disabled. The reason I discount the probability of
ZoneAlarm being "the culprit" is that I am running ZoneAlarm on one of the
other computers in this network and it does not exhibit the problem behavior
with Task Scheduler.
Any suggestions or observations will be appreciated.
TIA,
Phil