[sub3]

My theory is that there is some character or similar that is breaking the xml encoding used for shipping recording lists to kodi. If you can supply your npvr.db3 file, I'll can try it here in the debugger, to confirm recording list is sent, and what might be invalid about it.

 Try this file.

https://www.dropbox.com/s/qmxc7szmu6t5yxx/npvr.db3?dl=0

Please let me know when you have it, so that I can move it. 

Annoyingly it didn't tell me much more - the recordings actually loaded up fine here.

You'll probably need to supply the NextPVR logs, so we can check for errors there.

[Karellen]

ok, thanks sub3

[mcelliott]

My theory is that there is some character or similar that is breaking the xml encoding used for shipping recording lists to kodi. If you can supply your npvr.db3 file, I'll can try it here in the debugger, to confirm recording list is sent, and what might be invalid about it.

 Try this file.

https://www.dropbox.com/s/qmxc7szmu6t5yxx/npvr.db3?dl=0

Please let me know when you have it, so that I can move it. 

Annoyingly it didn't tell me much more - the recordings actually loaded up fine here.

You'll probably need to supply the NextPVR logs, so we can check for errors there.

I already supplied debug logs, a few posts up.

Regards,

Mark

[sub3]

NextPVR logs - not Kodi logs.

[mcelliott]

NextPVR logs - not Kodi logs.

Ah, sorry. It’s all gone now.

[sitush]

I've not wiped my database or even opened my logs, so presumably they are intact for both Kodi and NPVR. I could supply those if it would help, although I can't remember the precise date the problem surfaced ("some time mid-week" is the best I can do). I can't switch to MediaPortal because I'm running NPVR as a backend and actually viewing it's output through Kodi on an Ubuntu client

[emveepee]

I've not wiped my database or even opened my logs, so presumably they are intact for both Kodi and NPVR. I could supply those if it would help, although I can't remember the precise date the problem surfaced ("some time mid-week" is the best I can do). I can't switch to MediaPortal because I'm running NPVR as a backend and actually viewing it's output through Kodi on an Ubuntu client

 mcelliot's problem is actually due to two issues https://forums.nextpvr.com/showthread.ph...post529146 as well https://forums.nextpvr.com/showthread.ph...post529278  This patch should fix it https://forums.nextpvr.com/showthread.ph...post529964

Since you had a problem related to one of those earlier https://forums.nextpvr.com/showthread.ph...post523932 perhaps you never made the required fix and applying the patch should fix it for you too.

Martin

[sitush]

Thanks, I didn't know of that patch. I'll set a restore point and try it.

[sitush]

Downloaded the patch. Set a restore point. Copied the current NShare.dll to somewhere safe and pasted the new version from the extracted patch. Rebooted. Timer rules still show as empty using Kodi both on the NPVR backend PC and the Ubuntu client.

Drat.

[emveepee]

Downloaded the patch. Set a restore point. Copied the current NShare.dll to somewhere safe and pasted the new version from the extracted patch. Rebooted. Timer rules still show as empty using Kodi both on the NPVR backend PC and the Ubuntu client.

Drat.

So logs will be required.

Martin

[sitush]

Do I attach the NPVR logs here? There are loads of them, so using the paste thing seems messy.

[sitush]

NPVR logs at https://drive.google.com/file/d/1aU0o8q1...sp=sharing

[emveepee]

NPVR logs at https://drive.google.com/file/d/1aU0o8q1...sp=sharing

 There definitely is bad data in your recurring recording database so you will need to upload your database to the cloud too.

Martin

[sitush]

Thanks for looking into it. The database is now at https://drive.google.com/file/d/1X1y3Arb...sp=sharing

I'd take a stab and say it is something to do with the "America's Greatest Fibs" entry, partly because of the timing of what happened and partly because someone else mentioned it above. I seem to recall that the last time the database was corrupted it was because of an unhandled punctuation issue in the program title - but I'm getting old and my memory isn't what it was.

[emveepee]

Thanks for looking into it. The database is now at https://drive.google.com/file/d/1X1y3Arb...sp=sharing

I'd take a stab and say it is something to do with the "America's Greatest Fibs" entry, partly because of the timing of what happened and partly because someone else mentioned it above. I seem to recall that the last time the database was corrupted it was because of an unhandled punctuation issue in the program title - but I'm getting old and my memory isn't what it was.

 Yes it is America's Biggest Fibs causing the problem but that is because the EPG data has 01x19 and not ' in America.  Sub will need to fix this at the backend.

Martin