{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/scope-troubleshoot-ad-replication-error-8240-there-is-no-such-object-on-the-server-in-observed-ad/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/scope-troubleshoot-ad-replication-error-8240-there-is-no-such-object-on-the-server-in-observed-ad/",
        "slug": "scope-troubleshoot-ad-replication-error-8240-there-is-no-such-object-on-the-server-in-observed-ad",
        "url": "https://update.dsesecurity.com/updates/scope-troubleshoot-ad-replication-error-8240-there-is-no-such-object-on-the-server-in-observed-ad/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/scope-troubleshoot-ad-replication-error-8240-there-is-no-such-object-on-the-server-in-observed-ad.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/scope-troubleshoot-ad-replication-error-8240-there-is-no-such-object-on-the-server-in-observed-ad/"
        },
        "title": "Scope Troubleshoot AD Replication error 8240 There is no such object on the server in observed AD/DNS state",
        "summary": "Use Troubleshoot AD Replication error 8240 There is no such object on the server to review this narrow operational decision without extending the source beyond its stated scope.",
        "format": {
            "slug": "briefing",
            "name": "Briefing"
        },
        "priority": {
            "slug": "advisory",
            "name": "Advisory"
        },
        "featured": false,
        "image": {
            "theme": "network-infrastructure",
            "label": "Networks & infrastructure",
            "alt": "Resilient network core with engineered blue and gold data paths.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "slug": "cybersecurity",
                "name": "Cybersecurity",
                "url": "https://update.dsesecurity.com/topic/cybersecurity/"
            },
            {
                "slug": "microsoft-365-identity",
                "name": "Microsoft 365 & Identity",
                "url": "https://update.dsesecurity.com/topic/microsoft-365-identity/"
            },
            {
                "slug": "networks-infrastructure",
                "name": "Networks & Infrastructure",
                "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
            }
        ],
        "author": {
            "name": "DSE Security Editorial Team",
            "url": "https://update.dsesecurity.com/#editorial-team",
            "type": "Organization"
        },
        "publisher": {
            "name": "Detection Systems & Engineering",
            "url": "https://dsesecurity.com/"
        },
        "published_at": "2026-08-27T17:02:25+00:00",
        "modified_at": "2026-08-27T17:29:40+00:00",
        "reviewed_on": "2026-08-27",
        "reading_minutes": 3,
        "word_count": 607,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of Troubleshoot AD Replication error 8240 There is no such object on the server",
        "dse_recommendation": "Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards.",
        "primary_source": {
            "name": "Troubleshoot AD Replication error 8240 There is no such object on the server",
            "url": "https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/active-directory-replication-error-8240",
            "published_on": null,
            "authority": "Microsoft Learn"
        },
        "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
        "usage_info": "https://update.dsesecurity.com/usage/",
        "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
        "content_html": "<p>Use this document to resolve one bounded operational decision: Scope Troubleshoot AD Replication error 8240 There is no such object on the server in observed AD/DNS state. Only the official source and traced locations below supply facts. Confirm applicability before acting.</p>\n<h2>Source fact:</h2>\n<p>The official <a href=\"https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/active-directory-replication-error-8240\" target=\"_blank\" rel=\"noopener noreferrer\">Troubleshoot AD Replication error 8240 There is no such object on the server</a> from Microsoft supports the following bounded statements:</p>\n<ul>\n<li>At Introduction below H1, Microsoft states: “This article discusses the symptoms, cause, and resolution for Active Directory Domain Services (AD DS) operations that fail and generate Win32 error 8240: &#8220;There is no such object on the server.&#8221;” The research record locates this support at <strong>Introduction below H1</strong>.</li>\n<li>At Introduction below H1, Microsoft states: “Note: Home users: This article is intended for technical support agents and IT professionals only.” The research record locates this support at <strong>Introduction below H1</strong>.</li>\n</ul>\n<p>These statements are the factual basis for this document. Do not extend them into a broader assurance. Review Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services only where the source and recorded environment align.</p>\n<h2>What the source does not establish</h2>\n<p>The cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials before translating the source into an operational decision.</p>\n<h2>Applicability questions</h2>\n<ul>\n<li>For source statement 1 at <strong>Introduction below H1</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 2 at <strong>Introduction below H1</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>Which deployed instance of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services will be compared with the source, and why that instance?</li>\n<li>How will the review distinguish a source mismatch from a failure in Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials?</li>\n<li>Who approves the conclusion, exception, test window, and rollback threshold?</li>\n</ul>\n<h2>DSE recommendation:</h2>\n<p>DSE recommends using the cited source as the evidence anchor for this decision. Start with applicability, then compare the observed state with the cited source. Record the source location, examined part of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, observed and expected states, owner, and reason for deviation.</p>\n<p>Translate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials, while excluding secrets and sensitive personal or topology data from ordinary tickets.</p>\n<h2>Verification and evidence</h2>\n<p>Keep the source locations <strong>Introduction below H1</strong>; <strong>Introduction below H1</strong> adjacent to the sanitized artifacts used for comparison. Prefer sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state, with enough identity and timing data for an independent recheck.</p>\n<p>Label this evidence set <strong>DSE-20260827-301</strong> so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.</p>\n<p>Record the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes.</p>\n<h2>Official references</h2>\n<ul>\n<li><a href=\"https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/active-directory-replication-error-8240\" target=\"_blank\" rel=\"noopener noreferrer\">Troubleshoot AD Replication error 8240 There is no such object on the server</a> — Microsoft</li>\n</ul>",
        "content_text": "Use this document to resolve one bounded operational decision: Scope Troubleshoot AD Replication error 8240 There is no such object on the server in observed AD/DNS state. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Troubleshoot AD Replication error 8240 There is no such object on the server from Microsoft supports the following bounded statements:\n\nAt Introduction below H1, Microsoft states: “This article discusses the symptoms, cause, and resolution for Active Directory Domain Services (AD DS) operations that fail and generate Win32 error 8240: “There is no such object on the server.”” The research record locates this support at Introduction below H1.\nAt Introduction below H1, Microsoft states: “Note: Home users: This article is intended for technical support agents and IT professionals only.” The research record locates this support at Introduction below H1.\n\nThese statements are the factual basis for this document. Do not extend them into a broader assurance. Review Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services only where the source and recorded environment align.\nWhat the source does not establish\nThe cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials before translating the source into an operational decision.\nApplicability questions\n\nFor source statement 1 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\nWhich deployed instance of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services will be compared with the source, and why that instance?\nHow will the review distinguish a source mismatch from a failure in Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials?\nWho approves the conclusion, exception, test window, and rollback threshold?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Start with applicability, then compare the observed state with the cited source. Record the source location, examined part of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, observed and expected states, owner, and reason for deviation.\nTranslate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials, while excluding secrets and sensitive personal or topology data from ordinary tickets.\nVerification and evidence\nKeep the source locations Introduction below H1; Introduction below H1 adjacent to the sanitized artifacts used for comparison. Prefer sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state, with enough identity and timing data for an independent recheck.\nLabel this evidence set DSE-20260827-301 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\nRecord the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes.\nOfficial references\n\nTroubleshoot AD Replication error 8240 There is no such object on the server — Microsoft",
        "content_markdown": "Use this document to resolve one bounded operational decision: Scope Troubleshoot AD Replication error 8240 There is no such object on the server in observed AD/DNS state. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [Troubleshoot AD Replication error 8240 There is no such object on the server](https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/active-directory-replication-error-8240) from Microsoft supports the following bounded statements:\n\n- At Introduction below H1, Microsoft states: “This article discusses the symptoms, cause, and resolution for Active Directory Domain Services (AD DS) operations that fail and generate Win32 error 8240: “There is no such object on the server.”” The research record locates this support at Introduction below H1.\n\n- At Introduction below H1, Microsoft states: “Note: Home users: This article is intended for technical support agents and IT professionals only.” The research record locates this support at Introduction below H1.\n\nThese statements are the factual basis for this document. Do not extend them into a broader assurance. Review Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services only where the source and recorded environment align.\n\n## What the source does not establish\n\nThe cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials before translating the source into an operational decision.\n\n## Applicability questions\n\n- For source statement 1 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\n\n- Which deployed instance of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services will be compared with the source, and why that instance?\n\n- How will the review distinguish a source mismatch from a failure in Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials?\n\n- Who approves the conclusion, exception, test window, and rollback threshold?\n\n## DSE recommendation:\n\nDSE recommends using the cited source as the evidence anchor for this decision. Start with applicability, then compare the observed state with the cited source. Record the source location, examined part of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, observed and expected states, owner, and reason for deviation.\n\nTranslate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials, while excluding secrets and sensitive personal or topology data from ordinary tickets.\n\n## Verification and evidence\n\nKeep the source locations Introduction below H1; Introduction below H1 adjacent to the sanitized artifacts used for comparison. Prefer sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state, with enough identity and timing data for an independent recheck.\n\nLabel this evidence set DSE-20260827-301 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\n\nRecord the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes.\n\n## Official references\n\n- [Troubleshoot AD Replication error 8240 There is no such object on the server](https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/active-directory-replication-error-8240) — Microsoft"
    },
    "json_ld": {
        "@context": "https://schema.org",
        "@graph": [
            {
                "@type": "Organization",
                "@id": "https://dsesecurity.com/#organization",
                "name": "Detection Systems & Engineering",
                "alternateName": "DSE Security",
                "url": "https://dsesecurity.com/",
                "logo": {
                    "@type": "ImageObject",
                    "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20"
                }
            },
            {
                "@type": "Organization",
                "@id": "https://update.dsesecurity.com/#editorial-team",
                "name": "DSE Security Editorial Team",
                "url": "https://update.dsesecurity.com/",
                "parentOrganization": {
                    "@id": "https://dsesecurity.com/#organization"
                }
            },
            {
                "@type": "WebSite",
                "@id": "https://update.dsesecurity.com/#website",
                "name": "DSE Updates",
                "alternateName": "DSE Security Knowledge Hub",
                "url": "https://update.dsesecurity.com/",
                "inLanguage": "en-US",
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "potentialAction": {
                    "@type": "SearchAction",
                    "target": {
                        "@type": "EntryPoint",
                        "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}"
                    },
                    "query-input": "required name=search_term_string"
                }
            },
            {
                "@type": "WebPage",
                "@id": "https://update.dsesecurity.com/updates/scope-troubleshoot-ad-replication-error-8240-there-is-no-such-object-on-the-server-in-observed-ad/",
                "url": "https://update.dsesecurity.com/updates/scope-troubleshoot-ad-replication-error-8240-there-is-no-such-object-on-the-server-in-observed-ad/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-27"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/scope-troubleshoot-ad-replication-error-8240-there-is-no-such-object-on-the-server-in-observed-ad/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Scope Troubleshoot AD Replication error 8240 There is no such object on the server in observed AD/DNS state",
                        "item": "https://update.dsesecurity.com/updates/scope-troubleshoot-ad-replication-error-8240-there-is-no-such-object-on-the-server-in-observed-ad/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/scope-troubleshoot-ad-replication-error-8240-there-is-no-such-object-on-the-server-in-observed-ad/#article",
                "identifier": "https://update.dsesecurity.com/updates/scope-troubleshoot-ad-replication-error-8240-there-is-no-such-object-on-the-server-in-observed-ad/",
                "url": "https://update.dsesecurity.com/updates/scope-troubleshoot-ad-replication-error-8240-there-is-no-such-object-on-the-server-in-observed-ad/",
                "headline": "Scope Troubleshoot AD Replication error 8240 There is no such object on the server in observed AD/DNS state",
                "description": "Use Troubleshoot AD Replication error 8240 There is no such object on the server to review this narrow operational decision without extending the…",
                "abstract": "Use Troubleshoot AD Replication error 8240 There is no such object on the server to review this narrow operational decision without extending the source beyond its stated scope.",
                "articleBody": "Use this document to resolve one bounded operational decision: Scope Troubleshoot AD Replication error 8240 There is no such object on the server in observed AD/DNS state. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Troubleshoot AD Replication error 8240 There is no such object on the server from Microsoft supports the following bounded statements:\n\nAt Introduction below H1, Microsoft states: “This article discusses the symptoms, cause, and resolution for Active Directory Domain Services (AD DS) operations that fail and generate Win32 error 8240: “There is no such object on the server.”” The research record locates this support at Introduction below H1.\nAt Introduction below H1, Microsoft states: “Note: Home users: This article is intended for technical support agents and IT professionals only.” The research record locates this support at Introduction below H1.\n\nThese statements are the factual basis for this document. Do not extend them into a broader assurance. Review Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services only where the source and recorded environment align.\nWhat the source does not establish\nThe cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials before translating the source into an operational decision.\nApplicability questions\n\nFor source statement 1 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\nWhich deployed instance of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services will be compared with the source, and why that instance?\nHow will the review distinguish a source mismatch from a failure in Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials?\nWho approves the conclusion, exception, test window, and rollback threshold?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Start with applicability, then compare the observed state with the cited source. Record the source location, examined part of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, observed and expected states, owner, and reason for deviation.\nTranslate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials, while excluding secrets and sensitive personal or topology data from ordinary tickets.\nVerification and evidence\nKeep the source locations Introduction below H1; Introduction below H1 adjacent to the sanitized artifacts used for comparison. Prefer sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state, with enough identity and timing data for an independent recheck.\nLabel this evidence set DSE-20260827-301 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\nRecord the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes.\nOfficial references\n\nTroubleshoot AD Replication error 8240 There is no such object on the server — Microsoft",
                "datePublished": "2026-08-27T17:02:25+00:00",
                "dateModified": "2026-08-27T17:29:40+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/scope-troubleshoot-ad-replication-error-8240-there-is-no-such-object-on-the-server-in-observed-ad/"
                },
                "inLanguage": "en-US",
                "isAccessibleForFree": true,
                "author": {
                    "@type": "Organization",
                    "name": "DSE Security Editorial Team",
                    "url": "https://update.dsesecurity.com/#editorial-team"
                },
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "image": {
                    "@type": "ImageObject",
                    "@id": "https://update.dsesecurity.com/updates/scope-troubleshoot-ad-replication-error-8240-there-is-no-such-object-on-the-server-in-observed-ad/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Scope Troubleshoot AD Replication error 8240 There is no such object on the server in observed AD/DNS state"
                },
                "articleSection": [
                    "Cybersecurity",
                    "Microsoft 365 & Identity",
                    "Networks & Infrastructure"
                ],
                "keywords": [
                    "Cybersecurity",
                    "Microsoft 365 & Identity",
                    "Networks & Infrastructure",
                    "Briefing",
                    "Advisory priority"
                ],
                "genre": "Briefing",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Cybersecurity",
                        "url": "https://update.dsesecurity.com/topic/cybersecurity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Microsoft 365 & Identity",
                        "url": "https://update.dsesecurity.com/topic/microsoft-365-identity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Networks & Infrastructure",
                        "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
                    }
                ],
                "wordCount": 607,
                "timeRequired": "PT3M",
                "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
                "usageInfo": "https://update.dsesecurity.com/usage/",
                "copyrightHolder": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
                "citation": {
                    "@type": "CreativeWork",
                    "name": "Troubleshoot AD Replication error 8240 There is no such object on the server",
                    "url": "https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/active-directory-replication-error-8240"
                }
            }
        ]
    }
}