Windows 2000 Task Scheduler Error 0x8007000d: The data is invalid.

[Robert Reed]

Full error message is :
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:
0x8007000d: The data is invalid.

Account permissions or security rights are not the issue.

Cannot View "Hidden Tasks" from the "Advanced" tab of "Control SchedTasks"
"Hidden Tasks" is not available.

This is a relatively new install and the box was promoted to a DC after
installation. I can find lot of references to this error for Win2003 as a
shadow copy issue but this is a Win2000 installation so this is not
applicable since 2000 does not run shadow copy.

I suspect a corrupt task scheduler database as referred to in this community
posting:
http://www.microsoft.com/technet/co...=en-us-technet-win2ksrv&lang=en&cr=US&m=1&p=1

The posting refers to a tool SysTaskFix.exe which I cannot locate.

Any assistance or suggestions on this issue or download location of
SysTaskFix.exe would be greatly appreciate!

 

[Dave Patrick]

You might try deleting the possibly corrupt jobs from

%systemroot%\Tasks\*.job

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"Robert Reed" wrote:
> Full error message is :
> 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:
> 0x8007000d: The data is invalid.
>
> Account permissions or security rights are not the issue.
>
> Cannot View "Hidden Tasks" from the "Advanced" tab of "Control SchedTasks"
> "Hidden Tasks" is not available.
>
> This is a relatively new install and the box was promoted to a DC after
> installation. I can find lot of references to this error for Win2003 as a
> shadow copy issue but this is a Win2000 installation so this is not
> applicable since 2000 does not run shadow copy.
>
> I suspect a corrupt task scheduler database as referred to in this
> community
> posting:
> http://www.microsoft.com/technet/co...=en-us-technet-win2ksrv&lang=en&cr=US&m=1&p=1
>
> The posting refers to a tool SysTaskFix.exe which I cannot locate.
>
> Any assistance or suggestions on this issue or download location of
> SysTaskFix.exe would be greatly appreciate!

 

[Robert Reed]

Dave, I think the issue here is that these tasks were hidden and do not
appear in the tasks folder so that is no way to delete the tasks... and since
the view hidden tasks is not an option from the Advanced tab (for whatever
reason - I'm thinking a corrupt hidden task) I don't have a way to get to the
possibly corrupt hidden job tasks.

Perhaps I have followed Alice through the looking glass so if there are
other causes or solutions I'm open but at a loss as to what they might be

"Dave Patrick" wrote:

> You might try deleting the possibly corrupt jobs from
>
> %systemroot%\Tasks\*.job
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
> "Robert Reed" wrote:
> > Full error message is :
> > 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:
> > 0x8007000d: The data is invalid.
> >
> > Account permissions or security rights are not the issue.
> >
> > Cannot View "Hidden Tasks" from the "Advanced" tab of "Control SchedTasks"
> > "Hidden Tasks" is not available.
> >
> > This is a relatively new install and the box was promoted to a DC after
> > installation. I can find lot of references to this error for Win2003 as a
> > shadow copy issue but this is a Win2000 installation so this is not
> > applicable since 2000 does not run shadow copy.
> >
> > I suspect a corrupt task scheduler database as referred to in this
> > community
> > posting:
> > http://www.microsoft.com/technet/co...=en-us-technet-win2ksrv&lang=en&cr=US&m=1&p=1
> >
> > The posting refers to a tool SysTaskFix.exe which I cannot locate.
> >
> > Any assistance or suggestions on this issue or download location of
> > SysTaskFix.exe would be greatly appreciate!
>

 

[Dave Patrick]

AFAIK creating hidden tasks on Windows 2000 is not an option.

From a command prompt

AT

should list them.


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"Robert Reed" wrote:
> Dave, I think the issue here is that these tasks were hidden and do not
> appear in the tasks folder so that is no way to delete the tasks... and
> since
> the view hidden tasks is not an option from the Advanced tab (for whatever
> reason - I'm thinking a corrupt hidden task) I don't have a way to get to
> the
> possibly corrupt hidden job tasks.
>
> Perhaps I have followed Alice through the looking glass so if there are
> other causes or solutions I'm open but at a loss as to what they might be

 

[Robert Reed]

Dave yes I think you are right my error - so hidden tasks are not the issue.

What I'm dealing with here is a third party application setting a task to
run a .cmd against a MS SQL Express DB. I can create and run the .cmd just
fine by setting a Task in the Task Scheduler. When the application sets the
task, the task results in the error message.

I've used FileMon and the task is set and kicked off by task scheduler but
never completes and the error is found in the log. I THINK the task exsisted
(set by the application) prior to promotion of the box to DC and ran fine,
post promotion the task is set but errors out.

"Dave Patrick" wrote:

> AFAIK creating hidden tasks on Windows 2000 is not an option.
>
> From a command prompt
>
> AT
>
> should list them.
>
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
> "Robert Reed" wrote:
> > Dave, I think the issue here is that these tasks were hidden and do not
> > appear in the tasks folder so that is no way to delete the tasks... and
> > since
> > the view hidden tasks is not an option from the Advanced tab (for whatever
> > reason - I'm thinking a corrupt hidden task) I don't have a way to get to
> > the
> > possibly corrupt hidden job tasks.
> >
> > Perhaps I have followed Alice through the looking glass so if there are
> > other causes or solutions I'm open but at a loss as to what they might be
>

 

[Dave Patrick]

Can you edit the task properties? The application probably wasn't intended
to be installed on a DC


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"Robert Reed" wrote:
> Dave yes I think you are right my error - so hidden tasks are not the
> issue.
>
> What I'm dealing with here is a third party application setting a task to
> run a .cmd against a MS SQL Express DB. I can create and run the .cmd just
> fine by setting a Task in the Task Scheduler. When the application sets
> the
> task, the task results in the error message.
>
> I've used FileMon and the task is set and kicked off by task scheduler but
> never completes and the error is found in the log. I THINK the task
> exsisted
> (set by the application) prior to promotion of the box to DC and ran fine,
> post promotion the task is set but errors out.

 

[Robert Reed]

My understanding is that the task script (the .cmd) is set as a task by the
application in task scheduler and in fact the task does exist because it
runs, and fails (evidenced by the task scheduler log entries) but the task is
not visible. My understanding is that the task created by the application
SHOULD be visible in task scheduler. Since the task is not visible the
properties cannot be edited.

The cmd script executes perfectly when the task is setup manually throught
the task scheduler.


"Dave Patrick" wrote:

> Can you edit the task properties? The application probably wasn't intended
> to be installed on a DC
>
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
> "Robert Reed" wrote:
> > Dave yes I think you are right my error - so hidden tasks are not the
> > issue.
> >
> > What I'm dealing with here is a third party application setting a task to
> > run a .cmd against a MS SQL Express DB. I can create and run the .cmd just
> > fine by setting a Task in the Task Scheduler. When the application sets
> > the
> > task, the task results in the error message.
> >
> > I've used FileMon and the task is set and kicked off by task scheduler but
> > never completes and the error is found in the log. I THINK the task
> > exsisted
> > (set by the application) prior to promotion of the box to DC and ran fine,
> > post promotion the task is set but errors out.
>

 

[Dave Patrick]

Is it not visible from the command line?

AT

should list them. Can you turn off the application feature and use the task
that you've manually created?


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"Robert Reed" wrote:
> My understanding is that the task script (the .cmd) is set as a task by
> the
> application in task scheduler and in fact the task does exist because it
> runs, and fails (evidenced by the task scheduler log entries) but the task
> is
> not visible. My understanding is that the task created by the application
> SHOULD be visible in task scheduler. Since the task is not visible the
> properties cannot be edited.
>
> The cmd script executes perfectly when the task is setup manually throught
> the task scheduler.

 

[Robert Reed]

Dave,

Running AT at the command line results in: "There are no entries in the list"

There are currently two visible scheduled tasks in the task scheduler

Am I missing a switch here? I have tasks scheduled on other servers and they
also return the same response from the AT at command line

I am using the manually created tasks as a workaround but this is not ideal
as running certain tasks from the application console is just easier and more
reliable for the occasional need of the non-tech user... for forcing backups
etc etc...

Thanks,

Robert


"Dave Patrick" wrote:

> Is it not visible from the command line?
>
> AT
>
> should list them. Can you turn off the application feature and use the task
> that you've manually created?
>
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
> "Robert Reed" wrote:
> > My understanding is that the task script (the .cmd) is set as a task by
> > the
> > application in task scheduler and in fact the task does exist because it
> > runs, and fails (evidenced by the task scheduler log entries) but the task
> > is
> > not visible. My understanding is that the task created by the application
> > SHOULD be visible in task scheduler. Since the task is not visible the
> > properties cannot be edited.
> >
> > The cmd script executes perfectly when the task is setup manually throught
> > the task scheduler.
>

 

[Dave Patrick]

I think you'll need to contact the application developer for a solution. It
sounds like their app is not intended to be run from a DC since a DC doesn't
have a local accounts database.

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"Robert Reed" wrote:
> Dave,
>
> Running AT at the command line results in: "There are no entries in the
> list"
>
> There are currently two visible scheduled tasks in the task scheduler
>
> Am I missing a switch here? I have tasks scheduled on other servers and
> they
> also return the same response from the AT at command line
>
> I am using the manually created tasks as a workaround but this is not
> ideal
> as running certain tasks from the application console is just easier and
> more
> reliable for the occasional need of the non-tech user... for forcing
> backups
> etc etc...
>
> Thanks,
>
> Robert

 

[Robert Reed]

Thanks for your help Dave I am following up with the developer. We have been
running the application for a number of years on this server as a DC before
the "reinstall" of the server.

Thanks again for your help,

Robert



"Dave Patrick" wrote:

> I think you'll need to contact the application developer for a solution. It
> sounds like their app is not intended to be run from a DC since a DC doesn't
> have a local accounts database.
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
> "Robert Reed" wrote:
> > Dave,
> >
> > Running AT at the command line results in: "There are no entries in the
> > list"
> >
> > There are currently two visible scheduled tasks in the task scheduler
> >
> > Am I missing a switch here? I have tasks scheduled on other servers and
> > they
> > also return the same response from the AT at command line
> >
> > I am using the manually created tasks as a workaround but this is not
> > ideal
> > as running certain tasks from the application console is just easier and
> > more
> > reliable for the occasional need of the non-tech user... for forcing
> > backups
> > etc etc...
> >
> > Thanks,
> >
> > Robert
>

 

[Dave Patrick]

Ok, maybe you can find out from the developer what account is being used for
the scheduled task.

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"Robert Reed" wrote:
> Thanks for your help Dave I am following up with the developer. We have
> been
> running the application for a number of years on this server as a DC
> before
> the "reinstall" of the server.
>
> Thanks again for your help,
>
> Robert

 

[Robert Reed]

Dave,

I WAS able to resolve the issue this MSKB article helped
http://support.microsoft.com/kb/822904
Once the d42 files were deleted no more errors and the application console
work as it should.

I had seen this article but could not find the refered to dir.

I used Filemon to verify that this was not an account or permissions issue
and noticed the call to the folder and files refered to in the KB article and
with the help of filemon was able to delete the file.

I still don't understand why it worked but it did!

Robert

"Dave Patrick" wrote:

> Ok, maybe you can find out from the developer what account is being used for
> the scheduled task.
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
> "Robert Reed" wrote:
> > Thanks for your help Dave I am following up with the developer. We have
> > been
> > running the application for a number of years on this server as a DC
> > before
> > the "reinstall" of the server.
> >
> > Thanks again for your help,
> >
> > Robert
>

 

[Dave Patrick]

Good news. Thanks for letting us know the solution.

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"Robert Reed wrote:
> Dave,
>
> I WAS able to resolve the issue this MSKB article helped
> http://support.microsoft.com/kb/822904
> Once the d42 files were deleted no more errors and the application console
> work as it should.
>
> I had seen this article but could not find the refered to dir.
>
> I used Filemon to verify that this was not an account or permissions issue
> and noticed the call to the folder and files refered to in the KB article
> and
> with the help of filemon was able to delete the file.
>
> I still don't understand why it worked but it did!
>
> Robert