---
sourceDocument: Xanadu API Reference
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/api-reference

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu API Reference

ft:clusterId :

    - crapiref

bundleId :

    - crapiref

workflow :

    - Creator


---

# Generate logs for debugging

# Generate logs for debugging {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

If you experience unexpected behavior when using the ODBC driver, you can enable
debug logging and generate debug logs to help identify the issue.

## Before you begin

[Configure the logging level of the ODBC driver](https://servicenow-prod.fluidtopics.net/cAIavpB1AZrsiwQW13nodg "Change the logging level of the ODBC driver.")

Role required: admin

## About this task

Debug logs can be useful when submitting an incident with Customer Service and Support.

When you enable debug logging, note the version and bitness (32 bit or 64 bit) of
the installed ODBC driver, the Windows operating system, and
the client application you are using with the ODBC driver.

To generate debug
logs, follow these steps.

## Procedure

1. Close all active applications that may use the ODBC driver.
2. Navigate to one of these paths, based on your operating system.  
   * For Windows 10 and later: C:\\ProgramData\\ServiceNow\\odbc\\logging\\
   * For Windows 7: C:\\Users\\\<user_name\>\\AppData\\Local\\ServiceNow\\odbc\\logging
   * For Windows XP and earlier: C:\\Program Files\\ServiceNow\\ODBC\\%LOCALAPPDATA%\\ServiceNow\\odbc\\logging
   {#t_GenerateDebugLogs__ul_xqj_5qn_cr}
3. Delete any existing log data to ensure that you log only relevant information.
4. Run a query that produces the unexpected behavior, then immediately close the application and review the log files.
**Related tasks**   

* [Configure the logging level of the ODBC driver](https://servicenow-prod.fluidtopics.net/cAIavpB1AZrsiwQW13nodg "Change the logging level of the ODBC driver.")