PvrScheduleTask Takes Extremely Long To Complete

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
DPitts18

Posts: 25
Joined: Sat Jun 29, 2019 8:25 pm
Location:

HTPC Specs: Show details

PvrScheduleTask Takes Extremely Long To Complete

#1

Post by DPitts18 » Sun Oct 13, 2019 2:02 pm

Gary, I'm not sure if you can help me with this, but any clues or ideas how to fix it would be appreciated.

I'm not sure when the problem started, but I noticed it recently, whenever I run a guide update with EPG123 everything seems to run correctly and the trace log says everything completed successfully, however no recordings start anytime soon. When I checked for a possible cause in the task scheduler I noticed that PvrScheduleTask and ReindexSearchRoot were still running and apparently recordings won't start until they complete or at least PvrScheduleTask completes, the problem is as an example last night, that took almost 6 hours. I just looked at the history on PvrScheduleTask and I knew it was taking longer than it should, but it looks like it is taking around 6 hours to complete every time. I had been scheduling it to run the guide update around 3AM, but I noticed some recording weren't being made and others were starting late, so I decided to investigate. Please help if you can.

User avatar
garyan2

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

HTPC Specs: Show details

#2

Post by garyan2 » Sun Oct 13, 2019 3:10 pm

Sounds like it could be your index database could be a problem with both tasks taking that long. Go to Control Panel -> Indexing Options. Make sure 'Windows Media Center' is listed in the 'Included Locations' and click the [Advanced] button. On the new windows, click the [Rebuild] button.

That may run as well, but see if that makes a difference.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

DPitts18

Posts: 25
Joined: Sat Jun 29, 2019 8:25 pm
Location:

HTPC Specs: Show details

#3

Post by DPitts18 » Sun Oct 13, 2019 3:20 pm

Okay, media center was included and I clicked rebuild. I know that will take awhile. Should I just wait until tomorrow to try to run the guide update again and see if it made a difference?

User avatar
garyan2

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

HTPC Specs: Show details

#4

Post by garyan2 » Sun Oct 13, 2019 3:55 pm

You could probably try it right away. If it works, great. If not, I wouldn't throw in the towel on this until the Indexing Options window says "Indexing complete."
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

DPitts18

Posts: 25
Joined: Sat Jun 29, 2019 8:25 pm
Location:

HTPC Specs: Show details

#5

Post by DPitts18 » Sun Oct 13, 2019 4:06 pm

I am hesitant to try and run it now, because if I still have the problem it will basically make media center unusable for 6 hours until it completes. I think I am going to run it overnight tonight and then see if it made a difference. I will write back in the morning and let you know the results. Thanks again for your help.

DPitts18

Posts: 25
Joined: Sat Jun 29, 2019 8:25 pm
Location:

HTPC Specs: Show details

#6

Post by DPitts18 » Mon Oct 14, 2019 12:23 pm

I ran the guide update overnight with the same result. The index should end sometime today and I will run the guide update again after it's done and let you know the results. Is there anything else you might suspect I can test while I'm waiting?

User avatar
garyan2

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

HTPC Specs: Show details

#7

Post by garyan2 » Mon Oct 14, 2019 3:37 pm

How big is your database? Have you disabled any mcupdate tasks? I'm wondering if garbage collector has not been run in a long time.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

DPitts18

Posts: 25
Joined: Sat Jun 29, 2019 8:25 pm
Location:

HTPC Specs: Show details

#8

Post by DPitts18 » Mon Oct 14, 2019 8:46 pm

After further looking it's not exactly the same result. PvrScheduleTask has yet to stop running since it started around 3AM, I am assuming it's still running because the index is still indexing files. So no recordings are happening, that may imply that the indexing is the problem as to why the task is taking so long to complete and causing the original problem.

DPitts18

Posts: 25
Joined: Sat Jun 29, 2019 8:25 pm
Location:

HTPC Specs: Show details

#9

Post by DPitts18 » Mon Oct 14, 2019 8:53 pm

garyan2 wrote: Mon Oct 14, 2019 3:37 pm How big is your database? Have you disabled any mcupdate tasks? I'm wondering if garbage collector has not been run in a long time.
The MCEPG database file is 1.15GB. MCUPDATE is enabled and runs as usual. What would be garbage collector that would need to be run?

User avatar
garyan2

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

HTPC Specs: Show details

#10

Post by garyan2 » Tue Oct 15, 2019 7:25 am

That seems quite large. I can't remember off hand my recommended command line to force a database garbage cleanup, but look for dbgc in the forums by me. (Sorry, I'm on travel at the moment or I would search myself).

This step can take really really long time. You might want to consider using the database rebuild feature.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

User avatar
garyan2

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

HTPC Specs: Show details

#11

Post by garyan2 » Tue Oct 15, 2019 11:19 am

Take a look at this post for the command line... viewtopic.php?p=131568#p131568

EDIT: corrected link
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

DPitts18

Posts: 25
Joined: Sat Jun 29, 2019 8:25 pm
Location:

HTPC Specs: Show details

#12

Post by DPitts18 » Tue Oct 15, 2019 12:23 pm

I am running the "dbgc" command now.

Last night after the re-indexing finished the PvrSchedule finished and recordings started again, however after EPG ran again over night the PvrSchedule task is still running as of 4:50AM and it's now 8:20AM.

DPitts18

Posts: 25
Joined: Sat Jun 29, 2019 8:25 pm
Location:

HTPC Specs: Show details

#13

Post by DPitts18 » Tue Oct 15, 2019 12:25 pm

Also, how do I know dbgc is doing anything in the command prompt, should it be giving any feedback?

User avatar
garyan2

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

HTPC Specs: Show details

#14

Post by garyan2 » Tue Oct 15, 2019 1:58 pm

No feedback. That is why I added the START /WAIT. When it goes back to the prompt, it is done.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

DPitts18

Posts: 25
Joined: Sat Jun 29, 2019 8:25 pm
Location:

HTPC Specs: Show details

#15

Post by DPitts18 » Tue Oct 15, 2019 9:47 pm

How long should it take to run? Nothing has changed on the command prompt since I started it this morning.

DPitts18

Posts: 25
Joined: Sat Jun 29, 2019 8:25 pm
Location:

HTPC Specs: Show details

#16

Post by DPitts18 » Tue Oct 15, 2019 9:57 pm

Its weird because the "PvrScheduleTask" is taking longer than ever now. It started running at 4:50AM and didn't end until this afternoon at 3:58PM. The entire time the "PvrScheduleTask" is running Media Center will not record anything. It's so frustrating.

DPitts18

Posts: 25
Joined: Sat Jun 29, 2019 8:25 pm
Location:

HTPC Specs: Show details

#17

Post by DPitts18 » Tue Oct 15, 2019 11:08 pm

Okay the "Windows Media Center Store Update Manager" crashed, so I'm going to try and run the prompt again. I saw in some of the posts that some people had to run it 2 or 3 times to get it to complete.

DPitts18

Posts: 25
Joined: Sat Jun 29, 2019 8:25 pm
Location:

HTPC Specs: Show details

#18

Post by DPitts18 » Sat Oct 19, 2019 1:13 pm

I reran the DBGC command and the second time it ran successfully. I've been testing the time to process the EPG123 file the last few days and the time has greatly improved, it seems to be around 2 hours now, when it used to take around 6. I know beggars can't be choosers, but is that a decent time or is there anyway I can improve that?

User avatar
garyan2

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

HTPC Specs: Show details

#19

Post by garyan2 » Sat Oct 19, 2019 3:56 pm

That depends on when your clock stops. Depending on the speed of the hard drive and the size of the MXF file, I've seen the import take 20 minutes. The ReindexSearchRoot indexing can take quite some time as well, but the PvrScheduleTask should be quick.

I think the big thing, though is that your WMC should be fully functional during the indexing (assuming it has already indexed previously).
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

DPitts18

Posts: 25
Joined: Sat Jun 29, 2019 8:25 pm
Location:

HTPC Specs: Show details

#20

Post by DPitts18 » Sun Oct 20, 2019 2:25 pm

I am having the opposite, the ReindexSearchRoot is taking less time, it is taking between 5-30 minutes to complete and the PvrScheduleTask is taking around 2 hours. I'm not really complaining, you have helped a ton, to go from 6 hours to 2 is a huge improvement.

Post Reply