1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Can't schedule tasks

Discussion in 'Windows XP' started by Jeff Jewitt, Jun 17, 2010.

  1. Jeff Jewitt

    Jeff Jewitt Flightless Bird

    I am trying to add simple tasks such as disk defrag and cleanup. Am logged on
    as a Computer admin but the error message I get is

    A new task has been created but may not run because the account information
    could not be set
    The specific error is:
    0x80090016: Keyset does not exist

    Also when I disply hidden tasks as user feed sync I get a similar message

    The attempt to retrieve account information for the specified task failed;
    therefore, the task did not run. Either an error occurred, or no account
    information existed for the task.
    The specific error is:
    0x80090016: Keyset does not exist

    I did a little checking around and the one thing that came up with MS
    applied to Windows 2000, but I checked Protected Storage in Comp Management
    console and it is running.

    Any ideas?

    Jeff
    --
    Jeff
     
  2. Pegasus [MVP]

    Pegasus [MVP] Flightless Bird

    "Jeff Jewitt" <JeffJewitt@discussions.microsoft.com> wrote in message
    news:FCE220C0-811E-44B1-A5D6-D130EBAFA003@microsoft.com...
    > I am trying to add simple tasks such as disk defrag and cleanup. Am logged
    > on
    > as a Computer admin but the error message I get is
    >
    > A new task has been created but may not run because the account
    > information
    > could not be set
    > The specific error is:
    > 0x80090016: Keyset does not exist
    >
    > Also when I disply hidden tasks as user feed sync I get a similar message
    >
    > The attempt to retrieve account information for the specified task failed;
    > therefore, the task did not run. Either an error occurred, or no account
    > information existed for the task.
    > The specific error is:
    > 0x80090016: Keyset does not exist
    >
    > I did a little checking around and the one thing that came up with MS
    > applied to Windows 2000, but I checked Protected Storage in Comp
    > Management
    > console and it is running.
    >
    > Any ideas?
    >
    > Jeff


    I seem to recall that this happens when you use an account with an incorrect
    or blank password.
     
  3. Jim

    Jim Flightless Bird

    On Thu, 17 Jun 2010 11:53:45 -0700, Jeff Jewitt
    <JeffJewitt@discussions.microsoft.com> wrote:

    >
    >I am trying to add simple tasks such as disk defrag and cleanup. Am logged on
    >as a Computer admin but the error message I get is
    >
    >A new task has been created but may not run because the account information
    >could not be set
    > The specific error is:
    > 0x80090016: Keyset does not exist
    >
    >Also when I disply hidden tasks as user feed sync I get a similar message
    >
    >The attempt to retrieve account information for the specified task failed;
    >therefore, the task did not run. Either an error occurred, or no account
    >information existed for the task.
    > The specific error is:
    > 0x80090016: Keyset does not exist
    >
    >I did a little checking around and the one thing that came up with MS
    >applied to Windows 2000, but I checked Protected Storage in Comp Management
    >console and it is running.
    >
    >Any ideas?
    >
    >Jeff


    Did you use a password ?
     
  4. Jose

    Jose Flightless Bird

    On Jun 17, 2:53 pm, Jeff Jewitt <JeffJew...@discussions.microsoft.com>
    wrote:
    > I am trying to add simple tasks such as disk defrag and cleanup. Am logged on
    > as a Computer admin but the error message I get is
    >
    > A new task has been created but may not run because the account information
    > could not be set
    >         The specific error is:
    >         0x80090016: Keyset does not exist
    >
    > Also when I disply hidden tasks as user feed sync I get a similar message
    >
    > The attempt to retrieve account information for the specified task failed;
    > therefore, the task did not run. Either an error occurred, or no account
    > information existed for the task.
    >         The specific error is:
    >         0x80090016: Keyset does not exist
    >
    > I did a little checking around and the one thing that came up with MS
    > applied to Windows 2000, but I checked Protected Storage in Comp Management
    > console and it is running.
    >
    > Any ideas?
    >
    > Jeff
    > --
    > Jeff


    My tasks run okay with or without that service running and I have set
    up many tasks and never seen that error before, but here is my long
    winded copy/paste response about STs and some troubleshooting ideas
    and to consider just trying a really simple task first, then try
    something more complicated.



    Did you create this task yourself or did some program create it for
    you?

    Some applications you may want to schedule at a convenient time
    require user intervention (answering questions). Does your
    application have
    options to run unattended?

    Not so popular advice from me to troubleshoot Scheduled Tasks:

    It is strongly suggested that the task be assigned to a user that has
    a password (not the Administrator), so create a new user with a
    password just for tasks or add a password to your account if needed.
    You can temporarily assign yourself a PW to test and worry about this
    later. Right now you just need to see if your ST mechanism is working
    properly.

    If you set up the task to use the same account you log in with, you
    may see the task launch and start running while you are using the
    computer.

    If you set up the task to use a different account than the one you log
    in with
    the task should still run (and you will not see it), but for testing,
    use
    your login account and then change the account the task uses when you
    are sure
    it works.

    If you try to create new task using an account that does not have a
    password
    you will get this error trying to create the task:

    The new task has been created, but may not run because the account
    information
    could not be set. The specific error is 0x80070005: Access is denied

    The task will still be created, but will not run properly.

    There is a way around this, but get this working first to be sure your
    ST
    mechanism is not afflicted.

    Stop the Task Scheduler service. Click Start, Settings, Control Panel,
    Administrative Tools, Service and locate the Task Scheduler Service
    and
    stop it.

    Delete or rename the probably cluttered ST log file which is here:

    c:/windows\schedlgu.txt

    Restart the Task Scheduler service to create a new log (it is just a
    text
    file) and verify that a new log file has been created and looks
    something
    like this:

    "Task Scheduler Service"
    Started at 1/1/2010 6:26:43 AM
    [ ***** Most recent entry is above this line ***** ]


    Navigate to the c:/windows\tasks folder to see all your tasks. Expand
    the
    explorer window so you can see all the columns of interest dragging
    the
    column headings to see each column.

    The Next Run Time, Last Run Time, Status and Last Results columns
    are of interest. You can also click Advanced and view the ST log file
    from here.

    Choose to Add Scheduled Task. Create a new task to run Command
    Prompt
    once, right now. If you don't have a PW on your account, you will
    get
    an error trying to create it (more on that later). It will still be
    created,
    but will never run. Assign a password to your account at least
    temporarily
    to test your ST mechanism.

    Having temporarily assigned your login account a password, adjust the
    new ST Command Prompt task to use the same account and password you
    used
    to login to Windows and the task should configure with no errors.

    Right click the new Command Prompt task and choose Run and a command
    window should open immediately. If not, something is wrong. If yes,
    your mechanism is sound. Look in the log file to see your results.

    Since the Command Prompt task is set up to run under your account,
    this
    is whey you will see the Command Prompt window open right away. If
    you
    configured the task to use some other account (with a password of
    course),
    the Command Prompt task would run under that users name (not yours)
    and you
    would not see the Command Prompt window open, but the task would be
    running
    and you can see it in Task Manager. This way you know your ST
    mechanism is
    working.

    You know how to run tasks manually, observe the information columns,
    remove the log
    file, so now apply this knowledge to your new task. Be sure the Task
    Scheduler service
    is running again if you stop it to remove the log file while testing.

    Assign Properties to your new or troublesome task that match your
    login (at least for
    testing), observe the columns, and the log. If your task fails to run
    manually, the
    errors in the log file are the clues to what to do next.

    Always try to go back to your simple Command Prompt task that you
    created before to make
    sure the ST mechanism works properly - you know for sure that one
    works. Then apply your
    knowledge to get your new task working.

    You can change the task Properties to use your login account and
    password since you know it
    works properly on the Command Prompt task. If you change your new
    task and choose to run it
    and are logged in the same way, you should see your task run. When
    you are satisfied it
    is working properly, you probably don't want to have it interrupt you
    while you are logged
    in, so change the Properties back to use some other user login and
    password that you created
    just to run STs.

    Some tasks that are created by other applications will use the special
    account
    NT AUTHORITY\SYSTEM. This account has no password and is usually used
    for system
    oriented tasks but you will only be able to see it running when using
    Task Manager.
    If you try to manually run a ST like this, you will not see it open
    any window to run
    but you will see it running in Task Manager and in the log file. If
    you think you
    want to see it actually run, change the Properties to use your account
    and password,
    troubleshoot the task, then change the Properties back and test it
    again.

    These kinds of tasks may run just fine, but you will only be able to
    tell by the log file,
    looking in Task Manager or the status columns in the tasks folder. If
    you temporarily change
    the task to use the same account and password you use to login, you
    will be able to watch
    it run.

    Once you understand how to get a simple task like Command Prompt
    working and you know
    where the log file is and how to change the task Proprieties, you can
    work on your new or afflicted
    task and get it working.

    There are ways to work around some of the restrictions and
    requirements, but it is
    best to just use what you have and use it properly.

    A common problem with STs is no password on the account used to create
    the task or folks expect to
    "see" the task running when it is not assigned to their login and
    don't see anything and think
    the task is not running. That is not the way it works. The log file
    will tell you what is
    going on.

    If you are used to not having a password on your account because you
    don't like to enter one when
    you login or you are the only user on your system, and decide to start
    using some STs, it is sometimes
    easiest to just assign a password to your account or just create a new
    XP user account with a password
    and use it for the STs. You can assign a password to your account and
    still have your system set up
    to never prompt you for a password when you login but you should
    remember your password - or set up
    a new account.
     

Share This Page