Skip to main content
NetApp Knowledge Base

Custom workflow failing with "No such host is known" error in OnCommand Workflow Automation

Views:
168
Visibility:
Public
Votes:
3
Category:
oncommand-workflow-automation-wfa
Specialty:
legacy
Last Updated:

Applies to

OnCommand Workflow Automation (WFA) 4.x, 5.x

Windows 2012

 

Issue

Custom workflow is failing with below error

2021-03-13 21:21:19,357 ERROR [com.netapp.wfa.job.backend.JobsExecutionInterceptor] (Thread-1868 (ActiveMQ-client-global-threads)) Job CacheJob{, dataSourceId=DataSourceInfo{id=21, name='ds_name', connectionDetails=ConnectionDetails{id=21, ip='x.x.x.x', port=8080, userName='wfa', password='******', databaseName='null', timeoutInMinutes=10, lastUpdateTime=0}, dataProviderType=DataProviderType{id=16, productType='snapshots', productVersion='OCUM 7.x', scheme='snapshots'}}, schemeId=Scheme{id=8, name='snapshots'}, dataSourceName='ds_name', schemeName='snapshots'} failed: com.netapp.wfa.cache.execution.CacheException: Error running data acquisition script: Exception calling "Connect" with "2" argument(s): "No such host is known"

 

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.