I had been successfully using jt.exe to schedule tasks from my Vb
app. Suddenly it stopped working under XP when using the "Run when
logged in" option. When I check the status to see why it didn't run,
it says "SCHED_E_ACCOUNT_INFORMATION_NOT_SET". I'm wondering if an XP
update came out which killed that functionality? I tried using
schtasks but that doesn't not even have that option, so I'm required
to enter a password or run as SYSTEM. I tried the Win32_ScheduledJob
API also, but that doesn't give me the ability to do it either. Is
there currently any way to schedule a task from a VB application and
have it run when logged in (not requiring a password)? I don't mind
prompting the user for their Windows password if I have to, but in
some cases the user doesn't have one set, and I don't want them to
have to set one just to be able to use my program. I see tons of
other programs use the scheduler without asking for a password. How
can I do this?

On 27 Aug, 03:38, ramzi.au...******.com wrote:
> I had been successfully using jt.exe to schedule tasks from my Vb
> app. Suddenly it stopped working under XP when using the "Run when
> logged in" option. When I check the status to see why it didn't run,
> it says "SCHED_E_ACCOUNT_INFORMATION_NOT_SET". I'm wondering if an XP
> update came out which killed that functionality? I tried using
> schtasks but that doesn't not even have that option, so I'm required
> to enter a password or run as SYSTEM. I tried the Win32_ScheduledJob
> API also, but that doesn't give me the ability to do it either. Is
> there currently any way to schedule a task from a VB application and
> have it run when logged in (not requiring a password)? I don't mind
> prompting the user for their Windows password if I have to, but in
> some cases the user doesn't have one set, and I don't want them to
> have to set one just to be able to use my program. I see tons of
> other programs use the scheduler without asking for a password. How
> can I do this?

If you're wanting to launch an app when the user logs on and have it
run in their security context why not just stick a shortcut in their
Startup directory or add a command to the Run key in the registry?