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.
Getting error when saving any OOB pattern with error: "Invalid ndl, Entry point type xxxx in step yyyy in connection section zzzz is not defined on any pattern of relevant included CI" - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Getting error when saving any OOB pattern with error: "Invalid ndl, Entry point type xxxx in step yyyy in connection section zzzz is not defined on any pattern of relevant included CI"
KB0826545

Getting error when saving any OOB pattern with error: "Invalid ndl, Entry point type xxxx in step yyyy in connection section zzzz is not defined on any pattern of relevant included CI"


1350 Views Last updated : Aug 24, 2022 public Copy Permalink
KB Summary by Now Assist

Issue

In an OOB Pattern with a connection section step is defined, after making any changes on it, you are not able to save the changes. The following error is shown: "Invalid ndl, Entry point type xxxx in step yyyy in connection section zzzz is not defined on any pattern of relevant included CI"
Example steps to reproduce:

  1. Deactivate the following patterns: J2EE EAR On Linux, J2EE EAR On Windows, Websphere Portal On Linux, Websphere Portal On Windows
  2. Make any changes (e.g. the name) on OOB "Websphere On Unix" Pattern.
  3. Try to save the change, and observe the following error message: "Invalid ndl, Entry point type cmdb_ci_endpoint_j2ee_ear in step create connection to EARS in connection section EAR Connectivity Z/OS is not defined on any pattern of relevant included CI'"
  4. The changes in the pattern failed to be saved.

 

Release

Any

Cause

This is working as designed.

In the connection section step, during discovery or service mapping, the pattern will invoke the next pattern defined in this step. The entry point type that you defined in the connection section of the current pattern should match entry point type defined in Identification section of Any Active pattern. 

If somehow the pattern has been modified with any of the following, then you will encounter the error message:

  1. The pattern is deactivated
  2. The entry point type in Identification section has been removed or changed to other value

Resolution

Based on the example on this KB article, you can do the following step to find out all patterns involved and resolve them accordingly:

  1. Get the entry point type in the error message. In this case, you can find in the "Pattern" tab, the following entries: connection_type = INCLUSION, entry_point_type = "cmdb_ci_endpoint_j2ee_ear".
  2. Get containment rules (cmdb_metadata_containment) based on the CI type of the above pattern. In this case, the CI type is cmdb_ci_app_server_websphere.
  3. Use this as filter (parent or child) and find out all the CI related to it. In this case: cmdb_ci_app_server_ws_ear, cmdb_ci_appl_websphere_portal.
  4. Search all the pattern with CI type = results from step 3. In this case, you will see 4 patterns: J2EE EAR On Linux, J2EE EAR On Windows, Websphere Portal On Linux, Websphere Portal On Windows.
  5. Check if these patterns have been deactivated or the entry point type has been modified (removed or changed to other value).
  6. Revert these patterns to OOB and you should be able to save your original pattern.

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.