Log4OM, version 2.34.0.0 (was happening with previous versions), on Windows 10, only logger/no CAT
After gracefully closing (shutting) down the running instance, the very next attempt to start the logger fails at some point, with log (LOG4OM2_log_UI_20250213.log) indicating :
2025-02-13 07:59:49.6976 INFO: [SplashScreen] : Initializing scheduler...
2025-02-13 07:59:49.8486 ERROR: [FwFile][DeserializeObject] : C:\Users\m_kis\AppData\Roaming\Log4OM2\scheduler_clean.xml
[EXCEPTION] There is an error in XML document (29, 39). System.InvalidOperationException: There is an error in XML document (29, 39). ---> System.InvalidOperationException: Instance validation error: 'UpdateMetarData' is not a valid value for ScheduleActivityEnum.
Log shows handfull additional lines and ends with:
2025-02-13 07:59:50.0878 INFO: [#=z6OpZNtamIh8nvJVjuWvYsxw=] : [LOTW] load from file completed
At that point, process hangs without loading the UI
The "fix" is as simple as reinstalling a Log4OM again, without uninstalling the previous one, or changing anything in the file/folder structure. After reinstalling, logger starts just fine, till the next time - immediately after the logger is stopped the next time (intentionally, reboot, unexpected OS shutdown, ...), Log4OM fails to start again with the same error
Thanks!
Miro
