| Previous | Next |
| IDS_MON_MATCH_STRING | IDS_MON_VIEW_ALREADY_DEFINED |
IDS_MON_PROPERTY_NAME_IN_VIEW
IDS_MON_PROPERTY_NAME_IN_VIEW is a schema mutation conflict: the property name is already part of a view contract and cannot be redefined in the requested way. It is not a row-level failure and does not indicate that an indexed file has duplicate metadata.
Audit schema changes and deployment order
- Record the property and view definitions applied by the current application version.
- Check whether an upgrade attempts to redefine a property before replacing or migrating a legacy view that still references it.
- Make schema initialization idempotent; query execution code should not repeatedly issue property-definition commands.
For current Windows Search applications, prefer registered canonical properties and direct SystemIndex queries. The modern SELECT model treats properties as schema columns and returns NULL for a valid property missing from an item. A legacy view/property namespace conflict must be fixed in schema management or migration logic, not by recrawling files.
Legacy parser messages · Windows Search SELECT model · FROM SystemIndex
Looking for a different code? Search another status or error code.