• Welcome to Tux Reports: Where Penguins Fly. We hope you find the topics varied, interesting, and worthy of your time. Please become a member and join in the discussions.

Why is schedule task not running?

E

Eric

Flightless Bird
I am using XP with SP3 and office 2003, and just setup password for my user
account by using "control userpasswords2" command, in order to use schedule
task, the task to open file.xls is tested fine in this morning, but the
worksheet requests confirmation on macro's security as it opened. Before
setting password, I can skip this security's confirmation by assign a
selfcert for vertification, and it works fine. Once the username password has
changed, the macro's security dialogue pops up again, and the option "Always
trust macros from this publisher" is greyed out.
When I try to remove username's password under control panel, and reopen the
worksheet, then it works fine with selfcert, but schedule task cannot be
performed based on schedule. Is there any conflict between selfcert and
username's password?
Does anyone have any suggestions/
Thanks in advance for any suggestions
Eric
 
P

Pegasus [MVP]

Flightless Bird
"Eric" <Eric@discussions.microsoft.com> wrote in message
news:1640925F-0864-40F8-BF1B-7BB5E8E386A6@microsoft.com...
> I am using XP with SP3 and office 2003, and just setup password for my
> user
> account by using "control userpasswords2" command, in order to use
> schedule
> task, the task to open file.xls is tested fine in this morning, but the
> worksheet requests confirmation on macro's security as it opened. Before
> setting password, I can skip this security's confirmation by assign a
> selfcert for vertification, and it works fine. Once the username password
> has
> changed, the macro's security dialogue pops up again, and the option
> "Always
> trust macros from this publisher" is greyed out.
> When I try to remove username's password under control panel, and reopen
> the
> worksheet, then it works fine with selfcert, but schedule task cannot be
> performed based on schedule. Is there any conflict between selfcert and
> username's password?
> Does anyone have any suggestions/
> Thanks in advance for any suggestions
> Eric

I suspect that your scheduled task is indeed running, in spite of your
subject line, and that it cannot do its job because of some issue with macro
security. An Excel newsgroup would be a much better place to post this
question. Note also that the command "control userpasswords2" does not set
any password. It only allows you to automate the logon process by supplying
a password automatically. If that password is wrong then the automatic logon
process will fail. Why you use "control userpasswords2" in connection with a
scheduled task is unclear - the two have nothing in common. If you want a
task to run automatically then you schedule it to run at boot time or at a
specified time. Waiting for a logon even is unnecessary and will fail under
certain circumstances.
 
E

Eric

Flightless Bird
I forget to set the password on "control userpasswords'
Could you please tell me what the major difference is between "control
userpasswords' and "control userpasswords2"?
Thank you very much for any suggestions
Eric

"Pegasus [MVP]" wrote:

>
>
> "Eric" <Eric@discussions.microsoft.com> wrote in message
> news:1640925F-0864-40F8-BF1B-7BB5E8E386A6@microsoft.com...
> > I am using XP with SP3 and office 2003, and just setup password for my
> > user
> > account by using "control userpasswords2" command, in order to use
> > schedule
> > task, the task to open file.xls is tested fine in this morning, but the
> > worksheet requests confirmation on macro's security as it opened. Before
> > setting password, I can skip this security's confirmation by assign a
> > selfcert for vertification, and it works fine. Once the username password
> > has
> > changed, the macro's security dialogue pops up again, and the option
> > "Always
> > trust macros from this publisher" is greyed out.
> > When I try to remove username's password under control panel, and reopen
> > the
> > worksheet, then it works fine with selfcert, but schedule task cannot be
> > performed based on schedule. Is there any conflict between selfcert and
> > username's password?
> > Does anyone have any suggestions/
> > Thanks in advance for any suggestions
> > Eric
>
> I suspect that your scheduled task is indeed running, in spite of your
> subject line, and that it cannot do its job because of some issue with macro
> security. An Excel newsgroup would be a much better place to post this
> question. Note also that the command "control userpasswords2" does not set
> any password. It only allows you to automate the logon process by supplying
> a password automatically. If that password is wrong then the automatic logon
> process will fail. Why you use "control userpasswords2" in connection with a
> scheduled task is unclear - the two have nothing in common. If you want a
> task to run automatically then you schedule it to run at boot time or at a
> specified time. Waiting for a logon even is unnecessary and will fail under
> certain circumstances.
>
> .
>
 
P

Pegasus [MVP]

Flightless Bird
The command "control userpasswords" does not do anything at all.

"Eric" <Eric@discussions.microsoft.com> wrote in message
news:AC23AC6E-2909-42CF-B442-B1576714D876@microsoft.com...
> I forget to set the password on "control userpasswords'
> Could you please tell me what the major difference is between "control
> userpasswords' and "control userpasswords2"?
> Thank you very much for any suggestions
> Eric
>
> "Pegasus [MVP]" wrote:
>
>>
>>
>> "Eric" <Eric@discussions.microsoft.com> wrote in message
>> news:1640925F-0864-40F8-BF1B-7BB5E8E386A6@microsoft.com...
>> > I am using XP with SP3 and office 2003, and just setup password for my
>> > user
>> > account by using "control userpasswords2" command, in order to use
>> > schedule
>> > task, the task to open file.xls is tested fine in this morning, but the
>> > worksheet requests confirmation on macro's security as it opened.
>> > Before
>> > setting password, I can skip this security's confirmation by assign a
>> > selfcert for vertification, and it works fine. Once the username
>> > password
>> > has
>> > changed, the macro's security dialogue pops up again, and the option
>> > "Always
>> > trust macros from this publisher" is greyed out.
>> > When I try to remove username's password under control panel, and
>> > reopen
>> > the
>> > worksheet, then it works fine with selfcert, but schedule task cannot
>> > be
>> > performed based on schedule. Is there any conflict between selfcert
>> > and
>> > username's password?
>> > Does anyone have any suggestions/
>> > Thanks in advance for any suggestions
>> > Eric
>>
>> I suspect that your scheduled task is indeed running, in spite of your
>> subject line, and that it cannot do its job because of some issue with
>> macro
>> security. An Excel newsgroup would be a much better place to post this
>> question. Note also that the command "control userpasswords2" does not
>> set
>> any password. It only allows you to automate the logon process by
>> supplying
>> a password automatically. If that password is wrong then the automatic
>> logon
>> process will fail. Why you use "control userpasswords2" in connection
>> with a
>> scheduled task is unclear - the two have nothing in common. If you want a
>> task to run automatically then you schedule it to run at boot time or at
>> a
>> specified time. Waiting for a logon even is unnecessary and will fail
>> under
>> certain circumstances.
>>
>> .
>>
 
E

Eric

Flightless Bird
So what does it do? On hibernation mode for XP, when XP wakes up, it requests
for password, do you have any suggestions whether the password is set by
"control userpasswords" or "control userpasswords2"?
Thank you very much for any suggestions
Eric

"Pegasus [MVP]" wrote:

> The command "control userpasswords" does not do anything at all.
>
> "Eric" <Eric@discussions.microsoft.com> wrote in message
> news:AC23AC6E-2909-42CF-B442-B1576714D876@microsoft.com...
> > I forget to set the password on "control userpasswords'
> > Could you please tell me what the major difference is between "control
> > userpasswords' and "control userpasswords2"?
> > Thank you very much for any suggestions
> > Eric
> >
> > "Pegasus [MVP]" wrote:
> >
> >>
> >>
> >> "Eric" <Eric@discussions.microsoft.com> wrote in message
> >> news:1640925F-0864-40F8-BF1B-7BB5E8E386A6@microsoft.com...
> >> > I am using XP with SP3 and office 2003, and just setup password for my
> >> > user
> >> > account by using "control userpasswords2" command, in order to use
> >> > schedule
> >> > task, the task to open file.xls is tested fine in this morning, but the
> >> > worksheet requests confirmation on macro's security as it opened.
> >> > Before
> >> > setting password, I can skip this security's confirmation by assign a
> >> > selfcert for vertification, and it works fine. Once the username
> >> > password
> >> > has
> >> > changed, the macro's security dialogue pops up again, and the option
> >> > "Always
> >> > trust macros from this publisher" is greyed out.
> >> > When I try to remove username's password under control panel, and
> >> > reopen
> >> > the
> >> > worksheet, then it works fine with selfcert, but schedule task cannot
> >> > be
> >> > performed based on schedule. Is there any conflict between selfcert
> >> > and
> >> > username's password?
> >> > Does anyone have any suggestions/
> >> > Thanks in advance for any suggestions
> >> > Eric
> >>
> >> I suspect that your scheduled task is indeed running, in spite of your
> >> subject line, and that it cannot do its job because of some issue with
> >> macro
> >> security. An Excel newsgroup would be a much better place to post this
> >> question. Note also that the command "control userpasswords2" does not
> >> set
> >> any password. It only allows you to automate the logon process by
> >> supplying
> >> a password automatically. If that password is wrong then the automatic
> >> logon
> >> process will fail. Why you use "control userpasswords2" in connection
> >> with a
> >> scheduled task is unclear - the two have nothing in common. If you want a
> >> task to run automatically then you schedule it to run at boot time or at
> >> a
> >> specified time. Waiting for a logon even is unnecessary and will fail
> >> under
> >> certain circumstances.
> >>
> >> .
> >>
> .
>
 
P

Pegasus [MVP]

Flightless Bird
I repeat what I wrote before:
- The command "control userpasswords" does not do anything.
- The command "control userpasswords2" lets you automate the logon process.
It does NOT set a password and it has NO effect on what happens when the PC
comes out of hibernation.

Here is a method to change your password from a Command Prompt:
net user "%UserName%" xxyyzz
(replace xxyyzz with the new password)

"Eric" <Eric@discussions.microsoft.com> wrote in message
news:716B9E8D-022A-468A-8E19-2BBE80BC5B3D@microsoft.com...
> So what does it do? On hibernation mode for XP, when XP wakes up, it
> requests
> for password, do you have any suggestions whether the password is set by
> "control userpasswords" or "control userpasswords2"?
> Thank you very much for any suggestions
> Eric
>
> "Pegasus [MVP]" wrote:
>
>> The command "control userpasswords" does not do anything at all.
>>
>> "Eric" <Eric@discussions.microsoft.com> wrote in message
>> news:AC23AC6E-2909-42CF-B442-B1576714D876@microsoft.com...
>> > I forget to set the password on "control userpasswords'
>> > Could you please tell me what the major difference is between "control
>> > userpasswords' and "control userpasswords2"?
>> > Thank you very much for any suggestions
>> > Eric
>> >
>> > "Pegasus [MVP]" wrote:
>> >
>> >>
>> >>
>> >> "Eric" <Eric@discussions.microsoft.com> wrote in message
>> >> news:1640925F-0864-40F8-BF1B-7BB5E8E386A6@microsoft.com...
>> >> > I am using XP with SP3 and office 2003, and just setup password for
>> >> > my
>> >> > user
>> >> > account by using "control userpasswords2" command, in order to use
>> >> > schedule
>> >> > task, the task to open file.xls is tested fine in this morning, but
>> >> > the
>> >> > worksheet requests confirmation on macro's security as it opened.
>> >> > Before
>> >> > setting password, I can skip this security's confirmation by assign
>> >> > a
>> >> > selfcert for vertification, and it works fine. Once the username
>> >> > password
>> >> > has
>> >> > changed, the macro's security dialogue pops up again, and the option
>> >> > "Always
>> >> > trust macros from this publisher" is greyed out.
>> >> > When I try to remove username's password under control panel, and
>> >> > reopen
>> >> > the
>> >> > worksheet, then it works fine with selfcert, but schedule task
>> >> > cannot
>> >> > be
>> >> > performed based on schedule. Is there any conflict between selfcert
>> >> > and
>> >> > username's password?
>> >> > Does anyone have any suggestions/
>> >> > Thanks in advance for any suggestions
>> >> > Eric
>> >>
>> >> I suspect that your scheduled task is indeed running, in spite of your
>> >> subject line, and that it cannot do its job because of some issue with
>> >> macro
>> >> security. An Excel newsgroup would be a much better place to post this
>> >> question. Note also that the command "control userpasswords2" does not
>> >> set
>> >> any password. It only allows you to automate the logon process by
>> >> supplying
>> >> a password automatically. If that password is wrong then the automatic
>> >> logon
>> >> process will fail. Why you use "control userpasswords2" in connection
>> >> with a
>> >> scheduled task is unclear - the two have nothing in common. If you
>> >> want a
>> >> task to run automatically then you schedule it to run at boot time or
>> >> at
>> >> a
>> >> specified time. Waiting for a logon even is unnecessary and will fail
>> >> under
>> >> certain circumstances.
>> >>
>> >> .
>> >>
>> .
>>
 
S

Student

Flightless Bird
If you do NOT have a password it requires to make these changes.

========================

Scheduled Tasks - Applying/Running tasks without a password

In Pro:

Start > Administrative Tools > 'Local Security Policy' under:

Security Settings\Local Policies\Security Options

disable 'Accounts: Limit local account use of blank passwords to console
logon only'

In Home:

Locate the following registry key:

HKEY LOCAL MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

Value name: limit blank password use
Type: REG DWORD
Data: 0 (disabled) 1 (enabled)
 
You must log in or register to reply here.
Top