[Failed: Recording service not running at recording time]

[Jaggy]

From what I have observed on a couple of new installs the default now it "Automatic (Delayed Start)" the problem with this can be if it tries to do anything before the 'delay' has completed which for Microsoft seem to be quite a long time these days. Of course you can see if it has started with the tray icon as it turns green or red after the service has started.

[mvallevand]

Right you are I checked the script in the program folder and indeed it is

sc create "NextPVR Service" binpath= "%installpath%NextPVRService.exe" start= delayed-auto

I got my automatics mixed up, I actually thought it was automatic and faster I guess my PC is what is fast now.

Martin

[Poocher]

OK I had a failure again Argh.
I am attaching the log. However the failure was on Sept 25. Survivor - 09/25/2024 - 19:00 to 20:29

I am not sure why this one failed?

There were successful recordings on 09/24/2024

[mvallevand]

Windows sleep/wake is not configured properly on you machine. As admin run this powercfg /waketimers and you should see what NextPVR has set in the future

This line shows NextPVR setting the sleep timer:

2024-09-25 14:32:52.616 [DEBUG][10] Requesting wake up for 'RecordingOID1044' [Survivor] at 9/25/2024 6:59 PM

but you can see them but it didn't wake the PC, too bad.

2024-09-25 18:49:42.361 [DEBUG][47] OnSleep...
2024-09-25 22:01:33.810 [DEBUG][10] Marking recording (1044) as 'Recording service not running at recording time'

Given that you put it to sleep close to wake up time (10 min) you might need to look at the hidden sleep settings for "System unattended sleep timeout"

Martin

[Poocher]

Thank you Martin!

I found an article on how to unhide this setting in Windows 10. It states to run the following from an elevated command prompt. It looks like it will set the parameter to 2 minutes. Is this appropriate?

REG ADD HKLM\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\238C9FA8-0AAD-41ED-83F4-97BE242C8F20\7bc4a2f9-d8fc-4469-b07b-33eb785aaca0 /v Attributes /t REG_DWORD /d 2 /f

[Poocher]

OK I ran a script to enable the view of the option in the power plan settings.

From an elevated command prompt
powercfg -attributes SUB_SLEEP 7bc4a2f9-d8fc-4469-b07b-33eb785aaca0 -ATTRIB_HIDE

I did a bit of research and set this value to 30 minutes from the default of 2 minutes.

I think you may have found the smoking gun Martin. Thank you so much!!!

I will see if everything records as expected this week. Crossing my fingers.

[Poocher]

OK this appears to have resolved the issue. My Wednesday recording is the one the typically fails. It was successful.

Thanks for all the help isolating the root cause Martin!

[Poocher]

That is interesting Martin. I did not change this setting to the best of my knowledge.