Discovery Patterns return error "Relation and/or reference table cmdb_fc_target is not a known CI Type. Check the discovery logs for more details."Issue <!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Symptoms "Windows OS - Desktop" and "Windows OS - Server" patterns fail during Discovery at stage "Reference between cmdb_fc_target to cmdb_ci_fc_disk" with error message:"Relation and/or reference table cmdb_fc_target is not a known CI Type. Check the discovery logs for more details." Release Madrid Cause Domain separation at the customer's environment. There are duplicate records exist in table "sa_ci_to_pattern" when we checked the form for Pattern "Windows OS - Desktops". Following screenshot show the records after clean up. Prior to the cleanup, there are more records whereby 18 records belong to domain "global" and others belong to other domain. Resolution Check the "Related CI Type" (under Related Links) for pattern record in table "sa_pattern". For example, "Windows OS - Desktops": /nav_to.do?uri=sa_pattern.do?sys_id=bfaf65f7db75a200868a7c841f96199d Compare with a base system and clean up the duplicate records in "Related CI Type" if there is any.