0x800706fc : The trust relationship between the primary domain and the trusted domain failed

hi All

I have one WinXP SP2 machine join to Win2003 AD server

I had also created several NT task scheduler at this WinXP machine, all the
while the scheduler run without any issue

Recently, the NT task scheduler is having an issue and return 'could not
start' at the status column, when I double click on the task, it appear
below error msg

0x800706fc : The trust relationship between the primary domain and the
trusted domain failed
An error has occured attempting retrieve task account information. You may
continue editing the task object, but will be unable to change task account
information

The account information was blank, the job just stop running, i had delete
off the job and recreate it and run again, it run without issue, but it will
reoccur after few day

The above might point to trust relationship between the PC and Domain, BUT i
manage to login to this WinXP machine on any newly created user ID without
any issue, so i think it might not be trust issue, but i will give it a try
by rejoin it to domain.

kindly advice

Thanks a lot

Try running the support tool netdiag on that XP Pro computer. It will let
you know if their is a problem with the secure channel between the
workstation and a domain controller.

Steve


"gbkhor" wrote in message
...
hi All

I have one WinXP SP2 machine join to Win2003 AD server

I had also created several NT task scheduler at this WinXP machine, all
the while the scheduler run without any issue

Recently, the NT task scheduler is having an issue and return 'could not
start' at the status column, when I double click on the task, it appear
below error msg

0x800706fc : The trust relationship between the primary domain and the
trusted domain failed
An error has occured attempting retrieve task account information. You may
continue editing the task object, but will be unable to change task
account information

The account information was blank, the job just stop running, i had delete
off the job and recreate it and run again, it run without issue, but it
will reoccur after few day

The above might point to trust relationship between the PC and Domain, BUT
i manage to login to this WinXP machine on any newly created user ID
without any issue, so i think it might not be trust issue, but i will give
it a try by rejoin it to domain.

kindly advice

Thanks a lot

"gbkhor" wrote:

The account information was blank, the job just stop running, i had delete
off the job and recreate it and run again, it run without issue, but it will
reoccur after few day

I have met this problem where any event scheduled under a non-system account
mysteriously loses its credentials after a long period of successful
operation. Not sure why this happens but it appears to be a scheduler bug.
Don't think it's a domain issue either as I've had it happen on standalones.
Password expiry could of course be the culprit, but in this case it was
definitely not responsible, a RunAs test indicating that the account itself
was still functional.

Hi Anteaus

then, what action had u taken?

Thanks

"Anteaus" wrote in message
...
"gbkhor" wrote:

The account information was blank, the job just stop running, i had
delete
off the job and recreate it and run again, it run without issue, but it
will
reoccur after few day

I have met this problem where any event scheduled under a non-system
account
mysteriously loses its credentials after a long period of successful
operation. Not sure why this happens but it appears to be a scheduler bug.
Don't think it's a domain issue either as I've had it happen on
standalones.
Password expiry could of course be the culprit, but in this case it was
definitely not responsible, a RunAs test indicating that the account
itself
was still functional.

Auto-logon, then use a third-party task scheduler.

Run control userpasswords2

Actually, this approach is more-or-less mandated for NAS backup since in
XP-onward, network shares are userized, so it's necessary to maintain a
single account for all services that need LAN access.

Securitywise the screen can be locked if required, this will not prevent the
task running so long as a logon has been completed beforehand.

"gbkhor" wrote:

Hi Anteaus

then, what action had u taken?