Dear Gary,
When I mentioned above that the Manual Import just dies without logging the reason, I didn't mean Manual Import, I meant that running the "Save & Execute" in the Configuration app just dies partway through without logging the reason.
EPG123 Bug Reports
Forum rules
★ Download the latest EPG123 here: https://garyan2.github.io/ <> Setup guide here: https://garyan2.github.io/install.html ★
★ Download the latest EPG123 here: https://garyan2.github.io/ <> Setup guide here: https://garyan2.github.io/install.html ★
-
garyan2
- Posts: 7480
- Joined: Fri Nov 27, 2015 7:23 pm
- Location:
-
HTPC Specs:
Understood. I was able to duplicate and see the cause.
All, I just got word from SD that the issue should be resolved. Try to update your guide and verify.
Sent from my SM-G781U1 using Tapatalk
All, I just got word from SD that the issue should be resolved. Try to update your guide and verify.
Sent from my SM-G781U1 using Tapatalk
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io
Keeping WMC alive beyond January 2020. https://garyan2.github.io
-
CWguyFL
- Posts: 11
- Joined: Sat Sep 24, 2016 3:03 pm
- Location:
-
HTPC Specs:
Dear Gary,
Yes - new update was successful! Thanks!
Yes - new update was successful! Thanks!
-
Tallscott
- Posts: 2
- Joined: Mon Jun 23, 2014 7:03 pm
- Location:
-
HTPC Specs:
Hi Gary
I’ve got two channels where the guide data is mixed up:
Freeview West Central Scotland DVB from schedules direct. On WMC Win 10.
106 BBC Scotland HD and 108 BBC Four HD are transposed
So on 106 I’m getting BBC Four HD guide data and on 108 BBC Scotland HD
I’ve tried renumbering and renaming but it doesn’t swap the guide info.
Is there anything else I can do at my end or does it need corrected elsewhere?
Many thanks
G
I’ve got two channels where the guide data is mixed up:
Freeview West Central Scotland DVB from schedules direct. On WMC Win 10.
106 BBC Scotland HD and 108 BBC Four HD are transposed
So on 106 I’m getting BBC Four HD guide data and on 108 BBC Scotland HD
I’ve tried renumbering and renaming but it doesn’t swap the guide info.
Is there anything else I can do at my end or does it need corrected elsewhere?
Many thanks
G
-
garyan2
- Posts: 7480
- Joined: Fri Nov 27, 2015 7:23 pm
- Location:
-
HTPC Specs:
To get the lineup corrected you will need to submit a ticket with Schedules Direct.
In the meantime, you can manually map the listings to the proper channel. https://garyan2.github.io/map.html
You will select channel 106 on the left side (tuner channel) and then right-click channel 108 BBC Scotland on the right side and select 'Subscribe'. Do the same for tuner channel 108 with BBC Four.
In the meantime, you can manually map the listings to the proper channel. https://garyan2.github.io/map.html
You will select channel 106 on the left side (tuner channel) and then right-click channel 108 BBC Scotland on the right side and select 'Subscribe'. Do the same for tuner channel 108 with BBC Four.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io
Keeping WMC alive beyond January 2020. https://garyan2.github.io
-
Space
- Posts: 2841
- Joined: Sun Jun 02, 2013 9:44 pm
- Location:
-
HTPC Specs:
Maybe not a bug, and I have certainly seen these in the past, but usually only a few of them at a time and then they go away the next update, but it is now becoming a more consistent issue.
I have over 125 of these log entries for different channels in the log for a single update:
[11/24/2023 7:44:05 PM] [ INFO] Service !Service!EPG123_50276: WABCDT3: first mxf schedule entry to verify is in the future at 11/24/2023 9:00:00 PM.
I don't think it is a bug, but was wondering what exactly these log entries means and why I might be seeing over a hundred of them every update now for the past week or so?
I have over 125 of these log entries for different channels in the log for a single update:
[11/24/2023 7:44:05 PM] [ INFO] Service !Service!EPG123_50276: WABCDT3: first mxf schedule entry to verify is in the future at 11/24/2023 9:00:00 PM.
I don't think it is a bug, but was wondering what exactly these log entries means and why I might be seeing over a hundred of them every update now for the past week or so?
-
sjr56stn
- Posts: 77
- Joined: Tue Mar 03, 2015 4:49 pm
- Location:
-
HTPC Specs:
Now that the Schedules Direct server seems to have come back online this morning, my EPG123 is not loading the mxf file, and epg123client.exe throws an exception:
[26/11/2023 11:56:49] [ERROR] Unhandled exception caught from epg123Client.exe. message: Access to the path 'Global\{CD7E6857-7D92-4A2F-B3AB-ED8CB42C6F65}' is denied.
Any ideas?
[26/11/2023 11:56:49] [ERROR] Unhandled exception caught from epg123Client.exe. message: Access to the path 'Global\{CD7E6857-7D92-4A2F-B3AB-ED8CB42C6F65}' is denied.
Any ideas?
-
sjr56stn
- Posts: 77
- Joined: Tue Mar 03, 2015 4:49 pm
- Location:
-
HTPC Specs:
Oh! Tried EPD123_gui again and now everything works OK.
-
garyan2
- Posts: 7480
- Joined: Fri Nov 27, 2015 7:23 pm
- Location:
-
HTPC Specs:
Not a bug since the only issue is unexplained log entries. This is due to me no longer downloading a previous days worth of guide data for the stations. All days are based on UTC time, so the closer you run an update to 0000Z, the more likely you will see these entries. The "missing" schedule entry is actually from a previous day, so the first guide entry in the mxf file for that station on the current day may start later than the current time.Space wrote: ↑Sat Nov 25, 2023 3:08 am Maybe not a bug, and I have certainly seen these in the past, but usually only a few of them at a time and then they go away the next update, but it is now becoming a more consistent issue.
I have over 125 of these log entries for different channels in the log for a single update:
[11/24/2023 7:44:05 PM] [ INFO] Service !Service!EPG123_50276: WABCDT3: first mxf schedule entry to verify is in the future at 11/24/2023 9:00:00 PM.
I don't think it is a bug, but was wondering what exactly these log entries means and why I might be seeing over a hundred of them every update now for the past week or so?
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io
Keeping WMC alive beyond January 2020. https://garyan2.github.io
-
Space
- Posts: 2841
- Joined: Sun Jun 02, 2013 9:44 pm
- Location:
-
HTPC Specs:
I see, I think I do remember when you mentioned you were not downloading the previous day anymore.
I guess since I update at the same time all year (around 7:20pm ET), I would be much less likely to see these log entries when Daylight Savings Time is in effect, since that would mean it is 11:20pm UTC at 7:20pm EDT, so it would download updates to the days worth of data that is almost over.
If I understand correctly, you are more likely to get these log entries if you run the update closely AFTER midnight UTC. Closely BEFORE midnight UTC is when you are the least likely to see them, due to it downloading a whole extra days worth of programs (most of which will have already aired in the local timezone).
If so, to minimize these entries all year round, I could set the update to start before 7pm ET, which would make sure it is always downloading the days data for the day that is almost over. In fact, it is probably best to change it because if there are any last minute updates to programs starting between 7pm-midnight (EST) on the current day, those would not be updated at all if the update occurs after 7pm EST (midnight UTC).
I guess since I update at the same time all year (around 7:20pm ET), I would be much less likely to see these log entries when Daylight Savings Time is in effect, since that would mean it is 11:20pm UTC at 7:20pm EDT, so it would download updates to the days worth of data that is almost over.
If I understand correctly, you are more likely to get these log entries if you run the update closely AFTER midnight UTC. Closely BEFORE midnight UTC is when you are the least likely to see them, due to it downloading a whole extra days worth of programs (most of which will have already aired in the local timezone).
If so, to minimize these entries all year round, I could set the update to start before 7pm ET, which would make sure it is always downloading the days data for the day that is almost over. In fact, it is probably best to change it because if there are any last minute updates to programs starting between 7pm-midnight (EST) on the current day, those would not be updated at all if the update occurs after 7pm EST (midnight UTC).
-
garyan2
- Posts: 7480
- Joined: Fri Nov 27, 2015 7:23 pm
- Location:
-
HTPC Specs:
Correct. Anytime before 0000Z you will be okay and won't get the log entries. I run my updates around 1400Z and I set my number of days to download to 15 so I will have 14 days worth of guide listings which is what I personally want. I used to force the additional, mostly past previous day if the update was run between 0000Z and 0400Z... I may do that again but obviously it doesn't affect anything unless you importing into an empty database and some stations may have no data for programs that are currently in progress.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io
Keeping WMC alive beyond January 2020. https://garyan2.github.io
-
wilme2
- Posts: 57
- Joined: Mon Jul 08, 2013 6:33 pm
- Location:
-
HTPC Specs:
I have been having a lot of problems with the recent releases. Deleted cable channels and No Guide Data on OTA sub-channels that have previously been populated. (On the OTA sub-channels I may have figured out that somehow the Local Broadcast Listings were Excluded instead of Included?- I have to wait until all recordings are complete to test the changes I made.)
On the cable channel issue. Yesterday I downloaded 1.8.2.7, and did the undelete on my missing cable channels. I manually mapped the listings to those channels. The guide looked like I wanted. I ran an update, and it looked good. This morning however, every single channel (both cable and OTA) showed No Guide Data, even though the logs showed a good update at 4am. So I did an Update Guide Now and it successfully pulled in the guide data. But then I realized there were no recordings actually scheduled. So I had to go into every one of my ~80 series recordings and do a change/save - and each one started showing recordings again. But now I realize that the channels I undeleted yesterday are once again deleted.
Do I undelete the channels again? What nuclear bomb killed my guide and schedule recordings? The only weird log entry I see is [**** Intercepted "mcupdate.exe -uf -nogc" call. Ignored. ****]
On the cable channel issue. Yesterday I downloaded 1.8.2.7, and did the undelete on my missing cable channels. I manually mapped the listings to those channels. The guide looked like I wanted. I ran an update, and it looked good. This morning however, every single channel (both cable and OTA) showed No Guide Data, even though the logs showed a good update at 4am. So I did an Update Guide Now and it successfully pulled in the guide data. But then I realized there were no recordings actually scheduled. So I had to go into every one of my ~80 series recordings and do a change/save - and each one started showing recordings again. But now I realize that the channels I undeleted yesterday are once again deleted.
Do I undelete the channels again? What nuclear bomb killed my guide and schedule recordings? The only weird log entry I see is [**** Intercepted "mcupdate.exe -uf -nogc" call. Ignored. ****]
-
garyan2
- Posts: 7480
- Joined: Fri Nov 27, 2015 7:23 pm
- Location:
-
HTPC Specs:
1. For the OTA sub-channels, yes. Excluding the lineup means they would not have gotten any guide data. Once the OTA lineup is included then you should be good.
2. Version 1.8.2.7 changes are to mitigate the problem of channels being deleted if the lineup station is changed/removed. This shouldn't be a problem going forward. WMC was actually doing this when the MXF file was imported into the database before I could do anything about it. This is basically because when MS was managing your tuner channels and guide listings at the same time, they were linked and would appear and disappear together. Now with the tuner channels and guide listings being 2 separate things, when a lineup no longer contains a channel that was in the database, both the tuner channel and guide channel are orphaned.
For all guide listings disappearing, sounds like your database crashed and WMC built a new one. When it builds a new database, there are no guide listings until you import them again. Also, when it rebuilt the database, it uses the last saved configuration in its backup files which was probably before you undeleted the channels. You can undelete them again.
After the guide listings are imported by EPG123, WMC has to perform a database indexing and once it is complete will index the scheduled recordings. You may have been looking at the scheduled recordings while the database was being indexing and before the scheduled recordings were indexed. It would have probably populated the scheduled recordings on its own without you having to "force" it by saving each request.
2. Version 1.8.2.7 changes are to mitigate the problem of channels being deleted if the lineup station is changed/removed. This shouldn't be a problem going forward. WMC was actually doing this when the MXF file was imported into the database before I could do anything about it. This is basically because when MS was managing your tuner channels and guide listings at the same time, they were linked and would appear and disappear together. Now with the tuner channels and guide listings being 2 separate things, when a lineup no longer contains a channel that was in the database, both the tuner channel and guide channel are orphaned.
For all guide listings disappearing, sounds like your database crashed and WMC built a new one. When it builds a new database, there are no guide listings until you import them again. Also, when it rebuilt the database, it uses the last saved configuration in its backup files which was probably before you undeleted the channels. You can undelete them again.
After the guide listings are imported by EPG123, WMC has to perform a database indexing and once it is complete will index the scheduled recordings. You may have been looking at the scheduled recordings while the database was being indexing and before the scheduled recordings were indexed. It would have probably populated the scheduled recordings on its own without you having to "force" it by saving each request.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io
Keeping WMC alive beyond January 2020. https://garyan2.github.io
-
wilme2
- Posts: 57
- Joined: Mon Jul 08, 2013 6:33 pm
- Location:
-
HTPC Specs:
Gary, my guide is all fixed now after I included the OTA lineup and re-added the deleted cable channels. THANK YOUgaryan2 wrote: ↑Tue Nov 28, 2023 1:43 am 1. For the OTA sub-channels, yes. Excluding the lineup means they would not have gotten any guide data. Once the OTA lineup is included then you should be good.
2. Version 1.8.2.7 changes are to mitigate the problem of channels being deleted if the lineup station is changed/removed. This shouldn't be a problem going forward.
-
wilme2
- Posts: 57
- Joined: Mon Jul 08, 2013 6:33 pm
- Location:
-
HTPC Specs:
Well that didn't age well. Monday night we came home to find that our shows were not being recorded. They showed fine in the scheduled recordings and even said NOW next to some, but no record recording indicator or recordings were being created. I could still use the guide fine and tune all channels. I then rebooted- and when it came back up my Live TV setup within WMC was completely gone. I had a full image backup of the hard drive from the night before, but I went to Live TV to setup the cable and OTA again to see if it would work. It took several attempts and things didn't work as expected - I had to agree to the EPG (not deny), a VHF channel was automatically re-added, and I also had re-run the EPG123 tweak to allow > 4 tuners. I finally got the guide updated and everything working, but my series recordings were gone. I had a backup from 10/1/23 that I loaded, and recording resumed as usual. I still have to go unselect a few hundred channels I don't want in the guide.
A real pain to be spending this much time keeping WMC running on a PC that is otherwise perfectly stable. And on top of that I am finally going to have to call Spectrum about a high-split converter for the cable cards. (At least they now admit that is an option.)
-
Space
- Posts: 2841
- Joined: Sun Jun 02, 2013 9:44 pm
- Location:
-
HTPC Specs:
Code: Select all
1/8/2024 6:55:36 PM] [WARNG] Requests for MD5 schedule entries of station 102073 returned error code 7030 , message: You have requested a schedule which is not in any of your configured lineups.
[1/8/2024 6:55:36 PM] [WARNG] Requests for MD5 schedule entries of station 102074 returned error code 7030 , message: You have requested a schedule which is not in any of your configured lineups.Since I don't subscribe to these two stations (they are premium sport stations) I have now unselected them for download, but I'm still curious what these messages mean.
-
garyan2
- Posts: 7480
- Joined: Fri Nov 27, 2015 7:23 pm
- Location:
-
HTPC Specs:
That would be a problem on Schedules Direct's end. The lineup you are subscribed to lists those stations in it but the server is rejecting your request. Submit a ticket with SD.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io
Keeping WMC alive beyond January 2020. https://garyan2.github.io
-
Space
- Posts: 2841
- Joined: Sun Jun 02, 2013 9:44 pm
- Location:
-
HTPC Specs:
It looks like it might be a more wide spread problem...
-
Space
- Posts: 2841
- Joined: Sun Jun 02, 2013 9:44 pm
- Location:
-
HTPC Specs:
Gary,
I have had my StorageWarningGB set to 120 since I started using it, however, recently I noticed that I hadn't gotten any warnings mailed to me in a while, so checked the log and saw that free space was down to around 73 GB.
First thing I did was check the EPG123 log to see when the free space dropped below 120GB and it was on 1/25. I then checked if the email settings in EPG123 were correct and they were, and I was able to successfully send a test email from EPG123.
I then looked at the storage setting in the client, and that is where I saw the problem, somehow the StorageWarningGB was set to -1 instead of 120.
Do you have any idea what might have caused this change?
It looks like the config.json file was touched today, during the last automatic update, so I was unable to use the modification timestamp to determine when this config change might have happened. Does the client modify this file every time it runs for some reason?
I'm running version 1.8.2.7.
I have had my StorageWarningGB set to 120 since I started using it, however, recently I noticed that I hadn't gotten any warnings mailed to me in a while, so checked the log and saw that free space was down to around 73 GB.
First thing I did was check the EPG123 log to see when the free space dropped below 120GB and it was on 1/25. I then checked if the email settings in EPG123 were correct and they were, and I was able to successfully send a test email from EPG123.
I then looked at the storage setting in the client, and that is where I saw the problem, somehow the StorageWarningGB was set to -1 instead of 120.
Do you have any idea what might have caused this change?
It looks like the config.json file was touched today, during the last automatic update, so I was unable to use the modification timestamp to determine when this config change might have happened. Does the client modify this file every time it runs for some reason?
I'm running version 1.8.2.7.
-
jea101
- Posts: 5
- Joined: Wed Apr 01, 2015 2:57 pm
- Location:
-
HTPC Specs:
[ERROR]Of expected 850 stations only796 available – aborting update
My last successful MXF creation was at 3:30 AM EDT on Jan 26.
Now I get the aborting message.
I run the EPG updates on two different Windows 8.1 PCs
One updates at 3:30 AM and the other at 6:45 PM.
Also, the other PC shows 885 expected 840 available.
I am using Charter Spectrum South Pinellas and Local broadcast 33706 lineups
My last successful MXF creation was at 3:30 AM EDT on Jan 26.
Now I get the aborting message.
I run the EPG updates on two different Windows 8.1 PCs
One updates at 3:30 AM and the other at 6:45 PM.
Also, the other PC shows 885 expected 840 available.
I am using Charter Spectrum South Pinellas and Local broadcast 33706 lineups
Code: Select all
[1/29/2024 8:04:40 AM] =====================================================================================
[1/29/2024 8:04:40 AM] EPG123: Beginning MXF and XMLTV file updates. version 1.8.2.7
[1/29/2024 8:04:40 AM] =====================================================================================
[1/29/2024 8:04:40 AM] *** Windows 8.1 Pro with Media Center, 64-bit [Version: 6.3.9600.20778] ***
[1/29/2024 8:04:40 AM] *** .NET Framework 4.8.03761 is installed. ***
[1/29/2024 8:04:40 AM] [ INFO] DaysToDownload: 14 , TheTVDBNumbers : True , PrefixEpisodeTitle: False , PrefixEpisodeDescription : False , AppendEpisodeDesc: False , OADOverride : True , SeasonEventImages : True , IncludeSDLogos : True , AutoAddNew: True , CreateXmltv: False
[1/29/2024 8:04:40 AM] [ INFO] Token request successful. serverID: GH2-01 , datetime: 2024-01-29T12:53:31Z
[1/29/2024 8:04:40 AM] [ INFO] Status request successful. account expires: 2024-11-13T16:34:53Z , lineups: 2/4 , lastDataUpdate: 2024-01-29T13:01:48Z
[1/29/2024 8:04:40 AM] [ INFO] System status: Online , message: No known issues.
[1/29/2024 8:04:43 AM] [ INFO] Successfully requested listing of subscribed lineups from Schedules Direct.
[1/29/2024 8:04:43 AM] Entering BuildLineupServices() for 2 lineups.
[1/29/2024 8:04:43 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-FL09499-L. (798 stations; 892 channels)
[1/29/2024 8:04:44 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-33706. (117 stations; 117 channels)
[1/29/2024 8:04:44 AM] [ INFO] Kicking off background worker to download and process 29 station logos.
[1/29/2024 8:04:44 AM] [ INFO] Stations no longer available since last configuration save are: AYM, BABYUS, C1RWN, CAN24, DEPELUS, DJCH, DJCHHD, DWPLUS, DXD, DXDHD, DXDS, ELREY, ELREYHD, ESPCE7H, ESPCE8H, ESPEX, ESPNCE7, ESPNCE8, FILIPE, FOXLFUS, FREEFRM, FREFMHD, FUSION, FUSIONH, FXM, FXMHD, FXX, FXXHD, GOLTVE, GOLTVEH, HAPA, IMPCNET, MGMHD, NBCSNFH, NBCSNFL, NEWSY, NEWSYSD, NGMUNDO, NGWIHD, NGWILD, OLY, OLYHD, RTNPLUS, SECA, SECAHD, SMLLTS, UPLIFHD, UPLIFTV, VROLA, VROLAHD, ZEETV, WTAMLP, WVEALP, WZRACA
[1/29/2024 8:04:44 AM] [ INFO] Stations added for download since last configuration save are: WSNNLD, ACUWTHH, JBS, GRIOE, FOXWXSD, VICTSD, AMCPLDM, QVC3, CARSTV, JUSTSD, PETSTV, RECIPE, AFRCA, EARTHX, IMPACSD, FILPEHD, ZEETVH, WVEA6SD, STRY, CNL24, KIDSSHD, HOGARHD, DPLUSSD, VMEHD, VICTORY, HALLDR, FOXWX, STELLAR, DLCHD, AFRCAHD, STARTTV, CHIMETV, CARSTVH, JUST, PETSTVH, RECIPEH, CHPDM, ITVGHD, VMOVHD, WVEADT6, WTVTDT6, WBKHLD, WBKHLD2, WBKHLD3, WBKHLD4, WGCTLD, WGCTLD2, WGCTLD3, WGCTLD4, WGCTLD5, WGCTLD6, WGCTLD7, WGCTLD8, WXAXCD4, WXAXCD5, WXAXCD6, WFTSDT5, WFTSDT6, W32FHD2, W32FHD3, W32FHD4, W32FHD5, W32FHD6, WSPFCD5, WDNPLD, WDNPLD2, WDNPLD3, WDNPLD4, WDNPLD5, WWSBDT3, W16DQD3, W16DQD4, WTOGDT5, WTOGDT6, WTOGDT7, WRMDCD2, WRMDCD3, WRMDCD4, WTSPDT5, WVEADT5, WFTTDT5, WFTTDT6, WFTTDT7, WXPXDT7, WXPXDT8, WXPXDT9
[1/29/2024 8:04:44 AM] Exiting BuildLineupServices(). SUCCESS.
[1/29/2024 8:04:44 AM] [ERROR] Of the expected 850 stations to download, there are only 796 stations available from Schedules Direct. Aborting update for review by user.
[1/29/2024 8:04:44 AM] [ INFO] EPG123 update execution time was 00:00:03.8754165.
[1/29/2024 8:04:44 AM] [ERROR] Failed to create MXF file. Exiting.
[1/29/2024 8:04:50 AM] =====================================================================================
[1/29/2024 8:04:50 AM] EPG123CLIENT: Beginning MXF file import. version 1.8.2.7
[1/29/2024 8:04:50 AM] =====================================================================================
[1/29/2024 8:04:50 AM] *** Windows 8.1 Pro with Media Center, 64-bit [Version: 6.3.9600.20778] ***
[1/29/2024 8:04:50 AM] *** .NET Framework 4.8.03761 is installed. ***
[1/29/2024 8:04:50 AM] *** Windows Media Center [Version: 6.3.9600.16384] is installed. ***
[1/29/2024 8:04:50 AM] [ INFO] Import: True , Match: True , NoLogo: False , Force: False , ShowProgress: False , NoGC: False , NoVerify: False , Verbose: False
[1/29/2024 8:04:53 AM] Entering ImportMxfFile() for file "C:\ProgramData\GaRyan2\epg123\output\epg123.mxf".
[1/29/2024 8:06:10 AM] [ INFO] Successfully imported .mxf file into Media Center database. Exit code: 0
[1/29/2024 8:06:10 AM] Exiting ImportMxfFile(). SUCCESS.
[1/29/2024 8:06:10 AM] Entering VerifyLoad()
[1/29/2024 8:06:32 AM] [ INFO] Checked 285162 entries and corrected 0 of them.
[1/29/2024 8:06:32 AM] Exiting VerifyLoad()
[1/29/2024 8:06:34 AM] [ INFO] Completed the automatic mapping of lineup stations to tuner channels.
[1/29/2024 8:06:34 AM] [ INFO] Completed lineup refresh.
[1/29/2024 8:06:34 AM] Entering ReindexDatabase()
[1/29/2024 8:06:34 AM] [ INFO] INFO: WMC database indexing is currently running.
[1/29/2024 8:06:34 AM] Exiting ReindexDatabase(). SUCCESS.
[1/29/2024 8:06:34 AM] [ INFO] MXF file was created on 1/26/2024 3:30:02 AM
[1/29/2024 8:06:34 AM] [ERROR] The MXF file imported is 76.61 hours old.
[1/29/2024 8:06:34 AM] [ INFO] Completed EPG123 client execution.
[1/29/2024 8:06:34 AM] [ INFO] EPG123 client execution time was 00:01:44.1361921.
[1/29/2024 8:08:05 AM] =====================================================================================
[1/29/2024 8:08:05 AM] EPG123CLIENT: Beginning WMC recorder storage/tuner conflict checks. version 1.8.2.7
[1/29/2024 8:08:05 AM] =====================================================================================
[1/29/2024 8:08:05 AM] *** Windows 8.1 Pro with Media Center, 64-bit [Version: 6.3.9600.20778] ***
[1/29/2024 8:08:05 AM] *** .NET Framework 4.8.03761 is installed. ***
[1/29/2024 8:08:05 AM] *** Windows Media Center [Version: 6.3.9600.16384] is installed. ***
[1/29/2024 8:08:05 AM] [ INFO] WMC database indexing took 00:11:22.3178456. Exit: 0x00000000
[1/29/2024 8:08:05 AM] [ INFO] Recorder storage drive F:\ has 348.439 GB available. (3.279 TB of 3.619 TB used)
[1/29/2024 8:08:18 AM] [ INFO] No tuner conflicts detected within next 3 days.
[1/29/2024 8:08:18 AM] [ INFO] Completed WMC recorder storage/tuner conflict checks.