Top-Down Discovery fails to create inclusion connection for Microsoft IIS Web Server CI (cmdb_ci_microsoft_iis_web_server)<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Issue During Top-Down Discovery (Service Mapping), Discovery does not create an inclusion connection from the Microsoft IIS Web Server CI to its dependent components. Discovery reports that a containment rule and an associated pattern exist for the CI type, but no inclusion connection is created. Symptoms Discovery output reports the following message: "The system failed to create an inclusion connection from the CI (type: cmdb_ci_microsoft_iis_web_server). There is a containment rule for this CI type and a pattern which is associated with the contained item, but no inclusion connection created."The IIS Web Server appears on the Service Mapping topology map, but downstream connections (application servers, databases) are not drawn beneath it.Suggested Connections may appear, but the underlying containment and inclusion configuration mismatch remains unresolved. Cause A containment rule exists for cmdb_ci_microsoft_iis_web_server, and a pattern is associated with at least one of the contained items, but the pattern does not create the inclusion connection that the containment rule requires. Top-Down Discovery requires both of the following to be aligned: A containment rule that defines the relationship between the parent CI type and the contained CI type.A pattern step that explicitly creates the inclusion connection for the contained item. When the pattern omits the step that creates the inclusion connection, Discovery flags the configuration as inconsistent and reports the error. Resolution Apply the same remediation approach documented in KB1538113 (originally written for cmdb_ci_app_server_tomcat), substituting the IIS Web Server CI class. Navigate to Pattern Designer > Metadata Editor.Locate the containment rules associated with cmdb_ci_microsoft_iis_web_server.Verify the pattern associated with at least one of the contained items. Confirm whether a step that creates the inclusion connection is present and active.Choose one of the following remediations based on intent: Delete the containment rule if the relationship is not required.Set the pattern associated with the contained item to inactive.Modify the pattern so that it explicitly creates the inclusion connection. Validate the change in a non-production instance by re-running Discovery on a representative IIS host.Once verified, promote the change to production and re-run Discovery. Expected outcome: After Discovery runs successfully, the inclusion connection error no longer appears, and downstream CIs are drawn beneath the IIS Web Server on the topology map. Additional Notes If downstream connections (application servers, databases) still do not appear after the inclusion error clears, investigate SSH or credential authentication failures on the contained CIs. Those represent a separate failure mode and should be addressed in a new case.Suggested Connections are heuristic-based and should not be used as a substitute for fixing the containment and inclusion configuration. They may not reflect the true downstream topology.An alternative workaround is to add cmdb_ci_microsoft_iis_web_server to the map_accuracy_errors_ci_types_to_exclude property on the ecc_agent_property table. This suppresses the error but does not fix the underlying configuration, so use it only as a temporary measure. Related Reference KB1538113 — Service Mapping Discovery failed to create an inclusion connection from the CI (type: cmdb_ci_app_server_tomcat). (Now Support login required.) https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1538113 Keywords: Service Mapping, Top-Down Discovery, IIS Web Server, cmdb_ci_microsoft_iis_web_server, inclusion connection, containment rule, pattern designer, metadata editor, topology map, map accuracy error, ECC agent property, suggested connections