Router Change Broke epg123 import

An evolving, supported alternative to Rovi
Forum rules
★ Download the latest EPG123 here: http://epg123.garyan2.net <> Setup guide here: http://epg123.garyan2.net/downloads/epg123_Guide.pdf
Post Reply
User avatar
gzarzycki

Posts: 32
Joined: Fri Nov 08, 2019 9:44 pm
Location: Tucson, AZ.

HTPC Specs: Show details

Router Change Broke epg123 import

#1

Post by gzarzycki » Wed Dec 04, 2019 6:10 pm

Gary, I changed my router and now my client gets the error: Unhandled exception caught from epg123Client.exe. I took ownership of the ehome folders, the epg123 folders and the server folder. As you see, it wrote to the log, then errors with message: "Cannot open log for source 'epg123Client" I am dumbfounded why this is happening after changing a the home router.

[12/4/2019 10:29:27 AM] [ INFO] Matching MOVIEDM to channel 1899
[12/4/2019 10:29:28 AM] [ INFO] Completed the automatch of lineup stations to tuner channels.
[12/4/2019 10:29:28 AM] [ INFO] Completed lineup refresh.
[12/4/2019 10:29:28 AM] Entering runWmcTask(ReindexSearchRoot)
[12/4/2019 10:29:28 AM] [ INFO] SUCCESS: Attempted to run the scheduled task "Microsoft\Windows\Media Center\ReindexSearchRoot".
[12/4/2019 10:29:28 AM] [ INFO] Successfully started the ReindexSearchRoot task. Exit code: 0
[12/4/2019 10:29:28 AM] Exiting runWmcTask(ReindexSearchRoot). SUCCESS.
[12/4/2019 10:29:28 AM] Entering runWmcTask(PvrScheduleTask)
[12/4/2019 10:29:29 AM] [ INFO] SUCCESS: Attempted to run the scheduled task "Microsoft\Windows\Media Center\PvrScheduleTask".
[12/4/2019 10:29:29 AM] [ INFO] Successfully started the PvrScheduleTask task. Exit code: 0
[12/4/2019 10:29:29 AM] Exiting runWmcTask(PvrScheduleTask). SUCCESS.
[12/4/2019 10:29:29 AM] [ INFO] Completed EPG123 client execution.
[12/4/2019 10:29:29 AM] [ INFO] EPG123 client execution time was 00:01:16.5337344.
[12/4/2019 10:29:29 AM] [ERROR] Unhandled exception caught from epg123Client.exe. message: Cannot open log for source 'epg123Client'. You may not have write access.

User avatar
garyan2

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

HTPC Specs: Show details

#2

Post by garyan2 » Wed Dec 04, 2019 6:17 pm

Yah, that doesn't make sense. It may be the event log and not the trace.log file that it can't access. I'll take a look at my code to see if the error message could be better defined.

At the end of the run, epg123 will close the event log entry that was opened at the beginning with a lot of the information in the trace.log file, so the timing is right.
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

User avatar
gzarzycki

Posts: 32
Joined: Fri Nov 08, 2019 9:44 pm
Location: Tucson, AZ.

HTPC Specs: Show details

#3

Post by gzarzycki » Wed Dec 04, 2019 6:40 pm

garyan2 wrote:
Wed Dec 04, 2019 6:17 pm
Yah, that doesn't make sense. It may be the event log and not the trace.log file that it can't access. I'll take a look at my code to see if the error message could be better defined.

At the end of the run, epg123 will close the event log entry that was opened at the beginning with a lot of the information in the trace.log file, so the timing is right.
I'm tearing my hair out, what little I have. It makes no sense. I can read and write in all folders, so it appears a Windows file lock may be occuring. Changing my router shouldn't have anything to do with this, as the read and write is on the same PC. I even moved the .mxf file to the same folder instead of accessing across the LAN to eliminate the possibility of the a router causing the issue, but no go. I opened a command window with Admin privileges and ran this with no success: "C:\Program Files (x86)\epg123\epg123Client.exe" -i C:\ProgramData\GaRyan2\epg123\output\epg123.mxf -match

User avatar
garyan2

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

HTPC Specs: Show details

#4

Post by garyan2 » Wed Dec 04, 2019 6:50 pm

Dont sweat it too much right now. Everything is working, your guide is getting updated. It is just throwing an error when it is closing. That error has no impact on your guide itself.
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

User avatar
gzarzycki

Posts: 32
Joined: Fri Nov 08, 2019 9:44 pm
Location: Tucson, AZ.

HTPC Specs: Show details

#5

Post by gzarzycki » Wed Dec 04, 2019 7:42 pm

The guide is not being written. I open WMC and no EPG and no icons. I have no idea what is going on. it had been working until today. I had an issue with the tuners this morning. I ran the tuner setup again, did not let it get the guide. The tuners setup fine, but my EPG was gone. I then ran the epg123 and this started happening. I suspect I may need to run the client setup again and see if fixes it.

User avatar
garyan2

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

HTPC Specs: Show details

#6

Post by garyan2 » Wed Dec 04, 2019 8:05 pm

Running tv setup disconnects your guide data. You will have to click the Match by: [# Number] again.
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

User avatar
gzarzycki

Posts: 32
Joined: Fri Nov 08, 2019 9:44 pm
Location: Tucson, AZ.

HTPC Specs: Show details

#7

Post by gzarzycki » Wed Dec 04, 2019 8:29 pm

It seems the new router has created a cascade of issues. Now it won't complete the install because WMC is having issues installing Playready. Now I have to figure out why that is.

User avatar
gzarzycki

Posts: 32
Joined: Fri Nov 08, 2019 9:44 pm
Location: Tucson, AZ.

HTPC Specs: Show details

#8

Post by gzarzycki » Wed Dec 04, 2019 9:01 pm

Still no go. Fixed the Playready, restored the guide on epg123. All my channels were showing in the left screen. Did the install without errors. Checked WMC no guide. Ran the EPG update again, got the error again in the log, and still no epg.

User avatar
gzarzycki

Posts: 32
Joined: Fri Nov 08, 2019 9:44 pm
Location: Tucson, AZ.

HTPC Specs: Show details

#9

Post by gzarzycki » Wed Dec 04, 2019 9:19 pm

Okay, reinstalled epg123 again, no errors on the install, but the error continues in the log and it does not install the epg. At this point, I am lost to what the issue is other then I suspect folders or files are locked.

User avatar
garyan2

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

HTPC Specs: Show details

#10

Post by garyan2 » Wed Dec 04, 2019 9:22 pm

Take a snapshot of your client gui and post please. Showing both the left side and the right side lineup.
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

User avatar
gzarzycki

Posts: 32
Joined: Fri Nov 08, 2019 9:44 pm
Location: Tucson, AZ.

HTPC Specs: Show details

#11

Post by gzarzycki » Wed Dec 04, 2019 9:58 pm

Okay, I am reinstalling the old router, as it has caused many issues. I'll post it in a few minutea

User avatar
garyan2

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

HTPC Specs: Show details

#12

Post by garyan2 » Wed Dec 04, 2019 10:56 pm

For your guide, I think I understand now. Since you did a WMC TV Setup again, outside the client setup routine, you need to set a couple registry entries for the guide and search icons to show in WMC.

Code: Select all

[HKLM\\SOFTWARE\\Microsoft\\windows\\CurrentVersion\\Media Center\\Settings\\ProgramGuide]
"fAgreeTOS" = 1
"strAgreedTOSVersion" = "1.0"
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

User avatar
gzarzycki

Posts: 32
Joined: Fri Nov 08, 2019 9:44 pm
Location: Tucson, AZ.

HTPC Specs: Show details

#13

Post by gzarzycki » Wed Dec 04, 2019 11:09 pm

I'll keep this for reference but as I mentioned, after re-installing the old router, I did another setup and now the guide is there. This make no sense, maybe another coincidence I dunno, but my head hurts.

Thanks,
Gary

User avatar
gzarzycki

Posts: 32
Joined: Fri Nov 08, 2019 9:44 pm
Location: Tucson, AZ.

HTPC Specs: Show details

#14

Post by gzarzycki » Thu Dec 05, 2019 3:16 pm

The EPG is there now as I mentioned, but I still am getting the error message in the trace.log file. I wouldn't think the registry mod you mentioned would have anything to do with the trace.log error? I have not been able to fix this issue, no lock files that I can find. Is the Error referring to the trace.log being locked and if so, do you have any ideas why this is only happening on the one client PC?

Thanks,
Gary

[12/5/2019 1:19:22 AM] [ INFO] Completed EPG123 client execution.
[12/5/2019 1:19:22 AM] [ INFO] EPG123 client execution time was 00:02:17.4986415.
[12/5/2019 1:19:22 AM] [ERROR] Unhandled exception caught from epg123Client.exe. message: Cannot open log for source 'epg123Client'. You may not have write access.

User avatar
garyan2

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

HTPC Specs: Show details

#15

Post by garyan2 » Thu Dec 05, 2019 3:26 pm

This error is probably coming from the event log, not the trace log. The event log can be seen by opening Event Viewer and navigating to Media Center. If you are not seeing any entries from epg123 or epg123client, then your user account evidently doesn't have rights to write to the log.

I've never seen this before, so it is something new that you have done that no one else has, or at least has never reported.
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

User avatar
gzarzycki

Posts: 32
Joined: Fri Nov 08, 2019 9:44 pm
Location: Tucson, AZ.

HTPC Specs: Show details

#16

Post by gzarzycki » Thu Dec 05, 2019 3:37 pm

Okay, that gives me a new thing to chase. I never thought about that. When you said Event log earlier, I thought you were meaning the trace.log.

It might be a new issue, but I doubt it has anything to do with epg123, possibly a corrupt event log. I am a fanatic at watching logs so to make sure the software is running properly. Programmers habit I suppose. This is why I have the SM32 email program running in a batch file to send myself the logs.

Thanks,
Gary

User avatar
gzarzycki

Posts: 32
Joined: Fri Nov 08, 2019 9:44 pm
Location: Tucson, AZ.

HTPC Specs: Show details

#17

Post by gzarzycki » Thu Dec 05, 2019 3:40 pm

BTW, I ran epg123client under Administrator and still got the error. I did this thinking the possibility of a permission issue.

adam1991

Posts: 2680
Joined: Sat Jun 11, 2011 2:31 pm
Location:

HTPC Specs: Show details

#18

Post by adam1991 » Thu Dec 05, 2019 4:22 pm

garyan2 wrote:
Thu Dec 05, 2019 3:26 pm
This error is probably coming from the event log, not the trace log. The event log can be seen by opening Event Viewer and navigating to Media Center. If you are not seeing any entries from epg123 or epg123client, then your user account evidently doesn't have rights to write to the log.

I've never seen this before, so it is something new that you have done that no one else has, or at least has never reported.
I know what my vote is.

User avatar
gzarzycki

Posts: 32
Joined: Fri Nov 08, 2019 9:44 pm
Location: Tucson, AZ.

HTPC Specs: Show details

#19

Post by gzarzycki » Thu Dec 05, 2019 4:53 pm

You hit the nail on the head. Something messed with the event viewer permissions and the "system" permission did not exist in the "RtBackup" folder so the Windows Eventlog was not starting. I had to add the system permission while in Safe mode and restart the PC, now it works.

Post Reply