Skip to main content
NetApp Knowledge Base

AIQUM cluster discovery failed with invalid XML character from API response

Views:
54
Visibility:
Public
Votes:
0
Category:
active-iq-unified-manager
Specialty:
om
Last Updated:

Applies to

  • Active IQ Unified Manager (AIQUM) 9.13P1
  • API

Issue

  • Cluster discovery fails with error in AIQUM failed job:

Name: forceAcquisition

Description: Forces acquisition on a Data Source. Will wait until acquisition fails or completes or there is a timeout.

Failure Reason: Errors reported on acquisition with start time xx: xx: xx: xxx: [Communication problem with the cluster Clustername command: cifs-share-get-iter, error: '' on try 5 out of 5]

clipboard_e5741213844b0b1b9f7662c35805e3efb.png

  • au.log for AIQUM may contain similar errors with different Unicode characters and API call:
20XX-02-02 00:11:12,577 WARN  [foundation-poll-0] c.o.s.a.d.n.t.z.ZAPIConnection (ZAPIConnection.java:633) - [netappfoundation] clustername - while executing ZAPIs on datasource: clustername IP: clustername for ZAPI: cifs-share-get-iter, com.onaro.sanscreen.acquisition.framework.datasource.DataSourceErrorException: Failed to parse response org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x8) was found in the element content of the document.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.