Download crashes EPG123

[Katarr]

I've searched through the various forums and I don't see anyone else having this problem, so I thought I'd post it here. I recently changed my Schedules Direct password but for got to change it in EPG123. Started getting messages from Media Center that I was running out of listings. I did some poking around, figured out what was wrong and corrected my log in detail. That now seems to be fine, but when I try to "save and exit" to load new listings, it only makes it to step 2 of 8 in Stage 1 before it crashes. I've tried clearing cache and upgrading to the latest release, but it never makes it past that point. Any ideas as to what might be going on?

[garyan2]

I've searched through the various forums and I don't see anyone else having this problem, so I thought I'd post it here. I recently changed my Schedules Direct password but for got to change it in EPG123. Started getting messages from Media Center that I was running out of listings. I did some poking around, figured out what was wrong and corrected my log in detail. That now seems to be fine, but when I try to "save and exit" to load new listings, it only makes it to step 2 of 8 in Stage 1 before it crashes. I've tried clearing cache and upgrading to the latest release, but it never makes it past that point. Any ideas as to what might be going on?

Is there anything in the trace.log file to show what the error is?

[Katarr]

As far as I can tell, it's not creating one. When I say crash, I mean it just disappears - I'm not sure it ever has a chance to close the trace log.

[garyan2]

As far as I can tell, it's not creating one. When I say crash, I mean it just disappears - I'm not sure it ever has a chance to close the trace log.

It will always create and write to a trace.log file. The crash will prevent the event log being updated, but the trace.log file will be there. Where did you install epg123? If you don't have write permission to the folder(s), it will fail at that point.

[Katarr]

Okay, found it.. for some reason there are some trace files there with dates in the name and I thought it was supposed to be like that as well. Here is the latest entry from today. Please note that it took me some time to figure out that the SD password had to be reset. I tried a few times to change it and then "Save and Exit". It would run, crash and when I went back, it appears that it hadn't saved the password change. It took me a while to figure out that I needed to save and get out cleanly so it would save it for future logins...

[07/22/2018 14:21:11] ===============================================================================
[07/22/2018 14:21:11] Activating the epg123 configuration GUI.
[07/22/2018 14:21:11] ===============================================================================
[07/22/2018 14:21:11] [ INFO] epg123 version: 1.2.1
[07/22/2018 14:21:12] [ INFO] Successfully queried the Task Scheduler for status. Could not start. Last Run 07/22/2018 03:00:00; Exit: 0xFFFFFFFF
[07/22/2018 14:21:12] [ERROR] SD API WebException Thrown. Message: The remote server returned an error: (400) Bad Request. , Status: ProtocolError
[07/22/2018 14:21:12] [ERROR] SD responded with error code: 4003 , message: Invalid username or token has expired. , serverID: 20141201.web.X , datetime: 2018-07-22T21:14:18Z
[07/22/2018 14:21:12] [ERROR] Message: Invalid username or token has expired. Response: INVALID_USER
[07/22/2018 14:21:36] [ INFO] Token request successful. serverID: 20141201.web.X
[07/22/2018 14:21:36] [ INFO] Status request successful. account expires: 2019-07-30T03:40:05Z , lineups: 1/4 , lastDataUpdate: 2018-07-22T14:07:43Z
[07/22/2018 14:21:36] [ INFO] system status: Online , message: No known issues.
[07/22/2018 14:21:37] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[07/22/2018 14:21:37] [ INFO] Successfully retrieved the station mapping for lineup USA-AZ02424-X.
[07/22/2018 14:25:07] ===============================================================================
[07/22/2018 14:25:07] Activating the epg123 client GUI. version 1.2.1 for Win7
[07/22/2018 14:25:07] ===============================================================================
[07/22/2018 14:25:07] [ INFO] Successfully queried the Task Scheduler for status. Could not start. Last Run 07/22/2018 03:00:00; Exit: 0xFFFFFFFF

[garyan2]

Thanks for the feedback. I thought I had covered that scenario for a password changes ... guess not. I'll take a look and get it fixed for next release.

[Katarr]

Sounds like you know what it is... is there a workaround? I am about to run out of guide data. Fortunately, it's summer and we are only recording one or two things.

[garyan2]

Sounds like you know what it is... is there a workaround? I am about to run out of guide data. Fortunately, it's summer and we are only recording one or two things.

It sounded like you got it working, is that not the case? When you open the EPG123 Configuration GUI, does it automatically login, or does it prompt you for a new password give a message about invalid username or expired token?

I just checked my setup here and faked an expired password. All I had to do was put the new password in to login. A 'Save' and a 'Save & Execute' both worked and it properly saved the new password hash in the cfg file.

[Katarr]

Weird. I input a new password and it looks like it took it and connected okay. When I save and exit it starts the download but crashes...or is the password failing?

[garyan2]

Back to the trace.log file... anything in there?

[Katarr]

Not since way earlier today. I went ahead and tried to run the update again, and there were no new lines in the trace log. At that point, I renamed trace.log to traceOLD.log to see if it would build a new one. I started the program, confirmed it was logged in, cleared cache, hit the lineup button and then tried to save and exit. It crashed again and there is no new trace log. I checked the account and permissions for that folder. I am using an admin account with full permissions. Do I need to start thinking about reinstalling from scratch?

[garyan2]

Not yet. This is definitely a permission problem. Right-click the EPG123 shortcut (or exe file) and select 'Run as administrator'. If it executes with no problem, then it is a permission problem.

Note: Being part of the administrator group is not the same as running as administrator. The 'run as' will elevate the program execution to full administrative rights.

[Katarr]

You called it perfectly. Seems like it ran to completion this time and the trace.log file was created. Two things..

How do I make sure that MCE pulls the new data in? Is that the scheduled task that runs later tonight or can I use MCE to "Download Channel Guide"? I am assuming that EPG123 places the data where EPG will find it.
Also - this has been running perfectly for nearly a year. How the heck do I suddenly need to run as administrator to get it to work? That seems out of the blue.

[garyan2]

If your scheduled task is set to 'Full Mode' in the client, or the 'Automatically import...' option is selected in the configuration GUI, then it will automatically import into WMC. The run you just did should have imported the guide data into WMC if the auto import was set. The 'Download Channel Guide' does nothing for you ... it is only for the MS/Rovi guide data which was disconnected when you did not accept the program guide ToS during the epg123 install.

No idea why you would suddenly need to run as admin. You can take a look at the trace.log files to see when the problem started ... maybe a Win7 update broke it or possibly some AV program is getting in the way.

[Katarr]

Okay. Well thanks for your help on this! The tool is amazing and you have been extremely helpful with support on a Sunday night no less. Thanks!