cvc-complex-type.2.4.d: no child is expected here

What the message literally means

The schema permits exactly one line inside batch. The second line exceeds maxOccurs="1", so removing the accidental duplicate yields a complete valid batch. The corrected toy document illustrates duplicate removal; real application data must be reconciled before any record is discarded.

Three common causes to check first

1. A child exceeds its maximum count. Remember that maxOccurs defaults to one when the attribute is absent.
2. Two mutually exclusive choice branches were emitted together. Once the permitted branch is complete, the next branch may be an additional illegal child.
3. A field was written at the wrong nesting level. A tag intended for the next record can arrive after the current parent’s allowed content has finished.

Repair and retest

Inspect the parent’s particle and the occurrence limits of both the child and enclosing groups. Count children in document order, then identify the transition after which the validator expects the parent to end. Correct the export loop, duplicate join or container boundary that produced the surplus. Rerun with a real multi-record example to check that the repair preserves every intended record.

When this is a namespace problem

Changing a namespace cannot make a truly exhausted content model accept more children. A namespace mismatch may influence which earlier branch was selected, so inspect earlier diagnostics first. If a repeated child has the same expanded name as its accepted predecessor, occurrence counting is the stronger lead.

System.Xml.Schema: invalid child after completed content

The a and d suffixes answer different questions. The a case can often name another expected child; the d case says the parent should stop accepting children. Increasing maxOccurs without agreement changes the contract and can conceal accidental duplication in upstream data.

Complete tested XML and XSD pairs

Open either variant in the workbench, then choose Validate XML. Loading an example does not run validation or send documents; server checks require the existing permission checkbox.

These transcripts were captured on 5 November 2026 from the exact files shown below. Download all measured results and SHA-256 hashes.

<batch>
  <line>A</line>
  <line>B</line>
</batch>

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
  <xs:element name="batch">
    <xs:complexType>
      <xs:sequence>
        <xs:element name="line" type="xs:string" maxOccurs="1"/>
      </xs:sequence>
    </xs:complexType>
  </xs:element>
</xs:schema>

<batch>
  <line>A</line>
</batch>

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
  <xs:element name="batch">
    <xs:complexType>
      <xs:sequence>
        <xs:element name="line" type="xs:string" maxOccurs="1"/>
      </xs:sequence>
    </xs:complexType>
  </xs:element>
</xs:schema>

cvc-complex-type.2.4.d: Invalid content was found starting with element 'line'. No child element is expected at this point.

The element 'batch' has invalid child element 'line'.

Element 'line': This element is not expected.

Unexpected child with tag 'line' at position 2.

Saxon comparison and test scope

Saxonica documents XSD processing as an Enterprise Edition feature. The Saxon rows map the named constraint, rather than presenting an invented message. The four measured rows are Xerces, .NET, the shipped workbench engine and XSDHub’s second engine.

The corrected results apply to these self-contained XSD 1.0 specimens. They do not establish business-rule acceptance for a different document or schema version.

Continue the diagnosis

• cvc-complex-type.2.4.a: invalid child element
• xsd minoccurs maxoccurs
• xsd sequence vs choice

All parser error codes · XML and XSD validator

Primary references

• Apache Xerces message catalogue
• Microsoft: schema validation and identity checks