What does Windows error code 15157 (ERROR_PRI_MERGE_RESOURCE_PACKAGE_REQUIRED) mean?

ERROR_PRI_MERGE_RESOURCE_PACKAGE_REQUIRED

Packages for a PRI file merge must include at least one resource package.

Windows assigns decimal 15157 and hexadecimal 0x00003B35 to ERROR_PRI_MERGE_RESOURCE_PACKAGE_REQUIRED. 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 operation includes at least one compatible resource package when using the merge workflow. The value describes a PRI merge request that contains a main package but no resource package; it does not prove that the whole domain, DNS service, network, servicing stack, application package, or operating system has failed.

Likely impact: Creating an empty synthetic resource package merely to satisfy the command would add useless deployment complexity. 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 request that contains a main package but no resource package.
• 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

• artifact discovery found only the main PRI.
• resource packages were not built.
• filters excluded all language or scale packages.
• the wrong command is used when no merge is necessary.

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 request that contains a main package but no resource package, including stable GUIDs, DNs, zone names, package identities, file hashes, policy names, or process identifiers as applicable.
3. prove the state boundary: the operation includes at least one compatible resource package when using the merge workflow.
4. collect main package identity and resource package inventory before restarting services, deleting objects, rebuilding packages, or changing policy.
5. correlate build configuration and target languages 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 main package identity.
• collect resource package inventory.
• collect build configuration and target languages.
• collect artifact filter logs.
• collect MakePri command mode.

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 15157 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 this Win32 error is to build and include the intended resource package, or skip the merge operation when only the main PRI is required.

Retry only after the recorded boundary changes and prior completion is known. Read-only discovery for this Win32 error 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 this Win32 error cannot repair malformed input, unsupported structure, identity collision, missing authority, or incompatible package metadata.

Telemetry and support fields

• record pri_merge_resource_package_required_operation — producing API, command, callback, or servicing phase.
• record pri_merge_resource_package_required_target — stable object, zone, policy, package, file, or account identity.
• record pri_merge_resource_package_required_state_before and pri_merge_resource_package_required_requested_state.
• record pri_merge_resource_package_required_first_status — earliest component-specific code before translation.
• record pri_merge_resource_package_required_server, pri_merge_resource_package_required_process, UTC timestamp, and correlation ID.

A support bundle for this Win32 error should include decimal 15157, hexadecimal 0x00003B35, 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_MAIN_PACKAGE_REQUIRED is the inverse missing-role condition 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 single-language build invokes the resource-package merge step even though it produced only the main PRI. The pipeline skips merge for that configuration. 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 request that contains a main package but no resource package. Monitoring for this Win32 error 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.