| Previous | Next |
| ERROR_MRM_DIRECT_REF_TO_NON_DEFAULT_RESOURCE | ERROR_PRI_MERGE_VERSION_MISMATCH |
ERROR_MRM_GENERATION_COUNT_MISMATCH
ERROR_MRM_GENERATION_COUNT_MISMATCH means a resource map was regenerated after a query string or lookup state was created. The previous query is no longer valid for the current map generation.
Discard cached lookup state created against the old map and recreate the query after the resource map update. Persisting handles or query strings across PRI regeneration can reproduce the mismatch even when the new index is valid.
What to check
- Recreate the resource query after loading, unloading, or regenerating a PRI map.
- Avoid caching resource-map query state across package/resource reload operations.
- Check lifecycle code for concurrent refreshes of the resource index or runtime resource context.
Microsoft: Manage resources with MRT Core
Looking for a different code? Search another status or error code.