Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
vCenter probe hangs when target does not respond on port and causes discovery schedule to be cancelled - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • vCenter probe hangs when target does not respond on port and causes discovery schedule to be cancelled
KB0713750

vCenter probe hangs when target does not respond on port and causes discovery schedule to be cancelled


1083 Views Last updated : Apr 7, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

Overview


vCenter probes may be triggered incorrectly when discovering IPs where there is no vcenter application. The probe then hangs when the target does not respond. This will cause the discovery schedule to be cancelled if there is a maximum time configured, or be stuck if a maximum time is not configured.

Steps to reproduce


  1. Open "Discovery Definition > IP Services"
  2. Search for records where name contains "vmap" and collect the number from the port column
  3. Discover a device where such ports are open but no vcenter application is installed
  4. The probes will be triggered and hang

Root Cause


The first phase of discovery, Shazzam, checks for open ports on a target IP address. Probes will be triggered accordingly depending on the open ports. Such ports can be configured under "Discovery Definition > IP Services".

Solution


The issue is resolved via PRB1073935 in Kingston. Starting in kingston, a probe parameter was created to pre-validate the vcenter application before sending requests.

To turn on pre-validation: 

  1. Go to "Discovery Definition > Probes"
  2. Open the "VMWare - vCenter Datacenters" probe
  3. Add parameter prevalidate_vcenter = true
    Pre validate vcenter parameter

For versions prior to Kingston, or depending on the kingston release, the fix can be back ported as follows:

Warning: Any changes should be tested in non-production instances first

  1. Add prevalidate_vcenter = true parameter to "VMWare - vCenter Datacenters" probe
  2. Go to "MID Server > Script Includes"
  3. Open "AVMWareProbe"
  4. Add the following code before the line containing "this._getServiceInstance();"
    if (this.getParameter('prevalidate_vcenter') == 'true') {
    request = new Packages.com.glide.communications.HTTPRequest(this.vmHost + '/vimservice.wsdl');
    request.setContentType('application/xml');
    request.setHttpTimeout(30000);
    response = request.post('<?xml version="1.0" encoding="UTF-8"?>' +
    '<soapenv:Envelope xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" ' +
    'xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" ' +
    'xmlns:xsd="http://www.w3.org/2001/XMLSchema" ' +
    'xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">' +
    '<soapenv:Body><RetrieveServiceContent xmlns="urn:vim25">' +
    '<_this type="ServiceInstance">ServiceInstance</_this></RetrieveServiceContent>' +
    '</soapenv:Body></soapenv:Envelope>');

    if (!response || (response.getStatusCode() != 200)) {
    this.setError('Not exploring as vCenter: unable to fetch WSDL. The WSDL check is controller by the probe parameter "check_wsdl".');
    return;
    }
    } 

 


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

Attachments

Attachments

  • prevalidate_vcenter.png

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.