Why is schedule task not running?

E

Eric

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]

Eric said:
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

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
 
E

Eric

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
 
P

Pegasus [MVP]

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)
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top