{"action":"closed","issue":{"url":"https://api.github.com/repos/NLog/NLog/issues/862","labels_url":"https://api.github.com/repos/NLog/NLog/issues/862/labels{/name}","comments_url":"https://api.github.com/repos/NLog/NLog/issues/862/comments","events_url":"https://api.github.com/repos/NLog/NLog/issues/862/events","html_url":"https://github.com/NLog/NLog/issues/862","id":101496368,"number":862,"title":"Troubleshooting Hurdles","user":{"login":"AaronLS","id":2784372,"avatar_url":"https://avatars.githubusercontent.com/u/2784372?v=3","gravatar_id":"","url":"https://api.github.com/users/AaronLS","html_url":"https://github.com/AaronLS","followers_url":"https://api.github.com/users/AaronLS/followers","following_url":"https://api.github.com/users/AaronLS/following{/other_user}","gists_url":"https://api.github.com/users/AaronLS/gists{/gist_id}","starred_url":"https://api.github.com/users/AaronLS/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/AaronLS/subscriptions","organizations_url":"https://api.github.com/users/AaronLS/orgs","repos_url":"https://api.github.com/users/AaronLS/repos","events_url":"https://api.github.com/users/AaronLS/events{/privacy}","received_events_url":"https://api.github.com/users/AaronLS/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/NLog/NLog/labels/question","name":"question","color":"cc317c"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-08-17T19:48:49Z","updated_at":"2015-08-18T04:53:09Z","closed_at":"2015-08-18T04:53:09Z","body":"When trying to troubleshoot it is difficult to get internal logs to work, and throwExceptions has never worked for me.  If you are writing to stderr/stdout then they'll be null streams for scenarios such as a web project.  Instead you'd need to use Diagnostics.Debug.WriteLine.  Logging to file usually requires an absolute path but extra steps are needed to add permissions to ensure it writes successfully.\r\n\r\nTroubleshooting on top of troubleshooting:\r\nhttp://stackoverflow.com/questions/9428724/nlog-internal-log-not-working-with-asp-net-mvc\r\n\r\nI turned throwExceptions on both through the config as well as through code and no exceptions are thrown, even when I have an internal log file configured that it fails to write to.  Seems like if it fails to write the internal log file, and throwExceptions is turned on, then it should throw an exception.\r\n\r\n- I would expect it to be pretty noisy when throwExceptions is turned on, but all quiet.\r\n- I would expect a failure to write the internalLogFile should result in an exception.\r\n- I would suggest adding a internalLogToDebugConsole and clarify in documentation that internalLogToConsole/Error may be silent for some project types because they point to null streams.\r\n\r\nConfig file is successfully loading because I can inspect the log manager Configuration and see the targets from the config file.  \r\n\r\n```\r\n<nlog xmlns=\"http://www.nlog-project.org/schemas/NLog.xsd\"\r\n      xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\r\n      xsi:schemaLocation=\"http://www.nlog-project.org/schemas/NLog.xsd NLog.xsd\"\r\n      autoReload=\"true\"\r\n      throwExceptions=\"true\"\r\n      internalLogLevel=\"Trace\" \r\n      internalLogFile=\"c:/nlog-internal.log\"\r\n      internalLogToConsole=\"true\"\r\n      internalLogToConsoleError=\"true\"\r\n>\r\n```"}}