Scheduled Task Fails.

  • Thread starter Thread starter Waz Up
  • Start date Start date
W

Waz Up

I've schedule a task (shutdown - not the MS version) to run at a certain
time. When I run this program "Manually" all works well. However the
schedule task fails.

The account I use has admin privs, but DOES not have a password. I suspect
that is the issue.

Having said that, I run WinTvPVR and have serveral scheduled recordings that
run under the same account without fail.

What am I missing?

(System: WinXP, SP2 etc.)

Thanks.
 
Hi Waz Up,

That's the reason. You will need at least a one character password or the
Task Scheduler cannot create a security token with enough privileges to run
the task.

Good Luck,

Good luck,
CreateWindow - http://mymessagetaker.com
 
Open the SchedLgU.txt and see what you can see.

Start | Run | Type: SchedLgU.txt | Click OK

C:\WINDOWS\SchedLgU.txt

Or, Open Scheduled Tasks.
On the Advanced menu, click View Log.

Troubleshooting Scheduled Tasks
Paste the following line into Start | Run and click OK...

hh mstask.chm::/TS_troubleshoot.htm

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
 
Hi Wesley, here is the excerpt from the log:
<<< Start
"Auto Shutdown.job" (shutdown.exe) 4/23/2007 7:17:00 PM ** ERROR **
The attempt to log on to the account associated with the task failed,
therefore, the task did not run.
The specific error is:
0x8007052f: Logon failure: user account restriction. Possible reasons are
blank passwords not allowed, logon hour restrictions, or a policy
restriction has been enforced.
Verify that the task's Run-as name and password are valid and try again.
I've reviewed the help file and (of cours) it makes referrence to an invalid
login (i.e. blank password).

I buy into the Blank Password thing, but as i mentioned in my post, WinTVpvr
runs schedule recordings using the SAME account (i.e. mine) and there is no
password attached to this account. As an SE and MCT, I understand that this
is a "Bad Thing", but I'm researching this for a client to find out why
certain tasks will run "Without a password", while others fail.

Thanks

Waz Up
 
0x8007052f: Logon failure: user account restriction
http://www.google.com/search?hl=en&...r+account+restriction"&btnG=Search&lr=lang_en

Scheduled Tasks cannot run with a blank password
http://support.microsoft.com/kb/310715

Unless you bypass the password restriction, with Local Policies or a tweak
from Kelly, blank password scheduled tasks won't run
http://groups.google.com/group/micr...15631?lnk=st&q=&rnum=1&hl=en#c1d552d687e15631

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
 
Wesley, I tried something rather interesting.

I copied an exisiting schedueld task (one that has my account - with a blank
password). I simply changed the app that was to run and voila it worked.

I'm not sure why, and according to all the web posts (including the links
you gave me) this should not have worked, but alas it did.

Waz Up.
 
Check the setting of limitblankpassworduse, if set to 0, no password needed
for Scheduled Tasks. WinTV-PVR, which I never heard of and know nothing
about, may have changed the setting.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
Value name: limitblankpassworduse
Data Type: REG_DWORD
Value Data: 0 (disabled) 1 (enabled)

limitblankpassworduse is Enabled, set to 1, by default.

In Windows XP Professional only.
Group Policy Editor (Start | Run | gpedit.msc)
Computer Configuration\Windows Settings\Security Settings\
Local Policies\Security Options\
Accounts: Limit local account use of blank passwords to console logon only
If Enabled here, limitblankpassworduse value of 1.

Or Local Security Policy (Start | Run | secpol.msc)
Security Settings\Local Policies\Security Options\
Accounts: Limit local account use of blank passwords to console logon only
If Enabled here, limitblankpassworduse value of 1.

Limit local account use of blank passwords to console logon only
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/636.mspx?mfr=true

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
 
Back
Top