Enabling ASP.NET Core stdout log (Windows Server)

Some errors that occurr during application startup prevent Amplia's logging framework from working. In such cases, enabling the ASP.NET Core stdout log usually helps to diagnose the issue.

Important

Disable stdout logging when troubleshooting is complete.

To enable ASP.NET Core stdout log:

1. Navigate to the site's deployment folder on the hosting system.
2. If the logs folder isn't present, create the folder.
3. Edit the web.config file. Set stdoutLogEnabled to true and change the stdoutLogFile path to point to the logs folder (for example, .\logs\stdout). stdout in the path is the log file name prefix. A timestamp, process id, and file extension are added automatically when the log is created. Using stdout as the file name prefix, a typical log file is named stdout_20180205184032_5412.log.
4. Ensure your application pool's identity has write permissions to the logs folder.
5. Save the updated web.config file.
6. Make a request to the app.
7. Navigate to the logs folder. Find and open the most recent stdout log.
8. Study the log for errors.

To disabled it after troubleshooting is complete:

1. Edit the web.config file.
2. Set stdoutLogEnabled to false.
3. Save the file.

Warning

Failure to disable the stdout log can lead to app or server failure. There's no limit on log file size or the number of log files created.