You can use GetExitCode to return the reason it
couldn't start. One thing to check is that the user
account it's running under has the log on as batch job
privilege.
Roger
> Thank you, Roger, for pointing that out. I tried the
> test sample and it did create the scheduler object as
> one would expect.
>
> However, same as the at.exe attempt I did from CLI,
> the object doesn't run when the time came. I manually
> requested "Run" and the task runs fine (with the
> message dialog poping up).
>
> I retried several times by playing around with the
> settings (manually entering password and so forth) but
> nothing worked.
>
> Any clues?
>
> Thanks,
>
_______________________________________________
Python-win32 mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-win32
