No Updates to Guide - Failed to create MXF file

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
mawse1

Posts: 8
Joined: Tue Dec 19, 2017 11:26 am
Location:

HTPC Specs: Show details

No Updates to Guide - Failed to create MXF file

#1

Post by mawse1 » Tue Jun 30, 2020 7:26 am

Hi there

Im running version 1.1.17 and have been for a couple of years with no problems.
Nothing has changed, it just keeps on working as it should (big thumbs up Gary), but I noticed yesterday only had guide listings until friday - so had a quick look in the log file and found this.......
--------------------------------
[29/06/2020 17:00:18] [ERROR] The expected number of stations to download is 242 but there are only 217 stations available from Schedules Direct. Aborting update for review by user.
[29/06/2020 17:00:18] [ERROR] Failed to create MXF file. Exiting.
----------------------------------

Im guessing this is the issue - any advice/pointers on what to do and where to do it?

cheers

User avatar
garyan2

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

HTPC Specs: Show details

#2

Post by garyan2 » Tue Jun 30, 2020 4:10 pm

This is a safeguard against losing a lot, if not all, of your channels due to a problem with Schedules Direct's upstream. If at the beginning of an update, the number of stations available for download are less than 95% of the number of stations that were available when you last saved your EPG123 configuration file, then it will abort the update. The numbers you provided show you are at 90%.

The review by the user is to look at your lineups in the configuration GUI and determine whether there is something wrong or not. If you are missing stations, then you should submit a ticket to Schedules Direct to rectify that. If the reduction in the number is due to removing a lineup from your downloads, or simply the stations are no longer available from your provider, then you can click the [Save] or [Save & Execute] buttons to rebaseline the number of stations from 242 to 217. It will then pass the station count check and continue with the update.
- Gary
Keeping WMC alive beyond January 2020. http://epg123.garyan2.net

mawse1

Posts: 8
Joined: Tue Dec 19, 2017 11:26 am
Location:

HTPC Specs: Show details

#3

Post by mawse1 » Wed Jul 01, 2020 7:04 am

:thumbup: That did the trick - update as normal last night

User avatar
IT Troll

Posts: 789
Joined: Sun Nov 27, 2011 9:42 am
Location: Edinburgh, UK

HTPC Specs: Show details

#4

Post by IT Troll » Wed Jul 01, 2020 5:36 pm

It just hit the very same issue, albeit with a much smaller number of channels. It would seem a number of OTA channels were taken off air last week to make way for 5G. :thumbdown:

Code: Select all

[01/07/2020 06:15:04] [ERROR] The expected number of stations to download is 18 but there are only 16 stations available from Schedules Direct. Aborting update for review by user.
[01/07/2020 06:15:04] [ERROR] Failed to create MXF file. Exiting.
I guess the answer to this issue would be to have the Home Screen status icon enabled. I turned this off as I so rarely have any problems. Would it be possible for the icon to only appear in a warning/error situation? i.e. make the green icon invisible.
Are you a Recorded TV HD user or want to give it a try? Check out the new community-made update; Recorded TV HD v2.1

User avatar
garyan2

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

HTPC Specs: Show details

#5

Post by garyan2 » Thu Jul 02, 2020 4:59 am

Oh, fine. The code is written to add an option to only display Warning and Errors, but right now I'm debating whether to show if there is an update as well (show the green icon with the plus sign). That would mean the only time there is not an icon will be when everything is a success and there is not an update available. Keep in mind that using this option means that no icon showing does not necessarily mean everything is fine. If the client fails miserably and terminates for some reason, or the scheduled task is no longer running, you will not get any indication that something is wrong until your guide is about to run out.

Also, I'll just go ahead and announce it here. I will release a new version soon primarily to address the garbage cleanup. I discovered today that part of the garbage cleanup includes kicking off the reindexing task when it completes. I'm going to prevent that from happening since I kick it off right after the import. With the current version the reindexing is happening at the same time the client is importing the updated MXF file.
- Gary
Keeping WMC alive beyond January 2020. http://epg123.garyan2.net

User avatar
IT Troll

Posts: 789
Joined: Sun Nov 27, 2011 9:42 am
Location: Edinburgh, UK

HTPC Specs: Show details

#6

Post by IT Troll » Thu Jul 02, 2020 5:11 am

Thanks, that sounds great.

Garbage collection is pretty swift now that it is happening regularly. Glad you are looking after the health of our databases. :thumbup:
Are you a Recorded TV HD user or want to give it a try? Check out the new community-made update; Recorded TV HD v2.1

User avatar
StinkyImp

Posts: 308
Joined: Thu May 11, 2017 7:53 pm
Location:

HTPC Specs: Show details

#7

Post by StinkyImp » Thu Jul 02, 2020 4:38 pm

IT Troll wrote:
Thu Jul 02, 2020 5:11 am
Garbage collection is pretty swift now that it is happening regularly.
INFORMATIONAL POST ONLY

I know this is purely anecdotal, but my Garbage collection process seems to be taking longer each time.
  • First run = 8 minutes
  • Second run = 11 minutes
  • Third run = 15 minutes

Code: Select all

EPG123 Log Parser (and Report Generator) - v 1.7.6 (64 bit)
Report Created on 07/02/2020 at 08:59:26
================================================================
     1 [6/22/2020 12:15:22 AM] Entering PerformGarbageCleanup().
     2 [6/22/2020 12:23:35 AM] Exiting PerformGarbageCleanup(). SUCCESS.
     3 [6/27/2020 12:15:11 AM] Entering PerformGarbageCleanup().
     4 [6/27/2020 12:26:11 AM] Exiting PerformGarbageCleanup(). SUCCESS.
     5 [7/2/2020 12:15:27 AM] Entering PerformGarbageCleanup().
     6 [7/2/2020 12:30:30 AM] Exiting PerformGarbageCleanup(). SUCCESS.

===== QUERY INFORMATION (Predefined) ===========================
Logs used:		trace.log ONLY
Search String:		PerformGarbageCleanup
Date Range:		06/15/2020 thru 07/02/2020 (18 days)
Total results found:	6
Query time:		03 seconds

===== GENERAL INFORMATION ======================================
Log Path:		C:\epg123\
Logfile timespan:	5/19/2020 thru 7/2/2020 (45 days)
Total lines processed:	3248
Gary -> Is this because of the additional reindexing task?

User avatar
garyan2

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

HTPC Specs: Show details

#8

Post by garyan2 » Thu Jul 02, 2020 5:14 pm

StinkyImp wrote:
Thu Jul 02, 2020 4:38 pm
Gary -> Is this because of the additional reindexing task?
No, at the end of the garbage collection (it actually does 2 garbage collections for some reason looking at the mcupdate code), it just kicks off the reindexing task before exiting. It doesn't wait for it to complete. At the beginning of the garbage collection it does try to download the maintenance package, but that won't account for the added time there. It also will no longer try to download the package with the next EPG123 release but again, no real impact.

So not sure why it is taking longer each run. I doubt, though possible, that there is simply more work to do. I believe the process priority is Normal, but if there is anything else going on that could slow it down. Is there anything in the Event Viewer to show other mcupdate tasks running?
- Gary
Keeping WMC alive beyond January 2020. http://epg123.garyan2.net

User avatar
StinkyImp

Posts: 308
Joined: Thu May 11, 2017 7:53 pm
Location:

HTPC Specs: Show details

#9

Post by StinkyImp » Thu Jul 02, 2020 6:02 pm

garyan2 wrote:
Thu Jul 02, 2020 5:14 pm
Is there anything in the Event Viewer to show other mcupdate tasks running?
I had disabled both the "mcupdate" tasks when I installed 1.3.8.10.

Following are event viewer entries for the three runs. The 6/27 errors were the result of a "failure to communicate with SD".

Gotta run...

Image

User avatar
garyan2

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

HTPC Specs: Show details

#10

Post by garyan2 » Thu Jul 02, 2020 6:08 pm

I would re-enable the "mcupdate" task. WMC uses that a lot for a lot of other things other than the guide. The "mcupdate_scheduled" task can probably be disabled... with downloads disabled in WMC and EPG123 doing the garbage collection, it won't run even if it is enabled. So really, my suggestion, is to go ahead and leave them both enabled.
- Gary
Keeping WMC alive beyond January 2020. http://epg123.garyan2.net

User avatar
IT Troll

Posts: 789
Joined: Sun Nov 27, 2011 9:42 am
Location: Edinburgh, UK

HTPC Specs: Show details

#11

Post by IT Troll » Thu Jul 02, 2020 9:31 pm

StinkyImp wrote:
Thu Jul 02, 2020 4:38 pm
I know this is purely anecdotal, but my Garbage collection process seems to be taking longer each time.
My first run was 16 mins (hadn’t been run for several months). Runs two and three under the new schedule were around 90 seconds each.
I don’t download many channels and my database is on my SSD, which I guess are factors.
Are you a Recorded TV HD user or want to give it a try? Check out the new community-made update; Recorded TV HD v2.1

jones4725

Posts: 3
Joined: Fri Jun 26, 2020 1:30 pm
Location:

HTPC Specs: Show details

#12

Post by jones4725 » Sat Jul 04, 2020 3:46 pm

IT Troll wrote:
Thu Jul 02, 2020 9:31 pm
StinkyImp wrote:
Thu Jul 02, 2020 4:38 pm
I know this is purely anecdotal, but my Garbage collection process seems to be taking longer each time.
My first run was 16 mins (hadn’t been run for several months). Runs two and three under the new schedule were around 90 seconds each.
I don’t download many channels and my database is on my SSD, which I guess are factors.
Hi there -- I had a very similar experience, also in the same boat where my GC process wasn't happening and I didn't even know until EPG123 couldn't import the guide listings. Once I got the latest version of EPG installed and the database rebuilt, my first time the EPG scheduled task ran it took almost 30 minutes for the GC process to complete when called. The last few days the whole EPG scheduled task has taken around 4 minutes total and things are working well!

User avatar
StinkyImp

Posts: 308
Joined: Thu May 11, 2017 7:53 pm
Location:

HTPC Specs: Show details

#13

Post by StinkyImp » Sat Jul 04, 2020 4:41 pm

jones4725 wrote:
Sat Jul 04, 2020 3:46 pm
...my first time the EPG scheduled task ran it took almost 30 minutes for the GC process to complete when called. The last few days the whole EPG scheduled task has taken around 4 minutes total and things are working well!
My daily task usually runs around 40 seconds or less except the days when GC runs. I'll be interested to see if this trend continues or if it levels off after awhile?

I re-enabled the mcupdate task but kept the "mcupdate_scheduled" task disabled.

Code: Select all

EPG123 Log Parser (and Report Generator) - v 1.7.6 (64 bit)
Report Created on 07/04/2020 at 09:28:27
================================================================
   [6/20/2020 12:16:06 AM] [ INFO] EPG123 client execution time was 00:00:39.0152315.
   [6/21/2020 12:16:03 AM] [ INFO] EPG123 client execution time was 00:00:37.0411186.
-> [6/22/2020 12:24:23 AM] [ INFO] EPG123 client execution time was 00:09:01.1875533.
   [6/23/2020 12:16:14 AM] [ INFO] EPG123 client execution time was 00:00:39.6422674.
   [6/24/2020 12:16:08 AM] [ INFO] EPG123 client execution time was 00:00:39.2282438.
   [6/25/2020 12:16:10 AM] [ INFO] EPG123 client execution time was 00:00:40.2903044.
   [6/26/2020 12:16:04 AM] [ INFO] EPG123 client execution time was 00:00:38.9202261.
-> [6/27/2020 12:26:59 AM] [ INFO] EPG123 client execution time was 00:11:47.9414919.
   [6/28/2020 12:16:12 AM] [ INFO] EPG123 client execution time was 00:00:39.4822583.
   [6/29/2020 12:15:57 AM] [ INFO] EPG123 client execution time was 00:00:34.3489646.
   [6/30/2020 12:16:05 AM] [ INFO] EPG123 client execution time was 00:00:37.0661200.
   [7/1/2020 12:16:12 AM] [ INFO] EPG123 client execution time was 00:00:39.0502335.
-> [7/2/2020 12:31:27 AM] [ INFO] EPG123 client execution time was 00:16:00.0829136.
   [7/3/2020 12:16:11 AM] [ INFO] EPG123 client execution time was 00:00:41.7913904.
   [7/4/2020 12:15:52 AM] [ INFO] EPG123 client execution time was 00:00:29.1396667.

===== QUERY INFORMATION (Predefined) ===========================
Logs used:		trace.log ONLY
Search String:		client execution time
Date Range:		06/20/2020 thru 07/04/2020 (15 days)
Total results found:	15
Query time:		02 seconds

===== GENERAL INFORMATION ======================================
Log Path:		C:\epg123\
Logfile timespan:	5/19/2020 thru 7/4/2020 (47 days)
Total lines processed:	3387

User avatar
garyan2

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

HTPC Specs: Show details

#14

Post by garyan2 » Sat Jul 04, 2020 4:46 pm

garyan2 wrote:
Thu Jul 02, 2020 6:08 pm
I would re-enable the "mcupdate" task. WMC uses that a lot for a lot of other things other than the guide. The "mcupdate_scheduled" task can probably be disabled... with downloads disabled in WMC and EPG123 doing the garbage collection, it won't run even if it is enabled. So really, my suggestion, is to go ahead and leave them both enabled.
I may revisit this concerning the "mcupdate" task. I'm going to monitor what the task actually does for us anymore and look further in the WMC code to see if it is needed anymore. I do see WMC will run the task every time you open it to download packages. Disabling might even get rid of the WMC tray icon.
jones4725 wrote:
Sat Jul 04, 2020 3:46 pm
Hi there -- I had a very similar experience, also in the same boat where my GC process wasn't happening and I didn't even know until EPG123 couldn't import the guide listings. Once I got the latest version of EPG installed and the database rebuilt, my first time the EPG scheduled task ran it took almost 30 minutes for the GC process to complete when called. The last few days the whole EPG scheduled task has taken around 4 minutes total and things are working well!
The GC will only run every 5 days, so if I'm reading correctly you haven't yet gotten to the 2nd run to see the difference yet. My experience is pretty much the same as IT Troll's as well. I only download 15 days on 29 stations, so my database is pretty small as well and takes a little under 2 minutes to complete.
- Gary
Keeping WMC alive beyond January 2020. http://epg123.garyan2.net

User avatar
garyan2

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

HTPC Specs: Show details

#15

Post by garyan2 » Sat Jul 04, 2020 4:49 pm

garyan2 wrote:
Thu Jul 02, 2020 4:59 am
Oh, fine. The code is written to add an option to only display Warning and Errors, but right now I'm debating whether to show if there is an update as well (show the green icon with the plus sign). That would mean the only time there is not an icon will be when everything is a success and there is not an update available. Keep in mind that using this option means that no icon showing does not necessarily mean everything is fine. If the client fails miserably and terminates for some reason, or the scheduled task is no longer running, you will not get any indication that something is wrong until your guide is about to run out.

Also, I'll just go ahead and announce it here. I will release a new version soon primarily to address the garbage cleanup. I discovered today that part of the garbage cleanup includes kicking off the reindexing task when it completes. I'm going to prevent that from happening since I kick it off right after the import. With the current version the reindexing is happening at the same time the client is importing the updated MXF file.
New version is now released with the option to not only show the warnings, errors, and update available logos.
- Gary
Keeping WMC alive beyond January 2020. http://epg123.garyan2.net

User avatar
IT Troll

Posts: 789
Joined: Sun Nov 27, 2011 9:42 am
Location: Edinburgh, UK

HTPC Specs: Show details

#16

Post by IT Troll » Sun Jul 05, 2020 8:59 am

garyan2 wrote:
Sat Jul 04, 2020 4:49 pm
New version is now released with the option to not only show the warnings, errors, and update available logos.
Thanks for that. Not so great news though. I closed Media Center, installed the new version, launched them, configured the status logos, launched Media Center, and then immediately had a database recovery event (first one in 2.5 years).

Code: Select all

[05/07/2020 08:57:09] ===============================================================================
[05/07/2020 08:57:09]  Activating the epg123 configuration GUI. version 1.3.8.20
[05/07/2020 08:57:09] ===============================================================================
[05/07/2020 08:57:10] [ INFO] Token request successful. serverID: 20141201.web.3
[05/07/2020 08:57:10] [ INFO] Status request successful. account expires: 2021-07-23T10:51:28Z , lineups: 1/4 , lastDataUpdate: 2020-07-05T04:28:58Z
[05/07/2020 08:57:10] [ INFO] system status: Online , message: No known issues.
[05/07/2020 08:57:10] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[05/07/2020 08:57:11] [ INFO] Successfully retrieved the station mapping for lineup GBR-1000029-DEFAULT.
[05/07/2020 08:57:11] [ INFO] Successfully queried the Task Scheduler for status. Ready. Last Run 05/07/2020 06:15:07; Exit: 0x00000000
[05/07/2020 08:57:32] ===============================================================================
[05/07/2020 08:57:32]  Activating the epg123 client GUI. version 1.3.8.20
[05/07/2020 08:57:32] ===============================================================================
[05/07/2020 08:57:32] [ INFO] Successfully queried the Task Scheduler for status. Ready. Last Run 05/07/2020 06:15:07; Exit: 0x00000000

Date:          05/07/2020 08:57:35
Event ID:      1
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      HTPC
Description:
Recovery of guide listings and recording schedule is complete.
Now I don't think this is as a direct result of the latest version, as I know Media Center bides it's time and waits until next launch to spring this on you. I think this was caused by the last maintenance event.

Code: Select all

Log Name:      Media Center
Source:        MCUpdate
Date:          03/07/2020 06:15:12
Event ID:      0
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      HTPC
Description:
06:15:12 - Testing Internet connection.
06:15:12 - Connection established.
06:15:12 - Processing of MCEClientMaintenance is complete.
06:15:12 - Update successful.
06:15:12 - Next update at 08/07/2020 05:34:51.

Log Name:      Media Center
Source:        MCUpdate
Date:          03/07/2020 06:15:13
Event ID:      0
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      HTPC
Description:
06:15:13 - Starting Client Maintenance.

Log Name:      Media Center
Source:        MCUpdate
Date:          03/07/2020 06:17:00
Event ID:      0
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      HTPC
Description:
06:17:00 - Client Maintenance has completed.
Hopefully the additional changes to maintenance made in v1.3.8.20 will prevent this happening again. My previous conclusion is this happens when EPG123 imports guide data after MCUpdate performs some kind of update.

Finally, the behaviour of the status logo configuration may confuse people. I found that the switching from None to enabled takes effect immediately. But the switch between light and dark, and warnings/errors only, is only actioned after a client run. I am guessing it has to run to assess what the state is and then switch the images as appropriate. So if you change the accent colour and check the warnings/errors box you still get the green icon of the wrong accent initially.
Are you a Recorded TV HD user or want to give it a try? Check out the new community-made update; Recorded TV HD v2.1

User avatar
StinkyImp

Posts: 308
Joined: Thu May 11, 2017 7:53 pm
Location:

HTPC Specs: Show details

#17

Post by StinkyImp » Sun Jul 12, 2020 1:54 pm

It looks like my garbage collection has settled down to around 10 minutes. The 16 minute run on July 2nd appears to be an anomaly.

Code: Select all

EPG123 Log Parser (and Report Generator) - v 1.7.6 (64 bit)
Report Created on 07/12/2020 at 06:18:00
================================================================
[6/22/2020 12:15:22 AM] Entering PerformGarbageCleanup().
[6/22/2020 12:23:35 AM] Exiting PerformGarbageCleanup(). SUCCESS.
[6/22/2020 12:24:23 AM] [ INFO] EPG123 client execution time was 00:09:01.1875533.

[6/27/2020 12:15:11 AM] Entering PerformGarbageCleanup().
[6/27/2020 12:26:11 AM] Exiting PerformGarbageCleanup(). SUCCESS.
[6/27/2020 12:26:59 AM] [ INFO] EPG123 client execution time was 00:11:47.9414919.

[7/2/2020 12:15:27 AM] Entering PerformGarbageCleanup().
[7/2/2020 12:30:30 AM] Exiting PerformGarbageCleanup(). SUCCESS.
[7/2/2020 12:31:27 AM] [ INFO] EPG123 client execution time was 00:16:00.0829136.

[7/7/2020 12:15:23 AM] Entering PerformGarbageCleanup().
[7/7/2020 12:25:23 AM] Exiting PerformGarbageCleanup(). SUCCESS.
[7/7/2020 12:25:47 AM] [ INFO] EPG123 client execution time was 00:10:23.7716777.

[7/12/2020 12:15:26 AM] Entering PerformGarbageCleanup().
[7/12/2020 12:25:14 AM] Exiting PerformGarbageCleanup(). SUCCESS.
[7/12/2020 12:25:41 AM] [ INFO] EPG123 client execution time was 00:10:15.1201828.

===== QUERY INFORMATION (Predefined) ===========================
Logs used:		trace.log ONLY
Search String:		PerformGarbageCleanup, client execution time
Date Range:		06/22/2020 thru 07/12/2020 (21 days)
Total results found:	15
Query time:		03 seconds

===== GENERAL INFORMATION ======================================
Log Path:		C:\epg123\
Logfile timespan:	5/19/2020 thru 7/12/2020 (55 days)
Total lines processed:	3938

User avatar
StinkyImp

Posts: 308
Joined: Thu May 11, 2017 7:53 pm
Location:

HTPC Specs: Show details

#18

Post by StinkyImp » Fri Aug 07, 2020 5:51 pm

UPDATE:

I know the "client execution time" includes other processes but it looks like my average time for PerformGarbageCleanup will be around 10 minutes (give or take) and everything is running as smooth as silk. That's awesome!

Thanks Gary! :clap:

Code: Select all

EPG123 Log Parser (and Report Generator) - v 1.7.6 (64 bit)
Report Created on 08/07/2020 at 10:29:26
================================================================
[6/22/2020 12:15:22 AM] Entering PerformGarbageCleanup().
[6/22/2020 12:23:35 AM] Exiting PerformGarbageCleanup(). SUCCESS.
[6/22/2020 12:24:23 AM] [ INFO] EPG123 client execution time was 00:09:01.1875533.

[6/27/2020 12:15:11 AM] Entering PerformGarbageCleanup().
[6/27/2020 12:26:11 AM] Exiting PerformGarbageCleanup(). SUCCESS.
[6/27/2020 12:26:59 AM] [ INFO] EPG123 client execution time was 00:11:47.9414919.

[7/2/2020 12:15:27 AM] Entering PerformGarbageCleanup().
[7/2/2020 12:30:30 AM] Exiting PerformGarbageCleanup(). SUCCESS.
[7/2/2020 12:31:27 AM] [ INFO] EPG123 client execution time was 00:16:00.0829136.

[7/7/2020 12:15:23 AM] Entering PerformGarbageCleanup().
[7/7/2020 12:25:23 AM] Exiting PerformGarbageCleanup(). SUCCESS.
[7/7/2020 12:25:47 AM] [ INFO] EPG123 client execution time was 00:10:23.7716777.

[7/12/2020 12:15:26 AM] Entering PerformGarbageCleanup().
[7/12/2020 12:25:14 AM] Exiting PerformGarbageCleanup(). SUCCESS.
[7/12/2020 12:25:41 AM] [ INFO] EPG123 client execution time was 00:10:15.1201828.

[7/17/2020 12:15:25 AM] Entering PerformGarbageCleanup().
[7/17/2020 12:25:15 AM] Exiting PerformGarbageCleanup(). SUCCESS.
[7/17/2020 12:25:39 AM] [ INFO] EPG123 client execution time was 00:10:14.8381667.

[7/22/2020 12:15:27 AM] Entering PerformGarbageCleanup().
[7/22/2020 12:24:17 AM] Exiting PerformGarbageCleanup(). SUCCESS.
[7/22/2020 12:24:40 AM] [ INFO] EPG123 client execution time was 00:09:12.9526270.

[7/27/2020 12:15:27 AM] Entering PerformGarbageCleanup().
[7/27/2020 12:24:31 AM] Exiting PerformGarbageCleanup(). SUCCESS.
[7/27/2020 12:24:54 AM] [ INFO] EPG123 client execution time was 00:09:27.2094425.

[8/2/2020 12:15:20 AM] Entering PerformGarbageCleanup().
[8/2/2020 12:22:30 AM] Exiting PerformGarbageCleanup(). SUCCESS.
[8/2/2020 12:22:58 AM] [ INFO] EPG123 client execution time was 00:07:37.5302955.

[8/7/2020 12:15:24 AM] Entering PerformGarbageCleanup().
[8/7/2020 12:26:11 AM] Exiting PerformGarbageCleanup(). SUCCESS.
[8/7/2020 12:26:36 AM] [ INFO] EPG123 client execution time was 00:11:11.9014306.

===== QUERY INFORMATION (Predefined) ===========================
Logs used:		trace.log ONLY
Search String:		PerformGarbageCleanup, client execution time
Date Range:		06/22/2020 thru 08/07/2020 (47 days)
Total results found:	30
Query time:		05 seconds

===== GENERAL INFORMATION ======================================
Log Path:		C:\epg123\
Logfile timespan:	5/19/2020 thru 8/7/2020 (81 days)
Total lines processed:	5493

===== SYSTEM INFORMATION =======================================
Operating System:	Windows 7 Professional (64 bit)
Processor:		Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz
Total RAM:		8.00 GB
ehshell version:	6.1.7601.23434
EPG123 version:		1.3.9.30
Last boot time:		July 18, 2020 - 10:46 AM
System Uptime:		19 Days 23 Hours 42 Minutes

Post Reply