xmltv batch file problems, please, help me?

[grot]

Here's the thing. I have this nice batch file that runs the following commands:

xmltv tv_grab_na --days 8 --listings-overwrite true --listings foo.xml

xmltv tv_sort --output epgdata.xml foo.xml

copy epgdata.xml "C:\Program Files\Frey Technologies\SageTV\" /y

This works ABSOULTEY perfectly if I execute the batch file by hand. However, when I try to set windows task schedule to execute this, either on a schedule or one off, it finishes instantly and this is in the log:

"get.job" (get.bat)
Started 6/1/2003 9:12:46 AM
"get.job" (get.bat)
Finished 6/1/2003 9:12:46 AM
Result: The task completed with an exit code of (80).

I am not an idiot. I have checked every piece of support I can find online, and in typical windows fashion, there isn't even anywhere I can find that exit code. I am running this in the right directory, I am writing it from a password protected administrator account.

I get no visual confirmation that anything even happens when I run it, but I don't get an error either. This is the same problem I have, apparently, when I run ANYTHING through task scheduler.

Any suggestions?

[fasttech]

I think I read somewhere that you need to run those types of tasks under another account besides the Administrator account. Give that account administrator priviledges though.
Kenny

[olyar15]

You can run the task under the Administrator account. However, you must have a password for that account, and use the same password in the scheduled task. That was the problem that I originally had.

Also, if you go into the Scheduled task app, make sure the view is set to details, there is a column called status that will give you clues as to why it wasn't able to run. As well as a column stating the last time task was run.

[justme]

You could also try using the short(8.3) names for your directories in your batch file. I made a batch that worked perfectly when run from the command prompt(cmd.exe). Yet when I executed it from windows scheduler I got the same results your are describing. Changing all the directories to their sort names in my batch fixed it for me. You can use "dir /a:d /x" to see the sort names of just the directories. Your command should look something like this:

copy epgdata.xml "C:\PROGRA~1\FREYTE~1\SageTV\" /y

I typed that from memory so don't quote me. I hope this helps. Best of luck.

PS:Once you get your batch working, here is a neat trick I used to keep it unobtrusive. Create a shorcut to your batch file. Modify the shortcut's properties so it runs in a minimized window(you could also change the icon if you wished). Place the shortcut in the same directory you working batch file is in. Now change Window's scheduler to run the shorcut instead of the batch file. This way if you are on the computer when the scheduled task is run you only have to see a button on the task bar. If you wish to see whats going on just restore the window.

[grot]

Thanks for all the suggestions. Alas, none seem to work. The problem is that task scheduler says the batch file IS running, and exits with the mysterious success code of "80".

the .bat works fine, so I know it's not an 8.3 problem.

I can't even have it run word or the calculator on a schedule, I always get this instant end with an "80" success code.

I have found a shareware scheduler called winschedule which works wonderfully. But of course, this is yet another program I will end up paying for a $30 license for (grin) - to go along with alcohol, Divx, and all the other apps that I keep paying for because the OS doesn't work right.

Sigh.

I really wish I could get this to work, even if its just to save thirty bucks!

[Hocky]

Grot;
You are not clear as to what OS you are using. Bat files can differ greatly between WIN9x and NT. By NT I am saying any platform built on the New Technology.

I did a quick search and found this and it may help you out.

Follow this link.

Hocky

[grot]

Thanks Hocky, windows XP pro.

Thanks for the find in knowledge base too. This is indeed the problem I am having. I love Microsoft, not only is this a known bug, but the answer is "Call microsoft, and we may charge you, or wait until the next service pack, whenever we get arround to releasing it, or disable your HID (which, I believe, means kiss your joystick goodbye).

LOL.

Winscheduler seems to be fixing the gap for me at the moment.

[corykim]

I had the exact same problem, until I renamed the program in Windows Scheduler to use the 8.3 path. I'm talking about the entry that describes the .bat file itself, not the lines within the .bat file. See if that makes a difference.

[grot]

No go. My file was named go.bat, pretty darn compliant. Using winscheduler now without problem.

[insomniac]

Grot,

Did you make sure that you ran it as yourself and entered a password? Task scheduler doesnt do the intelligent thing when you schedule something with correct privelages....You have to re-enter your login/pass...

I hate to mention something so medial, but youd be surprised how many administrators have ran into this over time.

Also, if that doesnt work, try to write the batch file in a cmd /c session.

Ive also found that in batch, for some ungodly reason, things seem to work better if I change dir to the directory and run from there...I know there is no logical or ducumented reason for it, but its just my experience.. e.g. cd c:\progra~1\frey...

I.

Originally posted by grot
Here's the thing. I have this nice batch file that runs the following commands:

xmltv tv_grab_na --days 8 --listings-overwrite true --listings foo.xml

xmltv tv_sort --output epgdata.xml foo.xml

copy epgdata.xml "C:\Program Files\Frey Technologies\SageTV\" /y

This works ABSOULTEY perfectly if I execute the batch file by hand. However, when I try to set windows task schedule to execute this, either on a schedule or one off, it finishes instantly and this is in the log:

"get.job" (get.bat)
Started 6/1/2003 9:12:46 AM
"get.job" (get.bat)
Finished 6/1/2003 9:12:46 AM
Result: The task completed with an exit code of (80).

I am not an idiot. I have checked every piece of support I can find online, and in typical windows fashion, there isn't even anywhere I can find that exit code. I am running this in the right directory, I am writing it from a password protected administrator account.

I get no visual confirmation that anything even happens when I run it, but I don't get an error either. This is the same problem I have, apparently, when I run ANYTHING through task scheduler.

Any suggestions?

[laurenglenn]

Originally posted by insomniac
Grot,

Did you make sure that you ran it as yourself and entered a password? Task scheduler doesnt do the intelligent thing when you schedule something with correct privelages....You have to re-enter your login/pass...

I hate to mention something so medial, but youd be surprised how many administrators have ran into this over time.

Also, if that doesnt work, try to write the batch file in a cmd /c session.

Ive also found that in batch, for some ungodly reason, things seem to work better if I change dir to the directory and run from there...I know there is no logical or ducumented reason for it, but its just my experience.. e.g. cd c:\progra~1\frey...

I.

I had the same 0x80 problem. The verbose text in the window said that the password was not properly specified in the Task, so I hit Properties, went to the Run As button, hit Password and typed my password.

When choosing the BAT file, I used the Browse button to create a new task and then located the BAT file. This created a path in the Task listing and it's been working ever since.

Lauren