TAsk "could not start" error

An evolving, supported alternative to Rovi
Important Information
★ Download the latest EPG123 here: http://epg123.garyan2.net <> Setup guide here: http://epg123.garyan2.net/downloads/epg123_Guide.pdf

TAsk "could not start" error

Post#1 » Sun Aug 13, 2017 1:09 pm

When the update task tries to run at it's scheduled time, it is failing. This has occurred the last three updates. I will also add that I don't believe the task has ever run. I just installed EPG about 4 weeks ago, and the only reason I knew there was an issue as I was trying to look at the guide and it was empty. I can manually run the update, but that will get a bit tedious.

Here is the log for this morning:

[8/13/2017 8:02:21 AM] ===============================================================================
[8/13/2017 8:02:21 AM] Activating the epg123 configuration GUI.
[8/13/2017 8:02:21 AM] ===============================================================================
[8/13/2017 8:02:23 AM] [WARNG] epg123 is not up to date. Latest version is 1.1.13 and can be downloaded from http://epg123.garyan2.net.
[8/13/2017 8:02:23 AM] [ INFO] Successfully queried the Task Scheduler for status. Could not start. Last Run 8/13/2017 2:30:00 AM; Exit: 0x8007010B
[8/13/2017 8:02:23 AM] [ INFO] Token request successful. serverID: 20141201.web.1
[8/13/2017 8:02:23 AM] [ INFO] Status request successful. account expires: 2018-07-17T10:29:48Z , lineups: 1/4 , lastDataUpdate: 2017-08-13T02:43:32Z
[8/13/2017 8:02:23 AM] [ INFO] system status: Online , message: No known issues.
[8/13/2017 8:02:23 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[8/13/2017 8:02:24 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-IL12549-X.
[8/13/2017 8:02:48 AM] ===============================================================================
[8/13/2017 8:02:48 AM] Activating the epg123 client GUI. version 1.1.10 for Win7
[8/13/2017 8:02:48 AM] ===============================================================================
[8/13/2017 8:02:49 AM] [ INFO] Successfully queried the Task Scheduler for status. Could not start. Last Run 8/13/2017 2:30:00 AM; Exit: 0x8007010B



What do I need to do to correct this?
JimE
 
Posts: 7
Joined: 26 June 2016

Post#2 » Sun Aug 13, 2017 2:35 pm

Need to know a little about your setup. Could you post the attempted update at 2:30AM this morning?

Some rules to the task:
The task will only run if the machine is on AC Power and the network is available.
Import will only happen if there are no recordings in process (default)
If importing a file on a network, the task's user account and password needs to be configured
User avatar
garyan2
 
Posts: 2162
Joined: 27 November 2015
HTPC Specs: Show details
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

Post#3 » Sun Aug 13, 2017 5:12 pm

That's everything from the log for today. So I can only assume, if there is supposed to be more, that it's in a different log. That information was from the trace.log

This is a Win7 machine which is used as a media server and an HTPC using WMC. It runs 24x7.
Based on the recording history, there are only two entries, and they don't appear to be have been during the update time (default time os 2:30am).
The task runs and updates on the same machine.

If there is anything else, just let me know.
JimE
 
Posts: 7
Joined: 26 June 2016

Post#4 » Sun Aug 13, 2017 6:48 pm

Okay, so the task isn't starting epg123. Either the task is pointing to the wrong location, or it thinks you are on battery power or the network is not available. I would delete and recreate your task and see if it works after that.
User avatar
garyan2
 
Posts: 2162
Joined: 27 November 2015
HTPC Specs: Show details
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

Post#5 » Sun Aug 13, 2017 8:05 pm

I will recreate the task and see what happens.

Thanks for taking the time to help.
JimE
 
Posts: 7
Joined: 26 June 2016

Post#6 » Sun Aug 20, 2017 11:18 am

That appears to have worked.

I don't see an error this week, just an exit code of 0x00000000. Which I assume is normal.

Thanks again.
JimE
 
Posts: 7
Joined: 26 June 2016


Return to EPG123



Who is online

Users browsing this forum: No registered users and 2 guests

cron