| Previous | Next |
| ERROR_PRI_MERGE_MULTIPLE_MAIN_PACKAGES_NOT_ALLOWED | ERROR_PRI_MERGE_MAIN_PACKAGE_REQUIRED |
ERROR_PRI_MERGE_BUNDLE_PACKAGES_NOT_ALLOWED
Packages for a PRI file merge must not include bundle packages.
ERROR_PRI_MERGE_BUNDLE_PACKAGES_NOT_ALLOWED is Win32 error 15155 (0x00003B33).
Likely impact: Bundle metadata is not a substitute for the package-level resource schema expected by merge.
Typical causes
- a bundle PRI was supplied directly.
- the pipeline confuses bundle and package manifests.
- artifact discovery operates at the wrong directory level.
- a deployment bundle is reused as a merge input.
Troubleshooting steps
- Verify that the merge set contains the main package and resource packages rather than bundle-level package artifacts.
- Collect package type of each input and bundle and package manifest paths.
- Correlate artifact-selection logic with MakePri command line, input PRI inventory, package identities, schemas, file hashes, output path, tool version, and the first detailed merge diagnostic.
Useful evidence
- Collect intended deployment layout.
Recovery and retry
Extract or select the eligible constituent main and resource package PRI files instead of the bundle package.
Related errors
ERROR_PRI_MERGE_MULTIPLE_MAIN_PACKAGES_NOT_ALLOWED concerns count; this code rejects the bundle package type itself
Example
A packaging job points MakePri at the bundle output directory. Selecting the constituent package resources removes the unsupported bundle input.
References
Looking for a different code? Search another status or error code.