| Previous | Next |
| IDS_MON_PARSE_ERR_1_PARAM | IDS_MON_SEMI_COLON |
IDS_MON_PARSE_ERR_2_PARAM
IDS_MON_PARSE_ERR_2_PARAM provides more structure than the generic parser message: the provider reports both the nearby token and what the grammar expected. That makes it suitable for diagnosing missing clause separators, delimiters, or ordering keywords in generated Windows Search SQL.
Use the expected token as a grammar clue
- Record both substituted message parameters; dropping the expected token removes the most useful part of the diagnostic.
- Check the local clause syntax and the preceding token before replacing the token named in the error.
- If SQL is assembled from optional fragments, verify that removing one fragment did not leave a comma, Boolean operator, or opening delimiter behind.
Windows Search supports a defined sequence of clauses rather than arbitrary SQL-92 statements. For example, SELECT requires at least one property column, and ORDER BY has its own comma-separated column syntax. The parser expectation should be compared against the specific clause being built. A catalog reset does not change the grammar and is not an appropriate response to a repeatable parse error.
Parser messages · SELECT syntax · ORDER BY syntax
Looking for a different code? Search another status or error code.