EPG123 Bug Reports

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
garyan2

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

HTPC Specs: Show details

#21

Post by garyan2 » Sun Mar 06, 2016 7:32 am

HTBruceM wrote:Not sure if this is EPG123 issue, or SD issue. Thought I'd report it here to see where to go next.
I have a series recording in WMC to record "The Grinder", new episodes only.
Next week, the Grinder is showing a repeat, it's even in the title. But WMC recording schedule still shows that it will be recorded.
Screenshots follow. Is this a problem in EPG123 data/field mapping, or is it a Gracenote or SD issue?
Couple possibilities. Could you zip up your mxf file and send it to me? Need to see the data. I just added "The Grinder" to my guide for recording new shows only and it did not schedule the repeat for recording. Was this shortly after an update? Part of the reindex task that happens afterwards is to scan/validate the recording schedules.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

Space

Posts: 2838
Joined: Sun Jun 02, 2013 9:44 pm
Location:

HTPC Specs: Show details

#22

Post by Space » Sun Mar 06, 2016 3:47 pm

Are you sure you have no other Series set to record "The Grinder"? I see that the one you have in the pic is for "New" and only episodes at "9:30pm", but if you have another Series that is set to "New + Rerun" and to record at any time, it may be picking this one up to record.

kmp14

Posts: 138
Joined: Sat Sep 08, 2012 7:23 pm
Location:

HTPC Specs: Show details

#23

Post by kmp14 » Sun Mar 06, 2016 4:50 pm

HTBruceM wrote:Not sure if this is EPG123 issue, or SD issue. Thought I'd report it here to see where to go next.
I have a series recording in WMC to record "The Grinder", new episodes only...
FYI - I record that show too and my MC does NOT show that rerun as scheduled to record.

HTBruceM

Posts: 87
Joined: Sat Dec 22, 2012 12:42 am
Location: Oregon

HTPC Specs: Show details

#24

Post by HTBruceM » Sun Mar 06, 2016 5:41 pm

garyan2 wrote:Couple possibilities. Could you zip up your mxf file and send it to me? Need to see the data. I just added "The Grinder" to my guide for recording new shows only and it did not schedule the repeat for recording. Was this shortly after an update? Part of the reindex task that happens afterwards is to scan/validate the recording schedules.
See next post for the zipped MXF attachment.

I honestly cannot remember the sequence of events for when I added this series to the recording schedule. But I do know I cleared the entire recording schedule and added my new series recordings after I had run Lineup Selector (because it did something that messed up my series schedules).

BTW I am still on EPG123 v0.7.0. Today I'll download & run the latest 0.7.4, remove my custom tasks for EPG123 updates and use the new task generation in EPG123. After that I'll delete my existing "The Grinder" series and create a new one to see what happens.
Space wrote:Are you sure you have no other Series set to record "The Grinder"? I see that the one you have in the pic is for "New" and only episodes at "9:30pm", but if you have another Series that is set to "New + Rerun" and to record at any time, it may be picking this one up to record.
Yes I'm sure. Only one series for "The Grinder" is set.
2016-03-06 (1).png
Last edited by HTBruceM on Sun Mar 06, 2016 5:50 pm, edited 1 time in total.

HTBruceM

Posts: 87
Joined: Sat Dec 22, 2012 12:42 am
Location: Oregon

HTPC Specs: Show details

#25

Post by HTBruceM » Sun Mar 06, 2016 5:48 pm

The zipped MXF was too big to attached to a PM, so I'm posting it here as an attachment.

HTBruceM

Posts: 87
Joined: Sat Dec 22, 2012 12:42 am
Location: Oregon

HTPC Specs: Show details

#26

Post by HTBruceM » Sun Mar 06, 2016 6:38 pm

After the latest v074 update and run, that repeat episode of The Grinder was still there. After deleting the series, and creating a new one, the repeat episode is no longer scheduled to record! This time I created it from Recorded TV screen, Add Recording, Search, Title = "The Grinder", then I modified it to use only channel 512.

I wonder if when I added this series before that I might have been in the guide on this specific timeslot which happened to be a repeat? Sometimes I do my series recordings by scanning through the guide and hitting the record button twice on a show that I want (very convenient). But I do seem to recall that WMC would ALWAYS record that specific episode you happened to be on, even if it was a repeat episode, along with the other ones.

In my WMC settings under tasks/tv/recorder/recording defaults/"series only" settings, I have it set to NEW only. Always been this way.

User avatar
garyan2

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

HTPC Specs: Show details

#27

Post by garyan2 » Sun Mar 06, 2016 6:59 pm

HTBruceM wrote:After the latest v074 update and run, that repeat episode of The Grinder was still there. After deleting the series, and creating a new one, the repeat episode is no longer scheduled to record! This time I created it from Recorded TV screen, Add Recording, Search, Title = "The Grinder", then I modified it to use only channel 512.

I wonder if when I added this series before that I might have been in the guide on this specific timeslot which happened to be a repeat? Sometimes I do my series recordings by scanning through the guide and hitting the record button twice on a show that I want (very convenient). But I do seem to recall that WMC would ALWAYS record that specific episode you happened to be on, even if it was a repeat episode, along with the other ones.

In my WMC settings under tasks/tv/recorder/recording defaults/"series only" settings, I have it set to NEW only. Always been this way.
I just ran through that sequence and you are correct...WMC decided to record the repeat as well. You can go ahead and delete your mxf file attachment ... didn't find anything, of course.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

HTBruceM

Posts: 87
Joined: Sat Dec 22, 2012 12:42 am
Location: Oregon

HTPC Specs: Show details

#28

Post by HTBruceM » Sun Mar 06, 2016 7:11 pm

garyan2 wrote:I just ran through that sequence and you are correct...WMC decided to record the repeat as well. You can go ahead and delete your mxf file attachment ... didn't find anything, of course.
I can't edit that post now, I guess it's too old, must be something with TGB forum rules.

User avatar
Scallica

Posts: 2797
Joined: Mon Jun 06, 2011 7:09 pm
Location: USA!

HTPC Specs: Show details

#29

Post by Scallica » Sun Mar 06, 2016 7:48 pm

HTBruceM wrote:
garyan2 wrote:I just ran through that sequence and you are correct...WMC decided to record the repeat as well. You can go ahead and delete your mxf file attachment ... didn't find anything, of course.
I can't edit that post now, I guess it's too old, must be something with TGB forum rules.
Attachment deleted. We don't allow editing of posts after 1 hour.
HTPC Enthusiast / Forum Moderator - TGB.tv Code of Conduct

HTBruceM

Posts: 87
Joined: Sat Dec 22, 2012 12:42 am
Location: Oregon

HTPC Specs: Show details

#30

Post by HTBruceM » Sun Mar 06, 2016 11:52 pm

Thanks Scallica. Garyan2 told me how I could have done this myself in the control panel. I didn't realize we would remove any of our posting attachments from there.

User avatar
STC

Posts: 6808
Joined: Mon Jun 06, 2011 4:58 pm
Location:

HTPC Specs: Show details

#31

Post by STC » Mon Mar 07, 2016 2:38 am

0.7.4 Unhandled exception occurring after clicking logon to SD or when trying to create scheduled task.
Windows 7 Pro 64bit
.net 4.0

Code: Select all

System.MissingMethodException: Method not found: 'System.Type System.Runtime.InteropServices.Marshal.GetTypeFromCLSID(System.Guid)'.
   at epg123.epgTaskScheduler.createTask(Boolean wakeToRun, String startTime)
   at epg123.ConfigForm.btnTask_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(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: 4.0.0.0
    Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
epg123
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/EPG123/epg123.exe
----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
c3pbprku
    Assembly Version: 1.0.0.0
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
Newtonsoft.Json
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.2.19309
    CodeBase: file:///C:/EPG123/Newtonsoft.Json.DLL
----------------------------------------
System.Numerics
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------
System.Runtime.Serialization
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Serialization/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll
----------------------------------------
System.Xml.Linq
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml.Linq/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.Linq.dll
----------------------------------------
System.Data
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.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.
By the Community, for the Community. 100% Commercial Free.

Want decent guide data back? Check out EPG123

User avatar
garyan2

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

HTPC Specs: Show details

#32

Post by garyan2 » Mon Mar 07, 2016 4:51 am

STC wrote:0.7.4 Unhandled exception occurring after clicking logon to SD or when trying to create scheduled task.
Windows 7 Pro 64bit
.net 4.0

Code: Select all

System.MissingMethodException: Method not found: 'System.Type System.Runtime.InteropServices.Marshal.GetTypeFromCLSID(System.Guid)'.
   at epg123.epgTaskScheduler.createTask(Boolean wakeToRun, String startTime)
   at epg123.ConfigForm.btnTask_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(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: 4.0.0.0
    Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
epg123
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/EPG123/epg123.exe
----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
c3pbprku
    Assembly Version: 1.0.0.0
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
Newtonsoft.Json
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.2.19309
    CodeBase: file:///C:/EPG123/Newtonsoft.Json.DLL
----------------------------------------
System.Numerics
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------
System.Runtime.Serialization
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Serialization/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll
----------------------------------------
System.Xml.Linq
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml.Linq/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.Linq.dll
----------------------------------------
System.Data
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.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.
Got it working. Had to change the target framework build to .Net 4.0. Wondering if I should go down to 3.5?, or simply say minimum requirement is .Net 4.0. I just need to verify this works in Win10. Expect v0.7.5 posted on the website later tonight or tomorrow.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

User avatar
garyan2

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

HTPC Specs: Show details

#33

Post by garyan2 » Mon Mar 07, 2016 6:47 am

garyan2 wrote:
STC wrote:0.7.4 Unhandled exception occurring after clicking logon to SD or when trying to create scheduled task.
Windows 7 Pro 64bit
.net 4.0

Code: Select all

System.MissingMethodException: Method not found: 'System.Type System.Runtime.InteropServices.Marshal.GetTypeFromCLSID(System.Guid)'.
   at epg123.epgTaskScheduler.createTask(Boolean wakeToRun, String startTime)
   at epg123.ConfigForm.btnTask_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(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: 4.0.0.0
    Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
epg123
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/EPG123/epg123.exe
----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
c3pbprku
    Assembly Version: 1.0.0.0
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
Newtonsoft.Json
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.2.19309
    CodeBase: file:///C:/EPG123/Newtonsoft.Json.DLL
----------------------------------------
System.Numerics
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------
System.Runtime.Serialization
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Serialization/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll
----------------------------------------
System.Xml.Linq
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml.Linq/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.Linq.dll
----------------------------------------
System.Data
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.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.
Got it working. Had to change the target framework build to .Net 4.0. Wondering if I should go down to 3.5?, or simply say minimum requirement is .Net 4.0. I just need to verify this works in Win10. Expect v0.7.5 posted on the website later tonight or tomorrow.
Up and ready to go. No need to install .Net 4.5. Build is now targeted to 4.0. http://epg123.garyan2.net
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

User avatar
STC

Posts: 6808
Joined: Mon Jun 06, 2011 4:58 pm
Location:

HTPC Specs: Show details

#34

Post by STC » Mon Mar 07, 2016 11:25 am

Thank you for the fix. Recently installed on our production machine which does not do windows updates. I would have upgraded to 4.5 had you deemed it a requirement though ;)
By the Community, for the Community. 100% Commercial Free.

Want decent guide data back? Check out EPG123

glorp

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

HTPC Specs: Show details

#35

Post by glorp » Sun Mar 13, 2016 2:49 pm

This mornings' update seemed to go wrong. I'm using 0.7.5. Normally the updates take a total of about 9 minutes. Today it took less than 2. The resultant mxf file is 18,096 KB. Normally it has been ~100,000 KB. I did not get any new data added to the schedule. The trace log shows nothing unusual. No errors. Pastebin to the trace log below. I can't see any way to attach a text file in the forum as every file extension is rejected.
http://pastebin.com/BHtxdCX6

ED: It looks like it deleted a massive number of cache entries.

User avatar
STC

Posts: 6808
Joined: Mon Jun 06, 2011 4:58 pm
Location:

HTPC Specs: Show details

#36

Post by STC » Sun Mar 13, 2016 3:28 pm

SD had a db issue last night: http://www.thegreenbutton.tv/forums/vie ... 96#p103196
Probably related.
By the Community, for the Community. 100% Commercial Free.

Want decent guide data back? Check out EPG123

User avatar
garyan2

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

HTPC Specs: Show details

#37

Post by garyan2 » Sun Mar 13, 2016 3:32 pm

glorp wrote:This mornings' update seemed to go wrong. I'm using 0.7.5. Normally the updates take a total of about 9 minutes. Today it took less than 2. The resultant mxf file is 18,096 KB. Normally it has been ~100,000 KB. I did not get any new data added to the schedule. The trace log shows nothing unusual. No errors. Pastebin to the trace log below. I can't see any way to attach a text file in the forum as every file extension is rejected.
http://pastebin.com/BHtxdCX6

ED: It looks like it deleted a massive number of cache entries.
The SD-JSON database/server took a hit yesterday. We're only getting a few channel lineups. Was hoping it would be better today so I can run my tests for the next release (which will now detect this condition).

Looks like the only schedules that are being sent are the schedules/programs that have been updated since the problem occurred.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

glorp

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

HTPC Specs: Show details

#38

Post by glorp » Sun Mar 13, 2016 3:39 pm

So recovery from it removing ~32000 programs from cache should not be an issue when the SD data are available? It will just have to re-download/re-cache all the old program data? The guide itself is fine from what I see. It was not affected by uploading a small .mxf. and all the old program data are still there up through Mar 25. I guess I'm just wondering if there can/will be an ill effect from it trashing the cache (rhyme intended) :)

User avatar
garyan2

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

HTPC Specs: Show details

#39

Post by garyan2 » Sun Mar 13, 2016 4:18 pm

glorp wrote:So recovery from it removing ~32000 programs from cache should not be an issue when the SD data are available? It will just have to re-download/re-cache all the old program data? The guide itself is fine from what I see. It was not affected by uploading a small .mxf. and all the old program data are still there up through Mar 25. I guess I'm just wondering if there can/will be an ill effect from it trashing the cache (rhyme intended) :)
Yah, it will just have to download the missing cache again. I sent an email to rkulagow at SD to possibly get an update on this issue.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

User avatar
STC

Posts: 6808
Joined: Mon Jun 06, 2011 4:58 pm
Location:

HTPC Specs: Show details

#40

Post by STC » Sun Mar 13, 2016 4:26 pm

I wonder: DST?!
By the Community, for the Community. 100% Commercial Free.

Want decent guide data back? Check out EPG123

Post Reply