---
sourceDocument: Australia Platform security
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/platform-security

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Logs and Errors

# Troubleshooting and accessing logs {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

Access various logs to troubleshoot and identify the failure reasons.

## Code Signing logs {#cs-logs__section_qpv_tmp_3rb}

If any of the ECC queue records is not signed by the
Code
Signing Tracker API, the unsigned messages and the required details are displayed in the
Code Signing module. Navigate to System LogsSystem LogCode Signing to access the list of records that are not trusted.

For additional debug node logs, enable
com.glide.codesigning.tracking.debug and set its value to
<kbd class="ph userinput">true</kbd>.

## REST message signature validation failure on MID Server {#cs-logs__section_izn_grp_3rb}

Access the error message regarding to the signature validation failure,
by
navigating to System Web ServicesOutboundREST Message and opening the required REST message record.  
Abbildung : 1. Signature validation failure on MID Server  
Hinweis:  
Error messages related to the ECC firewall rejections start with <kbd class="ph userinput">ECC message execution denied</kbd>.
Abbildung : 2. ECC queue when signature validation fails on MID Server Abbildung : 3. Error message when ECC message is blocked by the user rule

## JDBC probe {#cs-logs__section_w4h_yrp_3rb}

When a JDBC data source with an invalid or missing signature is executed on a MID Server, an error message with the required details is displayed.

Source also displays the details of the error message.

## MID Server logs {#cs-logs__section_wbj_2vp_3rb}

To enable the detailed ECC firewall logging, increase the log level by setting the value of the MID Server configuration parameter, mid.log.level, to <kbd class="ph userinput">TRACE</kbd>. The detailed logs provide information about:

* Rules that the MID Server loaded from the boot configuration file.
* Granular execution trace of rules.
* Specific rule due to which an ECC message is to be accepted or rejected.

{#cs-logs__ul_zks_ybq_3rb}  
Hinweis:  
If boot-config.xml is invalid, the MID Server fails to start and the failure details are logged in the MID agent logs.