v1.1.0 Release

An evolving, supported alternative to Rovi
Forum rules
★ Download the latest EPG123 here: https://garyan2.github.io/ <> Setup guide here: https://garyan2.github.io/install.html
User avatar
Peepers

Posts: 6
Joined: Sat Jul 25, 2015 10:43 pm
Location:

HTPC Specs: Show details

#61

Post by Peepers » Sun Feb 12, 2017 7:00 am

That did not resolve the issue I still get [ALERT] Failed to parse the schedule Md5 return for stationId 32984 (KTVPLP) on 2017-02-12 and after. message: Accessed JArray values with invalid key value: "2017-02-12". Int32 array index expected.

User avatar
garyan2

Posts: 7438
Joined: Fri Nov 27, 2015 7:23 pm
Location:

HTPC Specs: Show details

#62

Post by garyan2 » Sun Feb 12, 2017 7:04 am

Peepers wrote:That did not resolve the issue I still get [ALERT] Failed to parse the schedule Md5 return for stationId 32984 (KTVPLP) on 2017-02-12 and after. message: Accessed JArray values with invalid key value: "2017-02-12". Int32 array index expected.
I believe SD was doing some background maintenance that wasn't supposed to impact us. Try again cause it looks like it just came back up for me with 0 errors while about 30 minutes ago every channel was empty.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

User avatar
Peepers

Posts: 6
Joined: Sat Jul 25, 2015 10:43 pm
Location:

HTPC Specs: Show details

#63

Post by Peepers » Sun Feb 12, 2017 7:10 am

fantastic! looks good now

sjr56stn

Posts: 77
Joined: Tue Mar 03, 2015 4:49 pm
Location:

HTPC Specs: Show details

#64

Post by sjr56stn » Sun Feb 12, 2017 1:38 pm

garyan2 wrote:Just realized I missed the booting back into normal mode :oops: (though the GUI would tell you to do so).
garyan2 wrote:
sjr56stn wrote:Not a successful upgrade for me (Win 7 x 64). I followed the upgrade instructions, but when I run epg123Client.exe I get "Unhandled exception has occurred .... etc". Details says an array is out of range. If I select continue, then the button I presume I must select to manually load the mxf file is greyed-out.
Right now, I can only assume there is an error in your database when I try to populate the lineups or merged channels in the GUI. In theory, you could follow the below to correct the problem.
  1. Boot into safe mode and open epg123Client.exe.
  2. Click [Rebuild WMC Database] to delete your database. BOOT BACK INTO NORMAL MODE.
  3. Open epg123Client.exe and click [Rebuild WMC Database] again to rebuild it.
  4. Select the epg123utility.mxf file for import when prompted.
  5. Listings will be empty, so will need to run epg123.exe v1.1.0 to build and import new listings.
There is, of course, the risk of restoring whatever epg123 is choking on. I'll scrub through my code to see where an out-of-range can occur.
Gary,
OK I tried that but when I rebooted into normal mode a ran epg123client.exe I just got the same index out of range error. I will send you more details of the error in a separate post. In the mean time I think I will go back to a restore point I have from a few days ago.
Steve

sjr56stn

Posts: 77
Joined: Tue Mar 03, 2015 4:49 pm
Location:

HTPC Specs: Show details

#65

Post by sjr56stn » Sun Feb 12, 2017 1:43 pm

Details in the exception box as follows:
QUOTE:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at epg123Client.clientForm.updateTaskPanel()
at epg123Client.clientForm.clientForm_Load(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
epg123Client
Assembly Version: 1.1.0.0
Win32 Version: 1.1.0.0
CodeBase: file:///C:/epg123/epg123Client.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5491 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8686 (QFE.050727-8600)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5495 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
mcepg
Assembly Version: 6.1.0.0
Win32 Version: 6.1.7601.17514
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/mcepg/6.1.0.0__31bf3856ad364e35/mcepg.dll
----------------------------------------
mcstore
Assembly Version: 6.1.0.0
Win32 Version: 6.1.7601.17514 (win7sp1_rtm.101119-1850)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/mcstore/6.1.0.0__31bf3856ad364e35/mcstore.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5494 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
ytsrotte
Assembly Version: 1.1.0.0
Win32 Version: 2.0.50727.8686 (QFE.050727-8600)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

User avatar
garyan2

Posts: 7438
Joined: Fri Nov 27, 2015 7:23 pm
Location:

HTPC Specs: Show details

#66

Post by garyan2 » Sun Feb 12, 2017 3:17 pm

sjr56stn wrote:Details in the exception box as follows:

Code: Select all

See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at epg123Client.clientForm.updateTaskPanel()
   at epg123Client.clientForm.clientForm_Load(Object sender, EventArgs e)
   at System.Windows.Forms.Form.OnLoad(EventArgs e)
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.Control.CreateControl()
   at System.Windows.Forms.Control.WmShowWindow(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
epg123Client
    Assembly Version: 1.1.0.0
    Win32 Version: 1.1.0.0
    CodeBase: file:///C:/epg123/epg123Client.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5491 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.8686 (QFE.050727-8600)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5495 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
mcepg
    Assembly Version: 6.1.0.0
    Win32 Version: 6.1.7601.17514
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/mcepg/6.1.0.0__31bf3856ad364e35/mcepg.dll
----------------------------------------
mcstore
    Assembly Version: 6.1.0.0
    Win32 Version: 6.1.7601.17514 (win7sp1_rtm.101119-1850)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/mcstore/6.1.0.0__31bf3856ad364e35/mcstore.dll
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5494 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
ytsrotte
    Assembly Version: 1.1.0.0
    Win32 Version: 2.0.50727.8686 (QFE.050727-8600)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
Do you have a epg123_update task? If you do, delete it. I did find a possible exception from reading an existing task, but still can't imagine how it could have gotten to that point.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

sjr56stn

Posts: 77
Joined: Tue Mar 03, 2015 4:49 pm
Location:

HTPC Specs: Show details

#67

Post by sjr56stn » Sun Feb 12, 2017 3:41 pm

Gary,
Sorry, I'm afraid I have restored a C Image that I happened to have from just a couple of weeks ago. I needed a working system.
Steve

(There is no EPG123_update.exec task in the EPG123 directory from that backup.)

User avatar
garyan2

Posts: 7438
Joined: Fri Nov 27, 2015 7:23 pm
Location:

HTPC Specs: Show details

#68

Post by garyan2 » Sun Feb 12, 2017 3:55 pm

sjr56stn wrote:Gary,
Sorry, I'm afraid I have restored a C Image that I happened to have from just a couple of weeks ago. I needed a working system.
Steve

(There is no EPG123_update.exec task in the EPG123 directory from that backup.)
I understand. Luckily, you can still help me pinpoint the hole in my code. I believe you have a task in Task Scheduler called epg123_update. The possible problem I found in my code that could cause this problem is about reading that task to update the panel. Could you let me know what the Actions look like for the task?
Capture.PNG
Sorry for the frustration, and thank you for any help you can give.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

sjr56stn

Posts: 77
Joined: Tue Mar 03, 2015 4:49 pm
Location:

HTPC Specs: Show details

#69

Post by sjr56stn » Sun Feb 12, 2017 5:33 pm

Gary,

I have checked the actions box in the task scheduler and saved an image of it, but just cannot figure out how to attach the image to this post!!

Suffice to say that I have calls to powercfg both ahead of, and after C:\epg123\epg123.exe -update. This to ensure that the machine doesn't sleep during the update. (I think your more recent versions of epg123.exe deal with the sleep issue, so these are probably no longer needed.)

Steve

User avatar
garyan2

Posts: 7438
Joined: Fri Nov 27, 2015 7:23 pm
Location:

HTPC Specs: Show details

#70

Post by garyan2 » Sun Feb 12, 2017 5:41 pm

sjr56stn wrote:Gary,

I have checked the actions box in the task scheduler and saved an image of it, but just cannot figure out how to attach the image to this post!!

Suffice to say that I have calls to powercfg both ahead of, and after C:\epg123\epg123.exe -update. This to ensure that the machine doesn't sleep during the update. (I think your more recent versions of epg123.exe deal with the sleep issue, so these are probably no longer needed.)

Steve
You just confirmed what I was seeing. The problem with my code was that custom tasks (depending on how they were customized) could confuse it and make it choke. The sleep prevention code has been in for awhile and powercfg is no longer needed. If you delete the task, epg123client should open without a problem.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

sjr56stn

Posts: 77
Joined: Tue Mar 03, 2015 4:49 pm
Location:

HTPC Specs: Show details

#71

Post by sjr56stn » Sun Feb 12, 2017 5:55 pm

garyan2 wrote:
sjr56stn wrote:Gary,

I have checked the actions box in the task scheduler and saved an image of it, but just cannot figure out how to attach the image to this post!!

Suffice to say that I have calls to powercfg both ahead of, and after C:\epg123\epg123.exe -update. This to ensure that the machine doesn't sleep during the update. (I think your more recent versions of epg123.exe deal with the sleep issue, so these are probably no longer needed.)

Steve
You just confirmed what I was seeing. The problem with my code was that custom tasks (depending on how they were customized) could confuse it and make it choke. The sleep prevention code has been in for awhile and powercfg is no longer needed. If you delete the task, epg123client should open without a problem.
OK I will try the update again after deleting the scheduled task. But probably not for a few days!
Steve

glorp

Posts: 369
Joined: Sun Sep 23, 2012 2:54 pm
Location:

HTPC Specs: Show details

#72

Post by glorp » Mon Feb 13, 2017 6:54 pm

Would you mind clarifying the instructions? You want epg123utility.exe to be run once from where the .cfg and the last built .mxf are located (server)? Then go to each client, run epg123Client.exe locally and import the newly created epg123utility.mxf from the server? Once that's done, allow the next cycle to load the regular .mxf the server creates with the standard "epg123Client.exe -i <path> -match" task call?

Also, are the W7/W8 differences all still in epg123Client.exe or is epg123utility affected by version?

User avatar
garyan2

Posts: 7438
Joined: Fri Nov 27, 2015 7:23 pm
Location:

HTPC Specs: Show details

#73

Post by garyan2 » Mon Feb 13, 2017 7:22 pm

glorp wrote:Would you mind clarifying the instructions? You want epg123utility.exe to be run once from where the .cfg and the last built .mxf are located (server)? Then go to each client, run epg123Client.exe locally and import the newly created epg123utility.mxf from the server? Once that's done, allow the next cycle to load the regular .mxf the server creates with the standard "epg123Client.exe -i <path> -match" task call?

Also, are the W7/W8 differences all still in epg123Client.exe or is epg123utility affected by version?
You've got it right. The utility mxf must be imported on an machine that receives the epg123.mxf from the same location. I would also add to delete and recreate the scheduled task for Client Mode on the clients. The server side task should also be deleted and created by v1.1.0 for server mode only or full mode if server also imports epg123.mxf.

Differences for W7/W8 are still in epg123Client... epg123.exe and epg123utility.exe are fine in either W7/W8/W10.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

bartswanson

Posts: 9
Joined: Tue Feb 14, 2017 12:47 am
Location:

HTPC Specs: Show details

#74

Post by bartswanson » Tue Feb 14, 2017 1:05 am

Hi Gary! Thanks for all the work you've done on this project.

I tried upgrading from v1.0.2 to v1.1.0 today and ended up with an empty Schedules Direct listing. I must admit that I'm rather lost right now.

I am running W7. Here's the snippet from my log after running epg123Client, epg123Utility, and epg123.

Code: Select all

[2/13/2017 6:28:42 PM] [ INFO] epg123 is up to date. version: 1.1.0
[2/13/2017 6:28:42 PM] [ INFO] Successfully queried the Task Scheduler for status. status: No task is scheduled to run..
[2/13/2017 6:28:43 PM] [ INFO] Token request successful. serverID: 20141201.web.1
[2/13/2017 6:28:43 PM] [ INFO] Status request successful. account expires: 2017-06-24T01:17:35Z , lineups: 1/4 , lastDataUpdate: 2017-02-13T21:48:18Z
[2/13/2017 6:28:43 PM] [ INFO] system status: Online , message: No known issues.
[2/13/2017 6:28:43 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[2/13/2017 6:28:44 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-46383.
[2/13/2017 6:29:06 PM] ===============================================================================
[2/13/2017 6:29:06 PM]  Beginning epg123 update execution.
[2/13/2017 6:29:06 PM] ===============================================================================
[2/13/2017 6:29:07 PM] [ INFO] Successfully retrieved TMDb configurations.
[2/13/2017 6:29:07 PM] [ INFO] epg123 version 1.1.0 , DaysToDownload: 30 , PrefixEpisodeTitle: False , AppendEpisodeDesc: False , TMDbCoverArt: False , LogoOverride: False , AutoAddNew: False
[2/13/2017 6:29:07 PM] [ INFO] Token request successful. serverID: 20141201.web.1
[2/13/2017 6:29:07 PM] [ INFO] epg123 is up to date. version: 1.1.0
[2/13/2017 6:29:07 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[2/13/2017 6:29:07 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-46383.
[2/13/2017 6:29:07 PM] [ INFO] Lineup USA-OTA-46383 has been excluded from download and processing.
[2/13/2017 6:29:07 PM] Entering getAllScheduleEntryMd5s() for 30 days on 0 stations.
[2/13/2017 6:29:07 PM] Exiting getAllScheduleEntryMd5s(). SUCCESS.
[2/13/2017 6:29:07 PM] Entering buildAllProgramEntries() for 0 programs.
[2/13/2017 6:29:07 PM] Exiting buildAllProgramEntries(). SUCCESS.
[2/13/2017 6:29:07 PM] Entering buildAllGenericSeriesInfoDescriptions() for 0 series.
[2/13/2017 6:29:07 PM] Exiting buildAllGenericSeriesInfoDescriptions(). SUCCESS.
[2/13/2017 6:29:07 PM] Entering getAllMoviePosters() for 0 movies.
[2/13/2017 6:29:07 PM] Exiting getAllMoviePosters(). SUCCESS.
[2/13/2017 6:29:07 PM] Entering getAllSeriesImages() for 0 series.
[2/13/2017 6:29:07 PM] Exiting getAllSeriesImages(). SUCCESS.
[2/13/2017 6:29:07 PM] Entering writeMxf().
[2/13/2017 6:29:07 PM] Exiting writeMxf(). SUCCESS.
[2/13/2017 6:29:07 PM] Entering writeImageArchive().
[2/13/2017 6:29:07 PM] Exiting writeImageArchive(). SUCCESS.
[2/13/2017 6:29:07 PM] [ INFO] 0 files deleted from the cache directory during cleanup.
[2/13/2017 6:29:07 PM] [STATS] Generated .mxf file contains 0 services, 0 series, 0 programs, and 0 people with 0 image links.
[2/13/2017 6:29:08 PM] ====================== Beginning epg123 client execution. =====================
[2/13/2017 6:29:08 PM] [ INFO] Import=True , Match=True , NoLogo=False
[2/13/2017 6:29:08 PM] [ INFO] import filename = epg123.mxf
[2/13/2017 6:29:08 PM] [ INFO] Successfully imported .mxf file into Media Center. Exit code: 0
[2/13/2017 6:29:08 PM] [ INFO] Completed the automatch of lineup stations to tuner channels.
[2/13/2017 6:29:08 PM] [ INFO] INFO: scheduled task "Microsoft\Windows\Media Center\ReindexSearchRoot" is currently running.
[2/13/2017 6:29:08 PM] [ INFO] SUCCESS: Attempted to run the scheduled task "Microsoft\Windows\Media Center\ReindexSearchRoot".
[2/13/2017 6:29:08 PM] [ INFO] Successfully started the ReindexSearchRoot task. Exit code: 0
[2/13/2017 6:29:08 PM] [STATS] epg123Client mxf load and database reindex execution time was 00:00:00.6400367.
[2/13/2017 6:29:08 PM] ====================== Completed epg123 client execution. =====================
[2/13/2017 6:29:10 PM] [STATS] epg123 update execution time was 00:00:04.0032290.
[2/13/2017 6:34:41 PM] ===============================================================================
[2/13/2017 6:34:41 PM]  Beginning epg123 utility transition tool execution.
[2/13/2017 6:34:41 PM] ===============================================================================
[2/13/2017 6:34:45 PM] [ INFO] Token request successful. serverID: 20141201.web.1
[2/13/2017 6:34:45 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[2/13/2017 6:34:45 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-46383.
[2/13/2017 6:34:46 PM] [ INFO] Lineup USA-OTA-46383 has been excluded from download and processing.
[2/13/2017 6:34:46 PM] Entering writeMxf().
[2/13/2017 6:34:46 PM] Exiting writeMxf(). SUCCESS.
[2/13/2017 6:34:46 PM] [STATS] Generated .mxf file contains 0 services, 0 series, 0 programs, and 0 people with 0 image links.
[2/13/2017 6:34:46 PM] [STATS] epg123 utility execution time was 00:00:04.1400058.
[Moderator note: please use code tags for long logs]

User avatar
garyan2

Posts: 7438
Joined: Fri Nov 27, 2015 7:23 pm
Location:

HTPC Specs: Show details

#75

Post by garyan2 » Tue Feb 14, 2017 2:00 am

bartswanson wrote:Hi Gary! Thanks for all the work you've done on this project.

I tried upgrading from v1.0.2 to v1.1.0 today and ended up with an empty Schedules Direct listing. I must admit that I'm rather lost right now.

I am running W7. Here's the snippet from my log after running epg123Client, epg123Utility, and epg123.

Code: Select all

[2/13/2017 6:34:45 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[2/13/2017 6:34:45 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-46383.
[2/13/2017 6:34:46 PM] [ INFO] Lineup USA-OTA-46383 has been excluded from download and processing.
Your lineup is excluded. In the main epg123.exe GUI, you will have to include it and see the green button, instead of the red button (refer to page 5 of the guide).
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

sjr56stn

Posts: 77
Joined: Tue Mar 03, 2015 4:49 pm
Location:

HTPC Specs: Show details

#76

Post by sjr56stn » Tue Feb 14, 2017 10:05 am

sjr56stn wrote:
garyan2 wrote:
sjr56stn wrote:Gary,

I have checked the actions box in the task scheduler and saved an image of it, but just cannot figure out how to attach the image to this post!!

Suffice to say that I have calls to powercfg both ahead of, and after C:\epg123\epg123.exe -update. This to ensure that the machine doesn't sleep during the update. (I think your more recent versions of epg123.exe deal with the sleep issue, so these are probably no longer needed.)

Steve
You just confirmed what I was seeing. The problem with my code was that custom tasks (depending on how they were customized) could confuse it and make it choke. The sleep prevention code has been in for awhile and powercfg is no longer needed. If you delete the task, epg123client should open without a problem.
OK I will try the update again after deleting the scheduled task. But probably not for a few days!
Steve
Gary,
Success! Deleting my non-standard scheduled task did the trick.
(Though I am ashamed to admit that lack of trust caused me to do another C image backup beforehand!)
Steve

bartswanson

Posts: 9
Joined: Tue Feb 14, 2017 12:47 am
Location:

HTPC Specs: Show details

#77

Post by bartswanson » Wed Feb 15, 2017 1:28 am

garyan2 wrote:
bartswanson wrote:Hi Gary! Thanks for all the work you've done on this project.

I tried upgrading from v1.0.2 to v1.1.0 today and ended up with an empty Schedules Direct listing. I must admit that I'm rather lost right now.

I am running W7. Here's the snippet from my log after running epg123Client, epg123Utility, and epg123.

Code: Select all

[2/13/2017 6:34:45 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[2/13/2017 6:34:45 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-46383.
[2/13/2017 6:34:46 PM] [ INFO] Lineup USA-OTA-46383 has been excluded from download and processing.
Your lineup is excluded. In the main epg123.exe GUI, you will have to include it and see the green button, instead of the red button (refer to page 5 of the guide).
OK, that got me quite a way farther. Now I've uploaded the schedule from epg123, but in WMC I have no guide. In Settings/TV/Guide, I only have two entries -- Edit Channels and Add Missing Channels. I'm still researching this, but at least v1.1.0 seems to be working.

User avatar
garyan2

Posts: 7438
Joined: Fri Nov 27, 2015 7:23 pm
Location:

HTPC Specs: Show details

#78

Post by garyan2 » Wed Feb 15, 2017 2:11 am

Open epg123Client.exe.... should get you even further.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

Sancho

Posts: 160
Joined: Wed Jun 13, 2012 9:52 pm
Location:

HTPC Specs: Show details

#79

Post by Sancho » Thu Feb 16, 2017 9:15 pm

Question re: manually importing an MXF file that did not import due to a recording in progress: after the import completes, I see this in the cmd prompt window:

Code: Select all

Importing guide data into Windows Media Center ...
Loading... 100%

Kicking off ReindexSearchRoot task ...
SUCCESS: Attempted to run the scheduled task "Microsoft\Windows\Media Center\ReindexSearchRoot".
At what point can the cmd prompt and/or Client GUI windows be closed? The SUCCESS message makes me think immediately, but I'll leave them open until I hear back.

Thanks!

User avatar
garyan2

Posts: 7438
Joined: Fri Nov 27, 2015 7:23 pm
Location:

HTPC Specs: Show details

#80

Post by garyan2 » Thu Feb 16, 2017 10:26 pm

Sancho wrote:Question re: manually importing an MXF file that did not import due to a recording in progress: after the import completes, I see this in the cmd prompt window:

Code: Select all

Importing guide data into Windows Media Center ...
Loading... 100%

Kicking off ReindexSearchRoot task ...
SUCCESS: Attempted to run the scheduled task "Microsoft\Windows\Media Center\ReindexSearchRoot".
At what point can the cmd prompt and/or Client GUI windows be closed? The SUCCESS message makes me think immediately, but I'll leave them open until I hear back.

Thanks!
Yah, at that point it is safe to close. I'll have the console update with something to indicate all import actions are completed on the next release.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

Post Reply