From: Seiya on
Thanks for helping, i troubleshoot very carefully but i haven't resolved it
yet.
I checked ST log and the task doesn't appear on it when it randomly doesn't
run.
LAN on the PC is always on and every Matlab Task have a domain account
password.
Other task, for example a batch backup job, runs correctly instead of Matlab
job that sometimes doesn't start.
I think that there is a kind of incompatibility between third party
application job and Windows Task Scheduler.
I've found a Hotfix on Microsoft.com for this problem but it is included on
SP2 and on the pc is installed SP3.
Thanks Vanguard for signature's tip.

Cheers



From: Jose on
On May 20, 11:34 am, "Seiya" <se...(a)mailinator.com> wrote:
> Thanks for helping, i troubleshoot very carefully but i haven't resolved it
> yet.
> I checked ST log and the task doesn't appear on it when it randomly doesn't
> run.
> LAN on the PC is always on and every Matlab Task have a domain account
> password.
> Other task, for example a batch backup job, runs correctly instead of Matlab
> job that sometimes doesn't start.
> I think that there is a kind of incompatibility between third party
> application job and Windows Task Scheduler.
> I've found a Hotfix on Microsoft.com for this problem but it is included on
> SP2 and on the pc is installed SP3.
> Thanks Vanguard for signature's tip.
>
> Cheers

Stop the Scheduler Service and delete the schedlgu.txt log file,
restart the service to create a new log file (as mentioned before).

Take a look at the Properties of your afflicted task and adjust the
parameters so it is 5 minutes in the future to start.

In explorer, browse to c:\windows\tasks and maximize the window and
adjust the columnar display so you can see:

Last Run Time, Next Run Time, Status, last Result

Enjoy a cool beverage for 6 minutes.

If 6 minutes goes by and you feel your task has not started, report
the results of the columns and then open the log file and copy/paste
the results here. Don't post a bunch of stuff from other tasks long
ago. The log file should be new, fresh and small.

Can anyone get this command to work without an exception error:

schtasks /query /v



From: VanguardLH on
Seiya wrote:

> I checked ST log and the task doesn't appear on it when it randomly
> doesn't run. LAN on the PC is always on and every Matlab Task have a
> domain account password. Other task, for example a batch backup job,
> runs correctly instead of Matlab job that sometimes doesn't start. I
> think that there is a kind of incompatibility between third party
> application job and Windows Task Scheduler. I've found a Hotfix on
> Microsoft.com for this problem but it is included on SP2 and on the
> pc is installed SP3.


What is the state (enabled or disabled) for the following option in the
scheduled event?
_
|_| Run only if logged on

If that option is enabled then the event can only run when you are
logged on. If disable, you must specify the account (Run As) under
which that event will run.

Check your power options. Maybe your computer is configured to power
down, hibernate, or go into standby mode. Besides not being able to
start jobs under these low-power states, the network interface might
also be disabled at those times. So configure your power options to
never go into a low-power mode and retest. Otherwise, you need to
enable the option in the scheduled event to wake your computer in order
to run the task.

If you are using a mapped drive to get at the program or its files then
perhaps your host isn't connected to that networked drive at the time
the scheduled tasks will run. The file server can terminate idle
connections to it to eliminate users that have been sloppy in leaving
those connections open for no purpose. Don't use mapped drive
designators (D:, M:, S:, or whatever drive letter you used in mapping a
drive letter to a networked drive). Instead use UNC path names, like
\\server\path to access the program.

The Task Scheduler merely runs the same command that you could enter at
a command prompt. So it is likely the state of your computer at the
scheduled time is what causes the program to not be executable.
From: Seiya on
@Jose: I Stopped ST service and recreated a new log file then i
restarted it. All ST columns are clearly visible so, if the error appears
again, i'll post it here.

@Vanguard: "Run only if logged on" is disabled, PC goes on Stand-By Mode
after 15 Mins of inactivity, so i checked "Wake your computer in order to
run the task" option.
No mapped drive is used.

Now I'm doing some test to check the job.
Thanks a lot