Solved Launcher error accessing theatre.lst
-
Hello.
I uninstalled then re-installed 4.37 to move it to a new NVMe drive. I copied off the auto keyfile and the pilot files then put them back after updating to 4.37.3. When launching I get this error:[09/11/2023 08:43:15] [INFO] :: Application Initialization starting. [09/11/2023 08:43:15] [INFO] :: Post_OnInitialized. [09/11/2023 08:43:15] [INFO] :: FalconBMS Launcher v2.4.1.5 [09/11/2023 08:43:15] [INFO] :: Start Reading Launcher Settings. [09/11/2023 08:43:15] [INFO] :: Finished Reading Launcher Settings. [09/11/2023 08:43:15] [INFO] :: Start Reading Registry. [09/11/2023 08:43:15] [INFO] :: Finished Reading Registry. [09/11/2023 08:43:15] [INFO] :: Start Init Devices. [09/11/2023 08:43:16] [EXCEPTION] Access to the path 'D:\Falcon BMS 4.37\Data\Terrdata\TheaterDefinition\theater.lst' is denied.::
Source: mscorlib Target Site: Void WinIOError(Int32, System.String) **Message: Access to the path 'D:\Falcon BMS 4.37\Data\Terrdata\TheaterDefinition\theater.lst' is denied.** Details: Exception Data: System.Collections.ListDictionaryInternal Stack Trace: at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.File.SetAttributes(String path, FileAttributes fileAttributes) at FalconBMS.Launcher.TheaterList.PopulateAndSave(AppRegInfo appReg, ComboBox Combo) in C:\git\arithex\AltLauncher_develop\FalconBMS-Alternative-Launcher\Falcon BMS Alternative Launcher\TheaterList.cs:line 24 at FalconBMS.Launcher.Windows.MainWindow.ReloadKeyfilesTheatersAndUpdateUI() in C:\git\arithex\AltLauncher_develop\FalconBMS-Alternative-Launcher\Falcon BMS Alternative Launcher\Windows\MainWindow.xaml.cs:line 248 ============ [09/11/2023 08:43:16] [INFO] :: Completed RSS fetch on background-thread. [09/11/2023 08:43:16] [INFO] :: RSS update finished. [09/11/2023 08:43:47] [INFO] :: Finished Init Devices. [09/11/2023 08:43:47] [INFO] :: Start VR Check. [09/11/2023 08:43:47] [INFO] :: Finished VR Check. [09/11/2023 08:43:47] [INFO] :: Start Timers. [09/11/2023 08:43:47] [INFO] :: Timers Started. [09/11/2023 08:43:47] [INFO] :: Post_OnInitialized complete. [09/11/2023 08:43:47] [INFO] :: Process exiting - closing logfile.
I can access the file in question when looking at the files so I don’t know what is preventing access.
-
@open-flankler said in Launcher error accessing theatre.lst:
Stack Trace: at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.File.SetAttributes(String path, FileAttributes fileAttributes)It is failing trying to clear the readonly attribute on that file. Not sure why this could be happening, either.
Some commands you can run, if you want to investigate further… output should look like this:
D:\>attrib "\Falcon BMS 4.37\Data\Terrdata\TheaterDefinition\theater.lst" A D:\Falcon BMS 4.37\Data\Terrdata\TheaterDefinition\Theater.lst D:\>icacls "\Falcon BMS 4.37\Data\Terrdata\TheaterDefinition\theater.lst" \Falcon BMS 4.37\Data\Terrdata\TheaterDefinition\theater.lst BUILTIN\Administrators:(I)(F) NT AUTHORITY\SYSTEM:(I)(F) BUILTIN\Users:(I)(RX) NT AUTHORITY\Authenticated Users:(I)(M)
-
@airtex2019 thank you for your reply.
When I run the commands:
D:>attrib “\Falcon BMS 4.37\Data\Terrdata\TheaterDefinition\theater.lst”
A D:\Falcon BMS 4.37\Data\Terrdata\TheaterDefinition\Theater.lstD:>icacls “\Falcon BMS 4.37\Data\Terrdata\TheaterDefinition\theater.lst”
\Falcon BMS 4.37\Data\Terrdata\TheaterDefinition\theater.lst BUILTIN\Administrators:(I)(F)
NT AUTHORITY\SYSTEM:(I)(F)
BUILTIN\Users:(I)(RX)Successfully processed 1 files; Failed processing 0 files
Interesting is that “NT AUTHORITY\Authenticated Users:(I)(M)” is missing.
-
@airtex2019 I seem to have fixed it with your help.
The user permissions weren’t set up correctly for some reason. I applied a few changes and now it launches.
Thanks
-
-
@open-flankler the way this typically works, the permissions “inherit” from their parents all the way up to the root of the drive
it’s a persistent problem with Windows and secondary drives – it greatly depends on where that drive came from … another computer … or leftover from a previous Windows install … or newly formatted, etc
anyway, pay attention to permissions on the root D:\ folder and the top-level folders for any other games or other stuff you have on that drive
try to make it match what’s on C:\ …
(but if you see stuff about “Mandatory High Label” don’t worry too much about that … that’s just something to help protect the root OS drive)