Absent Member.
Absent Member.

<UCMDB Support Tip> How to fix 'Failed to resolve IP' issue

Issue description:

A discovery job fails and an error ‘Failed to resolved IP’ may be reported in Communication log.


A typical error can be as in the example given below:

<log start="17:43:00" severity="warn">Failed to resolve: bejbpm06 (where bejbpm06 is the hostname)

Traceback (most recent call last):

  File "jee", line 1361, in reportNodesInDomainDnsEnabled

  File "jee_discoverer", line 886, in resolveIpsByHostname

  File "netutils", line 1379, in resolveIpsByHostname

ResolveException: Failed to resolve IP




This issue is caused because UCMDB probe cannot get IP address with host name ‘bejbpm06’.


As a test, you can open a CMD window and run ‘ping hostname’.


If it cannot return IP, the user needs to check the DNS setting in their network.  Perhaps, there is a simple way to resolve this.

  1. Go to <Windows>\system32\drivers\etc\
  2. Backup file ‘hosts’ and open it with a text editor
  3. Add a new line like ‘<IP hostname>’, then save.
Hao Yang

“HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.”

Click the KUDOS star on the left to say 'Thanks'
Labels (1)
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.