Scheduled Tasks result - 0x1

Hi Guys,

First of all, im a newbie so apologies in advance if this query sounds stupid.

I have created a BAT file which is supposed to automatically connect to a reporting software and output some data into an excel file. Rather than to always manually run this BAT file, I am then using windows XP scheduler to run this BAT file daily at a given time.
When i run the BAT file manually then it works fine - it connects to the software and outputs the data as i expect it to. However, when i try and run this bat file through windows schduler then unfortunately it doesnt work.

I get an 0x1 error under the last result column in the scheduled tasks window.
I checked the microsoft website to see what this means and i got the following description for this error: "0x1: An incorrect function was called or an unknown function was called".

Unfortunately, i'm still not sure why i am getting this message or what i can do to rectify this problem.

Any help would be greatly appreciated!! Many thanks for your time and help :)

Regards,

Zaf

Did you include your user account password when you setup the scheduled
task?

Gotcha! ;-)
---
Leonard Grey
Errare humanum est

z4f786 wrote:
> Hi Guys,
>
> First of all, im a newbie so apologies in advance if this query sounds
> stupid.
>
> I have created a BAT file which is supposed to automatically connect to
> a reporting software and output some data into an excel file. Rather
> than to always manually run this BAT file, I am then using windows XP
> scheduler to run this BAT file daily at a given time.
> When i run the BAT file manually then it works fine - it connects to
> the software and outputs the data as i expect it to. However, when i try
> and run this bat file through windows schduler then unfortunately it
> doesnt work.
>
> I get an *0x1* error under the *last result* column in the *scheduled
> tasks *window.
> I checked the microsoft website to see what this means and i got the
> following description for this error: "0x1: An incorrect function was
> called or an unknown function was called".
>
> Unfortunately, i'm still not sure why i am getting this message or what
> i can do to rectify this problem.
>
> Any help would be greatly appreciated!! Many thanks for your time and
> help :)
>
> Regards,
>
> Zaf
>
>

On May 20, 2:09 pm, z4f786 <z4f786.3sh...@DoNotSpam.com> wrote:
> Hi Guys,
>
> First of all, im a newbie so apologies in advance if this query sounds
> stupid.
>
> I have created a BAT file which is supposed to automatically connect to
> a reporting software and output some data into an excel file. Rather
> than to always manually run this BAT file, I am then using windows XP
> scheduler to run this BAT file daily at a given time.
> When i run the BAT file manually then it works fine - it connects to
> the software and outputs the data as i expect it to. However, when i try
> and run this bat file through windows schduler then unfortunately it
> doesnt work.
>
> I get an *0x1* error under the *last result* column in the *scheduled
> tasks *window.
> I checked the microsoft website to see what this means and i got the
> following description for this error: "0x1: An incorrect function was
> called or an unknown function was called".
>
> Unfortunately, i'm still not sure why i am getting this message or what
> i can do to rectify this problem.
>
> Any help would be greatly appreciated!! Many thanks for your time and
> help :)
>
> Regards,
>
> Zaf
>
> --
> z4f786
> ------------------------------------------------------------------------
> z4f786's Profile:http://forums.techarena.in/members/99916.htm
> View this thread:http://forums.techarena.in/windows-x...rt/1183461.htm
>
> http://forums.techarena.in

I worked on Scheduled Tasks with another guy, here is the part of my
lengthy
dialogue for him:

User name and password are required. You have to add a password to
the account that is going to run the task - even if you use
Administrator (which usually has no password). If you use the
Administrator account and change the password, you better remember
what it is, or use another account.

To get a good look at things, go to Control Panel, Administrative
Tools, Services. Stop the Task Scheduler.

Navigate to c:\windows. There is a log file called SchedLgU.Txt.
Look near the bottom around the current time for stuff like:

The attempt to log on to the account associated with the task failed,
therefore, the task did not run.
The specific error is:
0x8007052e: Logon failure: unknown user name or bad password.

Chances are the account name for the task has no password. It needs
one.

With the service stopped, you can delete the SchedLgU.Txt file to
start over. Restart the Task Scheduler Service and be sure it is set
to Automatic and Running. Look at the SchedLgu.Txt file now and there
is an appropriate message.

Navigate to c:\windows\tasks. There are all your tasks that you would
see in Control Panel. You can right click them and set up the
properties to have a valid user account and password, or you can do it
through Control Panel. When you Apply any changes, there should be no
errors. If you have an error, the task will get created but will not
run.

You can then right click the task and choose Run and it will run it
right now. Look in the SchedLgU.Txt file to see what happened. If
there is an error, we need to know what the error it is and figure it
out. If you see something like:

The specific error is:
0x80070005: Access is denied.

You have a permissions problem in the usr and/or password. So be
really, really sure the account and password are correct.

For practice, create a new task to run the Command Prompt sometime in
the future
Use your known good account and password. Assuming there
are no errors in the creation, you should be able to right click the
task and Run it and a Command Prompt window should open immediately.
If that works, you now know how to set up a scheduled task
successfully You can delete that task when finished testing.

Troubleshoot errors from what you see in the SchedLgU.Txt file, or
look in there to see what things look like when it runs successfully.
If the log gets too cumbersome, delete it as above.

Please report back your results.

Jose

"z4f786" <z4f786.3shyna@DoNotSpam.com> wrote in message
news:z4f786.3shyna@DoNotSpam.com...
>
> Hi Guys,
>
> First of all, im a newbie so apologies in advance if this query sounds
> stupid.
>
> I have created a BAT file which is supposed to automatically connect to
> a reporting software and output some data into an excel file. Rather
> than to always manually run this BAT file, I am then using windows XP
> scheduler to run this BAT file daily at a given time.
> When i run the BAT file manually then it works fine - it connects to
> the software and outputs the data as i expect it to. However, when i try
> and run this bat file through windows schduler then unfortunately it
> doesnt work.

It's likely that your account does not have a password.

The Windows Task Scheduler requires passwords run on local accounts;
otherwise the tasks will not run. This is a security feature.

Add a password to your account - for this purpose it really doesn't matter
what the password is, as long as it isn't blank - and try again.

HTH
-pk

>
> I get an *0x1* error under the *last result* column in the *scheduled
> tasks *window.
> I checked the microsoft website to see what this means and i got the
> following description for this error: "0x1: An incorrect function was
> called or an unknown function was called".
>
> Unfortunately, i'm still not sure why i am getting this message or what
> i can do to rectify this problem.
>
> Any help would be greatly appreciated!! Many thanks for your time and
> help :)
>
> Regards,
>
> Zaf
>
>
> --
> z4f786
> ------------------------------------------------------------------------
> z4f786's Profile: http://forums.techarena.in/members/99916.htm
> View this thread:
> http://forums.techarena.in/windows-x...rt/1183461.htm
>
> http://forums.techarena.in
>

Hey Guys,

Thank you very very much for all your help guys. I double checked the user name and password and they were correct but it still did not work.

I think i have some idea as to why it didnt work. The actual BAT file was stored on a network drive/server. If i try and schedule it to run the BAT file from the network drive then unfortunately it wasnt working.
However, when i moved the BAT file to C drive and tried scheduling it from there then it works!

As you probably guessed, i'm not a very technical person so im not sure why this is but im sure you guys will have a better idea as to why it schedules the BAT file from the C drive but not if it is stored on the network/server.

Thanks again for all your help :)

Regards,
Zaf

On May 21, 7:36 am, z4f786 <z4f786.3sj...@DoNotSpam.com> wrote:
> Hey Guys,
>
> Thank you very very much for all your help guys. I double checked the
> user name and password and they were correct but it still did not work.
>
> I think i have some idea as to why it didnt work. The actual BAT file
> was stored on a network drive/server. If i try and schedule it to run
> the BAT file from the network drive then unfortunately it wasnt
> working.
> However, when i moved the BAT file to C drive and tried scheduling it
> from there then it works!
>
> As you probably guessed, i'm not a very technical person so im not sure
> why this is but im sure you guys will have a better idea as to why it
> schedules the BAT file from the C drive but not if it is stored on the
> network/server.
>
> Thanks again for all your help :)
>
> Regards,
> Zaf
>
> --
> z4f786
> ------------------------------------------------------------------------
> z4f786's Profile:http://forums.techarena.in/members/99916.htm
> View this thread:http://forums.techarena.in/windows-x...rt/1183461.htm
>
> http://forums.techarena.in

Did you look in the log file for clues? That is one reason there is
a log file - for troubleshooting.

If it works there will be something in the log file. If it fails,
there will be something in the log file.

Did you try to run the task manually while the batch file is on your
other server?

If you try to run it manually what is in the new log file you created
before you tried it?

Jose

I was having a similar issue, and ultimately tried everything here and more.
Added frustration was I had a second job, nearly identical, that always
worked, but the first wouldn't. After reading and trying MS "solutions" RE
permissions and services configuration as above, and more, I went back to
square one and compared my two jobs. First job: scheduler calls a bat file
which calls a txt file that creates an exported file, then another exported
file. Bat then renames the newly exported files. No Dice, it never does the
renames. I changed the bat to call a txt file to do the first export, then
rename it, then call another txt file, then rename that exported file. Works!
I don't understand what the difference from an MS pespectiveis though, sad
as that is. Or maybe not.

"Jose" wrote:

> On May 21, 7:36 am, z4f786 <z4f786.3sj...@DoNotSpam.com> wrote:
> > Hey Guys,
> >
> > Thank you very very much for all your help guys. I double checked the
> > user name and password and they were correct but it still did not work.
> >
> > I think i have some idea as to why it didnt work. The actual BAT file
> > was stored on a network drive/server. If i try and schedule it to run
> > the BAT file from the network drive then unfortunately it wasnt
> > working.
> > However, when i moved the BAT file to C drive and tried scheduling it
> > from there then it works!
> >
> > As you probably guessed, i'm not a very technical person so im not sure
> > why this is but im sure you guys will have a better idea as to why it
> > schedules the BAT file from the C drive but not if it is stored on the
> > network/server.
> >
> > Thanks again for all your help :)
> >
> > Regards,
> > Zaf
> >
> > --
> > z4f786
> > ------------------------------------------------------------------------
> > z4f786's Profile:http://forums.techarena.in/members/99916.htm
> > View this thread:http://forums.techarena.in/windows-x...rt/1183461.htm
> >
> > http://forums.techarena.in
>
> Did you look in the log file for clues? That is one reason there is
> a log file - for troubleshooting.
>
> If it works there will be something in the log file. If it fails,
> there will be something in the log file.
>
> Did you try to run the task manually while the batch file is on your
> other server?
>
> If you try to run it manually what is in the new log file you created
> before you tried it?
>
> Jose
>