2.5.5 - "The path is not of a legal form" exception

[nia]

Hi.

Thanks for a comprehensive update.

This is what I did:

• I installed the new version
  
• Install NMTInstall2 (deselected the npvr install option)
  
• Restart PC
  
• Enter Recordings
  
• Left to Ready Recordings
  
• Left ... error thrown (should be Conflicts)
  
• Doesn't work on the PCH-A100 either
  
• If I try to approach the Conflicts screen by scrolling Right, an error is thrown on the PC, on the PCH, I can see it, but it crashes the NMT app and exits.
  

The error is reproduceable after having restarted the PC.

I have been in the config screen and saved - no difference. One note is, that in the Config screen I was asked to add an alias to my recording directory when I was in there. I guess it's part of the multiple recording directory feature.

Please note, that my recording directory is \\tower\pvr. That recording directory is still functioning.

Unrelated: It appears that it is MUCH faster when i enter the Recordings that before. Don't know why, but I like it

Logs and config.xml attached. Also copy of the Exception window content.

[sub]

You might need to zip and attach your npvr.db3 file, so I can try running it here.

[nia]

Here goes - it's quite large and probably needs a good cleanout... :o

It has quite a lot of old deleted recordings and some stuff from when I was recording to a different directory. Some of those files are still there - just moved to the server drive.

[nia]

Any news on this. A side effect is that the Recordings are not sorted, so I'm currently accessing recordings through the "Videos" page.

I see the npvr.db3 is not attached to my previous post. Did the attachment never stick to the post after upload, or did You remove it due to it's size?

[sub]

Your npvr.db3 never showed up. Have another go attaching it.

[nia]

Ok - this time it's 7zipped. That's 1/3rd of the ZIP size. Renamed to ZIP to manage size restrictions, but it really is .7z.

Maybe it was rejected due to size last time, and I just didn't notice.

This is a zip of todays DB3. I also upgraded to the latest patch level - no difference in behaviour.

[sub]

Do you have these default settings in your config.xml, or have you changed them to 'false'

<AutoRemoveMissingRecordings>true</AutoRemoveMissingRecordings>
<CheckForRenamedRecordings>true</CheckForRenamedRecordings>

[nia]

They are both true. config attached.

[sub]

Give this patch a go. It should fix it.

The problem seems to have stemed from some of your recordings having no filename. I've not seen any other cases of this.

[johnsonx42]

The problem seems to have stemed from some of your recordings having no filename. I've not seen any other cases of this.

Remember that there was a bug that would wipe-out the filename if a recording was updated in-progress. I don't know when the bug was introduced but you fixed it during the 2.5 pre-release testing.