---
sourceDocument: Xanadu API Reference
sourceDocumentLink: https://www.servicenow.com/docs/r/xanadu/api-reference

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu API Reference

ft:clusterId :

    - crapiref

bundleId :

    - crapiref

workflow :

    - Creator


---

# Configure the logging level of the ODBC driver

# Configure the logging level of the ODBC driver {#ariaid-title1}

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

Change the logging level of the ODBC driver.

## Before you begin

You must have administrator-level access for the Windows computer on which you want to configure the logging level.

Role required: none

## Procedure

1. In Windows, navigate to StartProgramsServiceNow ODBCManagement Console.
2. \[ODBC version 1.0.8\] Within the management console, navigate to \<your_installation_directory\>ServicesServiceNow_ODBCService SettingsIP Parameters.
3. \[ODBC version 1.0.8\] Change the value of the ServiceJVMOptions attribute to the desired logging level.  
4. Within the management console, navigate to \<your_installation_directory\>ServicesServiceNow_ODBCService SettingsLogging.
5. Change the value of the ServiceDebugLogLevel by selecting all available check boxes.  
6. In Windows, navigate to StartProgramsServiceNow ODBCODBC Administrator.
7. In the ODBC Administrator, select the Tracing tab.
8. Navigate to the path in the Log File Path field and delete the old log file, if it exists.
9. Click Start Tracing Now.
10. Enable SOAP debugging for your ServiceNow instance.
**Related concepts**   

* [Debug incoming SOAP envelope](https://www.servicenow.com/docs/krHVnSa_7dyqfMtkz15FzQ "To capture incoming SOAP envelope XML in the system log, add the property glide.processor.debug.SOAPProcessor with a value of true.")  
**Related tasks**   

* [Generate logs for debugging](https://www.servicenow.com/docs/7O0VCM8Nt_A66o27fVVMbQ "If you experience unexpected behavior when using the ODBC driver, you can enable debug logging and generate debug logs to help identify the issue.")

*[\>]: and then