Errors for the Vulnerability Response Integration with Claroty CTD

  • Release version: Australia
  • Updated March 12, 2026
  • 3 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Errors for the Vulnerability Response Integration with Claroty CTD

    This document outlines common errors and their causes when using the Vulnerability Response Integration with Claroty CTD. Understanding these errors will help ServiceNow customers troubleshoot effectively and maintain seamless integration with Claroty CTD.

    Show full answer Show less

    Vulnerability Detection Integration (Data Retrieval)

    • Error: Can't run a Claroty CTD Integration without a user name and password combo.
      Cause: Missing user name or password in the integration configuration.
    • Error: Can't run integration without a REST message and REST method specified.
      Cause: REST message or method fields are not populated on the job record.
    • Error: Can't run integration without Claroty CTD server URL specified.
      Cause: URL is absent in the integration configuration.
    • Error: Can't run integration without the detection API resource path specified.
      Cause: detectionapiresourcepath parameter is unpopulated; default is /ranger/assetswithinsights.
    • Error: Invalid response code {response code} received from Claroty CTD.
      Cause: Invalid response indicating possible invalid credentials.
    • Error: Unable to read the counttotal property from JSON data.
      Cause: Invalid payload received; check accessibility through the MID Server.

    Vulnerability Detection Integration (Data Processing)

    • Error: Error writing attachment.
      Cause: MID Server user may lack necessary role; contact your administrator.
    • Error: Attachment content is null: attachment sysid = {sysid}.
      Cause: Possible issue with the Claroty API or ServiceNow.
    • Error: Couldn't find attachment with sysid {sysid}.
      Cause: Data Source attachment was not found.

    Vulnerability Auto-Closure Integration (Data Retrieval)

    • Error: Can't run a Claroty CTD Integration without a user name and password combo.
      Cause: Missing credentials in the configuration.
    • Error: Can't run integration without a REST message and REST method specified.
      Cause: Fields not populated on the job record.
    • Error: Can't run integration without Claroty CTD server URL specified.
      Cause: URL absent in integration configuration.
    • Error: Can't run integration without the detection API resource path specified.
      Cause: Unpopulated detectionapiresourcepath parameter; default is /ranger/assetswithinsights.
    • Error: Invalid response code {response code} received from Claroty CTD.
      Cause: Invalid credentials indicated by response code.
    • Error: Unable to read the counttotal property from JSON data.
      Cause: Invalid payload; ensure Claroty CTD is reachable.
    • Error: Error parsing 'objects' array from response body.
      Cause: Invalid payload; check Outbound HTTP Logs for valid responses.

    Vulnerability Auto-Closure Integration (Data Processing)

    • Error: Failed to parse the Data Dictionary JSON.
      Cause: Invalid JSON payload from Data Source attachment; check for previous errors.

    You may encounter errors that need troubleshooting while you’re working with the Vulnerability Response Integration with Claroty CTD.

    Vulnerability Detection Integration (Data Retrieval)

    Error message Possible cause
    Can’t run a Claroty CTD Integration without a user name and password combo. No user name or password is present on the integration configuration.
    Can’t run integration without a REST message and REST method specified. On the Claroty CTD Integration job record, the REST message or REST method fields aren’t populated.
    Can’t run integration without Claroty CTD server URL specified. No URL is present on the integration configuration.
    Can’t run integration without the detection API resource path specified. On the integration configuration, the detection_api_resource_path parameter isn’t populated. The default is /ranger/assets_with_insights.
    Invalid response code {response code} received from Claroty CTD. The response from the Claroty API was invalid. For example, the message Invalid response code 401 is received from Claroty CTD. This invalid response code means Unauthorized and that the credentials (user name/password) are likely invalid.
    Unable to read the count_total property from JSON data. The count_total used for pagination wasn’t present in the API response. It likely means that an invalid payload was received from Claroty CTD.

    Ensure that the Claroty CTD instance is reachable through the MID Server and examine the Data Source attachment response.json file to ensure that count_total exists.

    Vulnerability Detection Integration (Data Processing)

    Error message Possible cause
    Error writing attachment. The system couldn’t attach the response data to the Data Source. Contact your administrator for further assistance.

    A common cause for this error is that the MID Server user is missing the sn_vul.vr_import_admin role.
    Attachment content is null: attachment sys_id = {sys_id}. The Data Source attachment content is null. This could indicate an issue with the Claroty API itself, or an issue in ServiceNow. Contact your administrator for further assistance.
    Couldn’t find attachment with sys_id {sys_id}. Data Source attachment wasn’t found. Follow the same procedures for the preceding error.

    Vulnerability Auto-Closure Integration (Data Retrieval)

    Error message Possible cause
    Can’t run a Claroty CTD Integration without a user name and password combo. No user name or password is present on the integration configuration.
    Can’t run integration without a REST message and REST method specified. On the Claroty CTD Integration job record, the REST message or REST method fields aren’t populated.
    Can’t run integration without Claroty CTD server URL specified. No URL is present on the integration configuration.
    Can’t run integration without the detection API resource path specified. On the integration configuration, the detection_api_resource_path parameter isn’t populated. The default is /ranger/assets_with_insights.
    Invalid response code {response code} received from Claroty CTD. The response from the Claroty API was invalid. For example, the message Invalid response code 401 is received from Claroty CTD. This invalid response code means Unauthorized and that the credentials (user name/password) are likely invalid.
    Unable to read the count_total property from JSON data. The count_total used for pagination wasn’t present in the API response. It likely means that an invalid payload was received from Claroty CTD.

    Ensure that the Claroty CTD instance is reachable through the MID Server and examine the Data Source attachment response.json file to ensure that count_total exists.
    Error parsing 'objects' array from response body. Likely means that an invalid payload was received from Claroty CTD. Ensure that the Claroty CTD instance is reachable and check Outbound HTTP Logs to see if there was a valid response.

    Vulnerability Auto-Closure Integration (Data Processing)

    Error message Possible cause
    Failed to parse the Data Dictionary JSON. The payload from the Data Source attachment was invalid JSON. Likely another error occurs before this error occurs. Ensure that the Claroty CTD instance is reachable and check Outbound HTTP Logs to see if there was a valid response.