Unable to delete recording. File may be in use.

[seattlefog]

I'm attempting to migrate nextpvr v5 to a  windows 11 computer. The previous computer (Windows 10) was v5 also. It appears that program recordings kick off as scheduled. The recording listing indicates they've finished but the tray app indicates they're still recording (way) past the scheduled stop time. I've uninstalled nextpvr  and reinstalled. I've purchased the latest wintv version (to ensure newest drivers) from Hauppague. I've installed the latest LAV decoders. i'll attempt to upload the log files and the config.xml, which I've copied from the previous installation. I removed the SID values and set the 3 keys to ensure that existing recordings would not be lost in migration. Drive locations are the same. Existing recordings are found and playback OK.

[seattlefog]

adding current config.xml

[mvallevand]

Are you running a VPN or some Internet Security or a poorly configured firewal ? There are too many network errors for normal operation. For sure something is blocking the stop, the server itself even as the server itself is still working intermittently.

Code:

2025-03-31 16:59:36.061    [DEBUG][10]    http://localhost:50044/stream/stop?handle=1
2025-03-31 16:59:38.075    [ERROR][10]    System.Net.WebException: The operation has timed out.
   at System.Net.HttpWebRequest.GetResponse()
   at System.Net.WebClient.DownloadBits(WebRequest request, Stream writeStream)
   at System.Net.WebClient.DownloadDataInternal(Uri address, WebRequest& request)
   at System.Net.WebClient.DownloadString(Uri address)
   at NShared.LocalRecorder.StopStream(Int32 streamHandle)

Martin

[seattlefog]

I'm running BitDefender. I've granted the nextpvr server (and installer) .exe files full exclusion from BD. But I'll definitely give it a second and third look. Odd that BD on the previous computer seemed to not have issues.. as of a few days ago. thanks for an area to investigate.

[mvallevand]

It's not just the server exe, DeviceHostWindows and the NRecord dll need access. Check you other PC.

Martin

[seattlefog]

It looks like the request to cancel recording is timing out. Perhaps because something is being blocked, though BitDefender doesn't seem to post any messages regarding blocks. I've turned off MS and BD firewalls, and BD advanced threat protection as far as I can tell. I did notice that the timeout is 2 seconds. I went one stop further and took the URL for the cancel request, pasted it into a browser and watched the monitor in the tray. After a few seconds, the recording cancelled. I did this a couple of times and both manual re-issue of the web service request for cancel appeared to work when performed via browser.

Once recording is cancelled, there's no issue deleting the recording.

is there some particular recipient of the cancel request that I can specifically un-block... or a web service timeout that can be altered? it sure seems like 2 seconds for a local request ought to be enough, but maybe not. I'd like to try looking at the previous computer but it was utilized for parts for the replacement build. Thanks for any additional thoughts you might have.

Here's the URL from the log I used to cancel the recording.
2025-03-31 19:54:28.556 [DEBUG][10] Started recording (570454:2:R:\RecordedTV\Jeopardy!\Jeopardy!.S41E146.ts)
2025-03-31 19:54:28.563 [DEBUG][10] No C:\Users\Public\NPVR-data\scripts\ParallelProcessing.bat
2025-03-31 19:54:28.877 [DEBUG][10] Active...staying awake
2025-03-31 19:54:30.599 [DEBUG][37] <?xml version="1.0" encoding="utf-8" ?>
<rsp stat="ok">
<Status>
<Device oid="20" identifier="Hauppauge WinTV 885 ATSC Tuner/Demod (ATSC)">
<Recording handle="140002">R:\RecordedTV\Jeopardy!\Jeopardy!.S41E146.ts</Recording>
</Device>
<Device oid="22" identifier="Hauppauge WinTV 885 ATSC Tuner/Demod (ATSC) (#2)"> </Device>
<Device oid="24" identifier="Hauppauge WinTV 885 ATSC Tuner/Demod 2 (ATSC)"> </Device>
<Device oid="26" identifier="Hauppauge WinTV 885 ATSC Tuner/Demod 2 (ATSC) (#2)"> </Device>
</Status>
</rsp>

2025-03-31 19:54:55.037 [DEBUG][37] CancelRecording(570454)
2025-03-31 19:54:55.037 [DEBUG][37] queueing (570454) for cancellation
2025-03-31 19:54:55.867 [DEBUG][10] recording service dequeued request to cancel (570454)
**** used the following URL to cancel the recording later ***
2025-03-31 19:54:55.874 [DEBUG][10] http://localhost:50951/stream/stop?handle=2
2025-03-31 19:54:57.879 [ERROR][10] System.Net.WebException: The operation has timed out.
at System.Net.HttpWebRequest.GetResponse()
at System.Net.WebClient.GetWebResponse(WebRequest request)
at System.Net.WebClient.DownloadBits(WebRequest request, Stream writeStream)
at System.Net.WebClient.DownloadDataInternal(Uri address, WebRequest& request)
at System.Net.WebClient.DownloadString(Uri address)
at NShared.LocalRecorder.StopStream(Int32 streamHandle)
2025-03-31 19:54:57.880 [DEBUG][10] StoreMetaData@exit
2025-03-31 19:54:57.880 [DEBUG][10] No C:\Users\Public\NPVR-data\scripts\PostCancel.bat
2025-03-31 19:55:01.192 [DEBUG][10] No longer active

[mvallevand]

I'd need to see the fully logs there were many more examples, Schedules Direct not working, not being able to contact HDHRs, not being able to contact nextpvr.com

I did explain the some http requests were making it thorough,, and it wasn't really timing, maybe routing errors so 2 second wasn't enough.

Specifically you are getting a stale DNS for Schedules Direct that hasn't been used for months so DNS cachng is broken.

Martin

[seattlefog]

On April 1 I took the following actions:
Uninstalled Bitdefender
Turned off Windows firewalls
flushed dns
rebooted router
rebooted PC multiple times during this process.
Nothing would stop a recording once started. The webservice continued to time out at 2 seconds. The http request to cancel recording, entered via Edge would stop the recording.
My final actions were SFC to ensure Windows 11 integrity,  another run of nextpvr setup, and a reboot at about 6:45PM.
I let nextpvr start recording programs per schedule, saw that they did not stop, and captured the log files, which I will attempt to attach.
Do you see anything in these logs that indicate a network or other error AFTER 6:45PM? Other than the cancel recording web service timeout failure. There will be plenty of "stuff" prior to 6:45 I'm sure given all the things I tried. Thank you for your time on this issue. Any clues or things to try would be appreciated. I've spent probably over 30 hours and I'm running out of ideas.

[mvallevand]

The network is improved, it can see SD and nextpvr.com when it phones home but the connection the to Hauppauge tuner via the BDA driver is still screwed up.

If you turn off keep the device primed does that help?

Martin

[seattlefog]

I unchecked "keep digital tuners primed", and rebooted. It didn't appear to make a difference.