V3.6.6 crashes on EPG update

[gb2011]

The dump looks like it crashed in the .NET xml parser classes. Are you able to supply the full xmltv file, so I can try it here? (put it on your dropbox)

here is the full xmltv file https://www.dropbox.com/s/i733nlyhltpdy2...g.xml?dl=0

[sub]

The beginning of the file is invalid, so NextPVR can't load it.

It has:

Code:

<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE tv SYSTEM "xmltv.dtd">

<?xml version='1.0' encoding='ISO-8859-1'?>
<tv generator-info-name="mc2xml" generator-info-url="mailto:mc2xml@gmail.com" source-info-name="Rovi">
    <channel id="I26.28460816.microsoft.com">
        <display-name>TV26</display-name>
        <display-name>26 TV26</display-name>
        <display-name>26</display-name>
        <display-name>WETA TV</display-name>
        <display-name>PBS</display-name>

That second <?xml version="1.0" encoding="ISO-8859-1"?> shouldn't be there. It also has an invalid character on the very last line of the file. Both of these need to be fixed before NextPVR would let you use that file. (it shouldn't crash, and I can't reproduce that here, but I get the feeling these would fix it for you)

[gb2011]

The beginning of the file is invalid, so NextPVR can't load it.

It has:

Code:

<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE tv SYSTEM "xmltv.dtd">

<?xml version='1.0' encoding='ISO-8859-1'?>
<tv generator-info-name="mc2xml" generator-info-url="mailto:mc2xml@gmail.com" source-info-name="Rovi">
    <channel id="I26.28460816.microsoft.com">
        <display-name>TV26</display-name>
        <display-name>26 TV26</display-name>
        <display-name>26</display-name>
        <display-name>WETA TV</display-name>
        <display-name>PBS</display-name>

That second <?xml version="1.0" encoding="ISO-8859-1"?> shouldn't be there. It also has an invalid character on the very last line of the file. Both of these need to be fixed before NextPVR would let you use that file. (it shouldn't crash, and I can't reproduce that here, but I get the feeling these would fix it for you)

Sorry about the bad xmltv file. I introduced the 2nd header trying to debug this problem. The character at the end of the file has been in my files for a long time while using V3.3.8.

Tried 2 different xmltv files. First one hand edit to remove dup header line and char at end of file, second one fixed my script to solve both issues. Both files result in the same crash as before.

Did I need to do any special besides running the installer to go from v3.3.8 to v3.6.6?

Here is the link to both new xmltv files in case you want to give it another try. https://www.dropbox.com/s/8xgh4cu7nf7rxn...2.zip?dl=0

[sub]

Did I need to do any special besides running the installer to go from v3.3.8 to v3.6.6?

No - you just run the installer. There is stacks of people using xmltv to, and no other reports of problems with this, so pretty sure it's either your xmltv file or something environmental about your machine (like antivirus or malware detection software interfering with things).;

Here is the link to both new xmltv files in case you want to give it another try. https://www.dropbox.com/s/8xgh4cu7nf7rxn...2.zip?dl=0

I'll try this file.

[sub]

I just tried these files and both are loading fine for me.

[gb2011]

I just tried these files and both are loading fine for me.

Thanks for looking into this.

I guess I will try to go back to V3.3.8, which has working well for me. Is there a way to do that besides uninstalling and reinstalling the old version?

[sub]

I've never tried a downgrade myself. It'd probably be an uninstall/reinstall. I wouldn't be surprised if you find you've got that same problem with 3.3.8 now though.

[gb2011]

Sub, you were at least half right it was an issue on my system. Thought you my might be interested in the final solution.

It appears by npvr.db3 got corrupted during the install of v3.6.6. Reinstalled V3.6.6 but still had the same crash. Then tried using an older database and that worked. Seems any database before the upgrade works. No idea what happened to the database during the upgrade. NPVR seemed to continue working after the upgrade. I was still able to watch and record shows.

Thanks for your support and all your efforts to maintain a great product.

[hyperactive]

Hey there.
I too had the same problem when I went to update the programming to account for daylight savings, which started this morning.
I restarted the recording service, then clicked on empty EPG, deleted and rescanned all the channels, then updated the EPG, and the whole thing came to a dead stop when it got to the bit where it said "updating recording schedule.". so I stopped all the services, deleted npvr.db3 and started from scratch.
Something must have become corrupted during the upgrade to 3.6.6 from the previous version
Drag to resize

[hyperactive]

Hey there.
I too had the same problem when I went to update the programming to account for daylight savings, which started this morning.
I restarted the recording service, then clicked on empty EPG, deleted and rescanned all the channels, then updated the EPG, and the whole thing came to a dead stop when it got to the bit where it said "updating recording schedule.". so I stopped all the services, deleted npvr.db3 and started from scratch.
Something must have become corrupted during the upgrade to 3.6.6 from the previous version