Hi Jose,
I too felt its a simple issue but things are not like that.
I searched the net and found the following link.>
http://support.microsoft..com/kb/904423.
which tells about he problem i am facing.I have installed the hotfix, but
the problem persists, i have also double the security setting for thisnew
scheduled task and have given maximum previleges to it and also tried with
administator privilege but none of these worked.
Could you please forward the links which you have found may be it would be
helpful.Sorry for the earlier reply.
BR,
Ranjit
Have you ever set up a scheduled task successfully before on this
computer? If yes, look at them and maybe see something you are
forgetting to do with this one.
I went to Google and pasted your error message, hit search and got
lots of hits, including the MS one.
I would do the search first and read the top most hits and consider
trying some of the suggestions you have not tried yet.
Here is a link where the people still had problem after the MS ideas,
but fixed it another way:
http://blogs.chron.com/helpline/archives/2005/12/denied_access_t.html
I think their solutions had to do with the Run Only if Logged On check
box, which you can still check in another place if you have the
Advanced options set - even after the error, the job still gets
created and then you can go back and change the properties of the job
and check the box. Maybe the Run Only if Logged on will not work for
you - I don't know what you are trying to do.
At the last step of creating your task do you see a message that says
the new task has been created but may not run...? It is important to
include as much as you can about your error message so we don't have
to ask so many questions back and forth (and I don't have to do so
much reading).
Try to schedule a simple task - like a command prompt on hour out in
time. How far do you get before you see the error? What is the last
thing you click before you see the error?
Once the job is scheduled, you can right click and run it to see if it
works. Get the command prompt job working, since that is easy then
apply your knowledge to your real job.
Since I can't reproduce your problem here, it is harder to
troubleshoot without guessing.
One fellow just gave up trying to fix it and someone pointed him to
http://www.splinterware.com/products/wincron.htm which has some free
scheduling thing that I know nothing about, but it worked for him.
When you are reading the Google results, pay attention to the dates of
the posts and try to stick with stuff that is not too old. Also, be
sure the resulting link applies to XP. There are some there for
Vista, Windows Server, etc. There will be other links at the bottom
of the Google search page to pages that are similar to your search
that may be helpful.