Cannot launch client after upgrade to 1.6.1.3

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
bjm051593

Posts: 6
Joined: Thu Nov 08, 2018 4:01 pm
Location:

HTPC Specs: Show details

Cannot launch client after upgrade to 1.6.1.3

#1

Post by bjm051593 » Mon Feb 01, 2021 3:55 pm

The other day I noticed the overlay icon had been red for more than a few days - looking into it, EPG stopped updating. I noticed that the scheduled task was not able to be accessed (not sure what changed to make that happen but it happened on both server and client machines).

I tried updated from 1.3 to 1.6.1.3 (I love the tray icon btw) - that didn't change the problem with accessing the task, that still fails - but now the client fails to launch.

I'm templated to flatten and rebuild, but for now, if I run the task manually the guide does update. So seems like this could be 2 distinct problems.

Any ideas on how to debug this?

Thanks,
Brian

===

[2/1/2021 9:45:58 AM] ===============================================================================
[2/1/2021 9:45:58 AM] Activating the epg123 client GUI. version 1.6.1.3
[2/1/2021 9:45:58 AM] ===============================================================================
[2/1/2021 9:45:58 AM] [ INFO] Successfully queried the Task Scheduler for status. ERROR: Access is denied.
[2/1/2021 9:45:58 AM] [ERROR] Unhandled thread exception caught from epg123Client.exe. message: Object reference not set to an instance of an object.
at epg123Client.clientForm.UpdateTaskPanel()
at epg123Client.clientForm.clientForm_Shown(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnShown(EventArgs e)
at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)
at System.Windows.Forms.Control.InvokeMarshaledCallbacks()

User avatar
garyan2

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

HTPC Specs: Show details

#2

Post by garyan2 » Mon Feb 01, 2021 4:03 pm

Not sure what could have changed, but I would suggest opening Task Scheduler and manually deleting the epg123_update task. The client will then open and you can create a new task.

Have you modified the task in any way that may be tripping up the client?
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

bjm051593

Posts: 6
Joined: Thu Nov 08, 2018 4:01 pm
Location:

HTPC Specs: Show details

#3

Post by bjm051593 » Mon Feb 01, 2021 7:02 pm

given I can't launch the client will the task still be recreated? (I'm guessing I could rename the task?)

I haven't made any changes that I recall (and I get the same behavior on 2 machines) - the thing has been sitting in the corner and "just works" so I never look at anything but the overlay icon ;)

User avatar
garyan2

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

HTPC Specs: Show details

#4

Post by garyan2 » Mon Feb 01, 2021 7:16 pm

Once you delete the task, you will be able to open the client. Because you are not able to read the status of the task (ERROR: Access is denied), the client is having difficulty updating the GUI. I must be missing an initialization of a variable when it can't access the task. Once you delete the task, you will be able to open the client and create a new task.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

User avatar
garyan2

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

HTPC Specs: Show details

#5

Post by garyan2 » Mon Feb 01, 2021 8:05 pm

Quick look in the code and I see where the code is failing when the client cannot access the status of the task. Fix will be in the next release.

If you run the client as administrator, it should open without a problem. You can try that instead of deleting the task.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

bjm051593

Posts: 6
Joined: Thu Nov 08, 2018 4:01 pm
Location:

HTPC Specs: Show details

#6

Post by bjm051593 » Tue Feb 02, 2021 3:11 pm

Thanks Gary - I can run the client as admin and that allowed me to re-create the task.

In case it helps, I can't run the task by selecting "Update Guide Now" from the tray, but it seemed to run correctly on the schedule last night (and the tray icon showed green). Suspect that's all related but just in case it helps.

Thanks again for the quick response...

Post Reply