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.
Inconcistent service mapping discovery when multiple connections are attempted to the same host - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Inconcistent service mapping discovery when multiple connections are attempted to the same host
KB0713756

Inconcistent service mapping discovery when multiple connections are attempted to the same host


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

Issue

Overview


Business service discovery at times fails with error "Failed to recognize application" if multiple applications in the map reside on the same host. Resuming discovery often clears the error. This behavior was observed on OpenVMS servers, however could potentially affect discovery of applications residing in other operating systems. OpenVMS operating system is not listed as supported per the following document.

  • Linux Discovery 

Root Cause


Review of MID server agent logs, matching at time of issue, found that connections were not accepted by the target IP address.

<time_stamp> () SSHProtocolEngine [#/<ip_address>:22] Received server DEBUG messageDEBUG: always display: true, message: Failed to allocate pty!&#13

Some environments may limit the number of concurrent connections from a source, and therefore new connection attempts will fail.

Solution


Note: "Failed to recognize application" is a generic error. This solution only applies to when multiple applications are discovered at once which reside on the same host.

Two possible solution are:

  1. Contact the sysadmin managing the system so that concurrent connections from the same source are allowed.
  2. Lower the number of connections created by service map to a given host concurrently.

To control the number of connections to a given IP address by service mapping:

  • Set following MID Server property "mid.servicewatch.max_concurrent_connections" to the desired number, the default is 7. Set it to 1 f the system only allows for a single connection. As a result, as long as there is one ecc queue output records that's currently processing, the others ecc queue records are kept in "ready" state.

Additional Information


For a list of available MID server properties see:

  • MID Server properties

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.