title: Azure Data Studio Troubleshooting

ms.custom: updatefrequency5

Report issues to [GitHub Issue Tracker](https://github.com/Microsoft/azuredatastudio/issues) and let us know any details that will help reproduce the error. Include any [log information](#how-to-set-the-logging-level) from the log file.

* Don't enumerate multiple bugs or feature requests in the same issue.

* Don't add your issue as a comment to an existing issue unless it's for the identical input. Many issues look similar, but have different causes.

* Version of Azure Data Studio

* Reproducible steps (1... 2... 3...) and what you expected versus what you actually saw.

* Images, animations, or a link to a video. Images and animations illustrate repro-steps but don't replace them.

* A code snippet that demonstrates the issue or a link to a code repository we can easily pull down onto our machine to recreate the issue.

* Errors in the Dev Tools Console (Help | Toggle Developer Tools)

Please remember to do the following:

* Search the issue repository to see if the same issue already exists.

* Simplify your code around the issue so we can better isolate the problem.

Run the `Developer: Set Log Level...` command to select the log level for the current session. This value is NOT persisted over multiple sessions - so if you restart Azure Data Studio it will revert back to the default `Info` level.

If you want to enable debug logging for startup then set the log level to `Debug` and run the `Developer: Reload Window` command.

If the `Mssql: Log Debug Info` user setting is set to true, then debug log info will be sent to the `MSSQL` output channel.

From Azure Data Studio, run the `Developer: Open Logs Folder` command to open the path to the logs. There's many different types of log files that write there, a few of the commonly used ones are:

1. `renderer#.log` (for example, renderer1.log) - this file is the log file for the main process.

1. `telemetry.log` - When the log level is set to `Trace` this file will contain the telemetry events sent by Azure Data Studio

1. `exthost#/exthost.log` - Log file for the extension host process (this is only the process itself, not the extensions running inside it)

1. `exthost#/Microsoft.mssql` - Logs for the mssql extension, which contains much of the core logic for MSSQL-related features

* sqltools.log is the log for SQL Tools Service

1. `exthost#/output_logging_#######` - these folders contain the messages displayed in the `Output` panel in Azure Data Studio. Each file is named `#-<Channel Name>` so for example the `Notebooks` output channel may output to a file named `3-Notebooks.log`.

If you are asked to provide logs, zip up the entire folder to ensure that the correct logs are included.

If Azure Data Studio crashes unexpectedly, restarting Azure Data Studio should reopen any unsaved editor files as well. If they do not, there may have been an error trying to reopen them. In that case, follow these steps to navigate to the folder containing the backups where you can manually open them to recover their contents.

1. Run the `Developer: Open User Data Folder` command in Azure Data Studio from the **Command Palette** (**Ctrl/Cmd + Shift + P**).

2. In the folder that opens, navigate to the `Backups` folder.

This will contain folders with randomly generated names. Within these folders will be files that contain the editor backups (which will include some additional metadata along with their text contents).