Record Error: Root element is missing.
|
2021-02-11, 12:21 AM
(2021-02-10, 05:35 PM)Graham Wrote:(2021-02-10, 04:29 PM)mvallevand Wrote: Do you have keep digital tuners primed on? If not maybe turn that on I did not. I do now. I also moved the 4 ATSC tuners to the top of the list and disabled all others. screen shot attached. Thank you for the linked information. I didn't spot what "primed" did. Perhaps I just read too fast?
2021-02-12, 06:04 PM
The root element is missing message occurred again last night. I believe it occurred while watching a previously recorded program from the default recording drive. This is the 3rd time that the error has occurred and I believe they all first occur while watching a recorded program. I speculate that there is some sort of delay in loading an xml channel file, caused by the simultaneous viewing and recording activity, and it "times out". This results in a corrupted element for that particular channel which can only be cleared by a reboot. If there's a time value I could alter to test this theory I'd be happy to oblige. Latest log files attached.
2021-02-12, 07:06 PM
(This post was last modified: 2021-02-12, 07:06 PM by mvallevand.)
Same error after a delay even primed, seems like a driver error, but I haven't seen that message before. What OS are you running?
2021-02-11 15:57:00.043 [ERROR][4] Failed to create IATSCLocator 2021-02-11 15:57:00.057 [ERROR][4] Unexpected error: System.Runtime.InteropServices.SEHException (0x80004005): External component has thrown an exception. at Native.DigitalRecorderBase.StartStream(String target, Int32 serviceID) at DeviceHostWindows.Devices.DigitalDevice.StartStream(String tuning, String target, String& reason) Martin
2021-02-12, 08:44 PM
(2021-02-12, 07:06 PM)mvallevand Wrote: Same error after a delay even primed, seems like a driver error, but I haven't seen that message before. What OS are you running?I'm running Windows 10 Pro 64 bit on 20H2 with latest updates applied. It's interesting that the error your reference occurred at 15:57 but the recording failed at about 21:00. From what I can see that channel wasn't used to record anything from 15:57 until approx 21:00.
2021-02-12, 08:45 PM
(This post was last modified: 2021-02-12, 08:46 PM by mvallevand.)
There were many failures following that first IATSCLocator message the tuner was useless after it occurred.
Martin
2021-02-16, 07:25 PM
npvrTray crashed about midnight. Is there a common element between the recording service and the tray application that I should examine more closely? Logs and Windows Application Event log entries attached.
2021-02-17, 06:03 PM
Another failure yesterday evening. The npvrtray application appeared... odd. I've included a screen shot in with the zipped log files in case it provides a clue. So far, recordings fail about every 36 hours, give or take.
2021-02-17, 06:21 PM
(This post was last modified: 2021-02-17, 06:22 PM by mvallevand.)
Since it's a driver error what do you want NextPVR to do? It is trying all four tuners.
2021-02-16 19:57:01.145 [ERROR][9] Failed to create IATSCLocator 2021-02-16 19:57:01.152 [ERROR][9] Unexpected error: System.Runtime.InteropServices.SEHException (0x80004005): External component has thrown an exception. Martin
2021-02-17, 06:29 PM
You've stated it looked like a driver error previously but haven't elaborated on what driver you believe to be at fault, or suggestions on how to address it. Do you, for example, believe it to be the Hauppauge driver that should be uninstalled and reinstalled or...?
2021-02-17, 06:41 PM
Sorry I thought it was obvious that I meant the tuner drivers since the tuners are failing.
Martin |
|
|
