When an application fails to start due to the log folder not being present, the application needs to be better about reporting the true cause of the failure. It should be easy enough for a junior developer / deployment engineer to determine the cause of the error. Ideas include writing to the event log, or to a custom error web page for web apps or the console for console apps.
Logged In: YES
user_id=1959419
Originator: NO
I have got the following messages with new startup logger:
[ConfigManager][?]default: Incorrect path in 'location' attribute
[ConfigManager][?]Caching: Incorrect path in 'location' attribute
Are these messages enough or do I need to do any more diagnostics?