What does Windows error code 15149 (ERROR_PRI_MERGE_MISSING_SCHEMA) mean?

Previous	Next
ERROR_PRI_MERGE_VERSION_MISMATCH	ERROR_PRI_MERGE_LOAD_FILE_FAILED

ERROR_PRI_MERGE_MISSING_SCHEMA

The primary PRI files to be merged does not contain a schema.

Windows assigns decimal 15149 and hexadecimal 0x00003B2D to ERROR_PRI_MERGE_MISSING_SCHEMA. The constant belongs to Package Resource Index (PRI) merge processing; its name is not enough to identify the affected directory object, DNS zone, policy, installer, package, or resource context.

Operational meaning

The key question is whether the designated primary PRI supplies the resource schema used to interpret every merged input. The value describes a primary PRI input that does not contain the schema required for merge; it does not prove that the whole domain, DNS service, network, servicing stack, application package, or operating system has failed.

Likely impact: Without the primary schema, resource keys and qualifiers cannot be interpreted reliably. Record the scope that was actually tested instead of escalating from one rejected object or phase to a system-wide outage.

Where the result appears

• This result can appear while processing a primary PRI input that does not contain the schema required for merge.
• This result can appear while merging resources.pri files for an app package, resource package, or deployment image.
• This result can appear while MakePri merge or build automation that combines package resource indexes.
• It can appear while validation of package family, main-package, bundle, schema, and canonical output constraints.

Typical causes

• the wrong PRI was selected as primary.
• the file is a resource-only PRI.
• generation omitted schema sections.
• the input is truncated or not the expected package index.

Diagnostic sequence

1. capture it immediately after the failing or status-returning call and record whether the API uses Win32, DNS_STATUS, HRESULT conversion, or callback semantics.
2. identify the exact target involved in a primary PRI input that does not contain the schema required for merge, including stable GUIDs, DNs, zone names, package identities, file hashes, policy names, or process identifiers as applicable.
3. prove the state boundary: the designated primary PRI supplies the resource schema used to interpret every merged input.
4. collect primary input path and hash and PRI dump showing schemas before restarting services, deleting objects, rebuilding packages, or changing policy.
5. correlate package role of each input with MakePri command line, input PRI inventory, package identities, schemas, file hashes, output path, tool version, and the first detailed merge diagnostic.
6. determine whether the result is a failure, warning, informational completion, continuation request, or marker constant before choosing retry behavior.
7. after changing one responsible condition, repeat the same smallest operation and verify both success and absence of unintended partial effects.

Evidence to preserve

• collect primary input path and hash.
• collect PRI dump showing schemas.
• collect package role of each input.
• collect MakePri generation command.
• collect file integrity and tool version.

Correlate this evidence with MakePri command line, input PRI inventory, package identities, schemas, file hashes, output path, tool version, and the first detailed merge diagnostic. Preserve raw identifiers and the first detailed diagnostic: translating everything to 15149 can hide whether the cause was validation, topology, authorization, replication, policy, file I/O, packaging, or an intentional continuation state.

Recovery and retry

The recovery objective for it is to select or regenerate a main PRI that contains the authoritative schema before merging resource packages.

Retry only after the recorded boundary changes and prior completion is known. Read-only discovery for it can usually be repeated with bounded backoff; directory mutations, DNS updates, policy installation, servicing actions, and PRI writes require a state check first. Backoff for it cannot repair malformed input, unsupported structure, identity collision, missing authority, or incompatible package metadata.

Telemetry and support fields

• record pri_merge_missing_schema_operation — producing API, command, callback, or servicing phase.
• record pri_merge_missing_schema_target — stable object, zone, policy, package, file, or account identity.
• record pri_merge_missing_schema_state_before and pri_merge_missing_schema_requested_state.
• record pri_merge_missing_schema_first_status — earliest component-specific code before translation.
• record pri_merge_missing_schema_server, pri_merge_missing_schema_process, UTC timestamp, and correlation ID.

A support bundle for it should include decimal 15149, hexadecimal 0x00003B2D, the smallest reproducible request, target identity, effective configuration, and evidence from the owning Windows component. When documenting it, remove secrets from exported logs but keep SIDs, GUIDs, package-family names, record types, and hashes when they are needed to distinguish objects.

Difference from nearby results

ERROR_PRI_MERGE_VERSION_MISMATCH finds incompatible schemas; this code says the primary schema is absent This distinction determines whether the correct next step is input correction, topology repair, continuation, policy review, package rebuild, or no error handling at all.

Practical validation scenario

A pipeline chooses a language resource PRI as the primary input. Pointing merge at the main package PRI supplies the required schema. A negative test should reproduce it with the responsible condition preserved; the recovery test should alter only that condition and confirm the intended final state.

Developer and administrator guidance

Developers should model it explicitly in the result domain instead of collapsing every nonzero value into “failed.” Administrators should capture evidence before destructive remediation and use the component that owns a primary PRI input that does not contain the schema required for merge. Monitoring for it should suppress range markers and classify warning, informational, cancellation, and continuation values separately from terminal failures.

References

• Microsoft: exact Win32 system error range — official context relevant to it.
• Microsoft: MakePri.exe command options — official context relevant to it.
• Microsoft: Package Resource Index files — official context relevant to it.

---

Looking for a different code? Search another status or error code.