This text is taken from this discussion: [discussion:439052]
I recently learned, that if C1 encounteres errors during starup due to configuration errors, it will display a generic and misleadning "No Access" message. See for example this discussion: http://compositec1.codeplex.com/discussions/438915.
The application knows exactly what is wrong, and the error(s) is logged. But since the Console cannot start, there is no way to view a friendly view of the log, and the user has to browse through the raw log files.
__Feature request:__
In stead of showing the generic "No Access" error, the Application show display the actual errors that are being logged to the log file. This way, the user will immidiately be able to see where and why the system fails to start.
Comments: ** Comment from web user: napernik **
I recently learned, that if C1 encounteres errors during starup due to configuration errors, it will display a generic and misleadning "No Access" message. See for example this discussion: http://compositec1.codeplex.com/discussions/438915.
The application knows exactly what is wrong, and the error(s) is logged. But since the Console cannot start, there is no way to view a friendly view of the log, and the user has to browse through the raw log files.
__Feature request:__
In stead of showing the generic "No Access" error, the Application show display the actual errors that are being logged to the log file. This way, the user will immidiately be able to see where and why the system fails to start.
Comments: ** Comment from web user: napernik **
We've made some changes to VirtualElementProvider and its configuration, console will be loaded property even if some of the element providers, defined in .../Composite.config, failed to load.
The fix/change will be available in the next code sync to Codeplex (C1 4.0beta3 )