Skip to main content
NetApp Stage KB

Cluster addition failed in UM as invalid XML character return during acquisition

Last Updated:

Applies to

  • ActiveIQ Unified Manager (AIQUM) 9.6+
  • OnCommand Unified Manager (OCUM) 9.5 and Below


  • Cluster addition fails in AIQUM
  • au.log:
2022-05-23 10:17:12,188 WARN [pool-36-thread-4] c.o.s.a.d.n.t.z.ZAPIConnection ( - [netappfoundation] <cluster_name> - while executing ZAPIs on datasource: <cluster_name> IP: <cluster_IP> for ZAPI: storage-disk-get-iter, com.onaro.sanscreen.acquisition.framework.datasource.DataSourceErrorException: Failed to parse response org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x5) was found in the element content of the document.
at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) ~[xercesImpl.jar:?]
at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source) ~[xercesImpl.jar:?]
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) ~[xercesImpl.jar:2.12.0]
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) ~[xercesImpl.jar:2.12.0]
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) ~[xercesImpl.jar:2.12.0]
at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source) ~[xercesImpl.jar:2.12.0]

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.