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.
Pattern discovery error "Solaris global zone host/address of local zone need to be discovered first. Please run quick discovery on this IP and try again." - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Pattern discovery error "Solaris global zone host/address of local zone need to be discovered first. Please run quick discovery on this IP and try again."
KB0749069

Pattern discovery error "Solaris global zone host/address of local zone need to be discovered first. Please run quick discovery on this IP and try again."


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

Issue

Symptoms

Pattern discovery error "Solaris global zone host/address of local zone need to be discovered first. Please run quick discovery on this IP and try again."

Release

All currently supported releases.

Cause

Process detection is triggered when discovering applications as part of pattern discovery. Discovering solaris demands extra logic to determine if the commands run to collect information on the process should be run on the global or local zones. The error to discover the global zone is thrown when process detection if triggered on the global zone and the process is not found. There is no need to discover the global zone due to this error. The error is added as a candidate root cause of the pattern failing. However, it is possible the pattern discovery would still be successful even when this error is found as for solaris there are multiple attempts to collect the process information.

Resolution

  1. Review pattern discovery log process detection. If the process detection is successful this error can be disregarded.
  2. Resolve the errors returned by the process detection, steps will depend on error returned.
  3. Try mid server property mid.solaris.use_netstat_u_param = true.
  4. If error is not resolved, contact support for further troubleshooting.

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?

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.