Hitachi service ETL failing with error- Cannot discover the Array class due to the following error 'CIM_ERR_FAILED'

Version 5
    Share:|

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    TrueSight Capacity Optimization


    COMPONENT:

    Capacity Optimization


    APPLIES TO:

    TrueSight Capacity Optimization Capacity Optimization



    DETAILS:

    In debug level log of ETL we saw these error messages,

    ---<cut>---
    INFO : 2017/01/18 10:15:00 CET ; Thread 324044 ; HDS ; com.sentrysoftware.portal.common.job.interruption.ControlledExecution ; $Revision$ ; doRun
         | EXCEPTION SAXException : CLASSNAME attribute not found!
         |         org.sblim.cimclient.internal.cimxml.sax.node.Node.getClassName(Node.java:187)
         |         org.sblim.cimclient.internal.cimxml.sax.node.InstanceNode.init(InstanceNode.java:66)
         | EXCEPTION WBEMException : CIM_ERR_FAILED
         |         org.sblim.cimclient.internal.wbem.WBEMClientCIMXML.enumerateInstances(WBEMClientCIMXML.java:755)
         |         com.sentrysoftware.portal.client.wbem.impl.EnumeratesInstancesOperation.execute(WBEMClientImpl.java:622)
         | EXCEPTION WBEMServerFailureException : CIM_ERR_FAILED
         |     WBEMServerFailureException [Error=protocol.connection.serverfailure, Context=[WBEM/CIM-XML, https://10.129.0.103:5989, UT01257, CIM_ERR_FAILED]]

         |         com.sentrysoftware.portal.client.wbem.impl.WBEMClientImpl.createError(WBEMClientImpl.java:476)
         |         com.sentrysoftware.portal.client.wbem.impl.WBEMClientImpl.doRequest(WBEMClientImpl.java:374)
         | EXCEPTION WBEMResponseException : CIM_ERR_FAILED
         |     WBEMResponseException [Error=protocol.response.full, Context=[WBEM/CIM-XML, SELECT Name FROM CIM_Namespace [interop], CIM_ERR_FAILED]]
         |         com.sentrysoftware.portal.hitachi.common.AbstractHITACHICollect.selectData(AbstractHITACHICollect.java:174)
         |         com.sentrysoftware.portal.hitachi.common.AbstractHITACHICollect.useSpecificNamespace(AbstractHITACHICollect.java:511)
         |         com.sentrysoftware.portal.hitachi.common.AbstractHITACHICollect.selectData(AbstractHITACHICollect.java:165)
         |         com.sentrysoftware.portal.hitachi.Array.discover(Array.java:378)
         |         com.sentrysoftware.portal.common.job.impl.DiscoveryOperation.discoverClass(DiscoveryOperation.java:143)
         | EXCEPTION DiscoveryException : Underlaying error
         |     DiscoveryException [Error=discovery, Context=[class com.sentrysoftware.portal.hitachi.Array]]
         |         com.sentrysoftware.portal.hitachi.Array.discover(Array.java:456)
         |         com.sentrysoftware.portal.common.job.impl.DiscoveryOperation.discoverClass(DiscoveryOperation.java:143)
         | EXCEPTION OperationException : Discovery (Array) completed with error(s).
         |         com.sentrysoftware.portal.common.job.impl.DiscoveryOperation.interruptAfterDiscoveryException(DiscoveryOperation.java:179)
         |         com.sentrysoftware.portal.common.job.impl.DiscoveryOperation.discoverClass(DiscoveryOperation.java:147)
         | An operation fails, this will be added to the current execution error stack.
    ---<cut>---

    This errors are in most cases problems on the Storage Provider, the ETL is connecting to.

    1.  Collect Trouble shooting  before escalating to Sentry. 
     http://www.sentrysoftware.com/support/troubleshooting-tools.asp with the help of Hitachi admin.
    2.  Collect the logs of possible from the SMI-S provider store in this example location: 
    C:\Mapp\wk\832000480182\SMI\logs  the real path depends on the Firmware.


    Article Number:

    000129397


    Article Type:

    Product/Service Description



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles