Upgrade issue - The path is not a legal form

[seattlefog]

Additional information. I did the initial transition from V4 to V5 in Feb 2021. It appears I downloaded and ran setup.exe in August of 2021 to update to the latest version of V5. So I think the previous update of v5 went just fine. Hope that helps provide a clue.

[mvallevand]

I can duplicate this.

Code:

NextPVRServer.exe
Unhandled exception. System.ArgumentException: The path is empty. (Parameter 'path')
   at System.IO.Path.GetFullPath(String path)
   at System.IO.DirectoryInfo..ctor(String path)
   at NUtility.SettingsHelper..ctor()
   at NUtility.SettingsHelper.GetInstance()
   at NUtility.Logger.SetLogFileName(String name, Boolean ignoreSettings)
   at NPVR5.Program.Main(String[] args)

Do you have a C:\Users\Public\Documents folder? If not create it and see if that makes a difference.

Martin

[seattlefog]

Creating a Documents folder seems to have worked. That permitted the upgrade / installation to run through. I performed a quick record and a few other misc tasks. Everything seems to be working. There are some odd UI behaviors. If I do a sort, the "sorting a-z" pop-up does not go away until I click on something else. Also the top "menu bar"(?) isn't always visible. I may have altered another folder during trouble shooting. I'm not worried at this point and consider the update issue resolve. Thank you very much for all your help.

[mvallevand]

Thanks to SysInternals for ProcMon since it showed me that NextPVR was accessing that folder before NPVR-Data

Martin

[sub]

Good spotting.

It asks Windows for the common documents directory (which is normally in c:\users\public\documents), to help it work out the location of c:\users\public. I haven't come across a Windows machine that didn't have this default directory. I guess he manually deleted it at some point?

In the early days of v5 it was hard coded c:\users\public, but this logic was added to handle users where this wasn't on the C:\ drive etc.

[seattlefog]

I don't recall doing it but probably "moved" it, merging contents into my current documents folder. I ran procmon on the launch of nextpvr after the failed installation and couldn't spot the callout. Great spot indeed!