No guide updates since SD servers were down

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
Post Reply
technodevotee

Posts: 963
Joined: Thu Sep 10, 2015 4:10 pm
Location: West Midlands

HTPC Specs: Show details

No guide updates since SD servers were down

#1

Post by technodevotee » Tue Apr 21, 2020 7:33 am

EPG123 was working fine until SD did their maintenance (thanks Gary) but fails every day now and the log contains

[ERROR] Unhandled exception caught from epg123.exe. message: Object reference not set to an instance of an object.

[ERROR] The MXF file imported is 119.81 hours old.

sorry if there is a resolution to this somewhere but I can't see it.

User avatar
garyan2

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

HTPC Specs: Show details

#2

Post by garyan2 » Tue Apr 21, 2020 7:44 am

I think you had a problem before the servers went down. Your MXF file is 5 days old... servers went down 2 days ago. Without seeing where your exception is occurring, I would recommend clearing the cache and trying an update again.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

technodevotee

Posts: 963
Joined: Thu Sep 10, 2015 4:10 pm
Location: West Midlands

HTPC Specs: Show details

#3

Post by technodevotee » Tue Apr 21, 2020 7:53 am

Thanks for the prompt reply Gary

I'm trying that now.

Update:
That appears to have fixed the problem as it is currently importing a new MXF.

:thumbup:

technodevotee

Posts: 963
Joined: Thu Sep 10, 2015 4:10 pm
Location: West Midlands

HTPC Specs: Show details

#4

Post by technodevotee » Tue Apr 21, 2020 8:44 am

garyan2 wrote: Tue Apr 21, 2020 7:44 am I think you had a problem before the servers went down. Your MXF file is 5 days old... servers went down 2 days ago. Without seeing where your exception is occurring, I would recommend clearing the cache and trying an update again.
Thought you might like to know that I went back through the log and you are right. The first time the error appeared was on 18 April 2020.

It seems the update failed part way through the previous day so either the PC crashed, restarted due to a windows update or something else.

Anyway, clearing the cache has resolved the problem.

Thanks again for your fantastic service - you truly are a superstar!

Post Reply