when your application starts and the Console is not running, a TCP connect attempt of the SmartInspect libraries fails and the logging information can thus not be sent to the Console. One option to workaround this is to check if the Console is running before trying to connect. If the Console is not running, then you could start it programmatically directly out of your application. A similar functionality is already on our TODO list.
Another option will be the new ‘reconnect’ protocol option of SmartInspect 2.0 (will be released this month). If this option is set to true, the protocol tries to reconnect automatically if a working connection disconnects or if no connection could be established in the first place.