Error code search

The specified xml text was not well-formed. See Extended Error for more details.

The caller is trying to subscribe to a direct channel which is not allowed. The events for a direct channel go directly to a logfile and cannot be subscribed to.

Configuration error.

The query result is stale / invalid. This may be due to the log being cleared or rolling over after the query result was created. Users should handle this code by releasing the query result object and reissuing the query.

Query result is currently at an invalid position.

Registered MSXML doesn't support validation.

An expression can only be followed by a change of scope operation if it itself evaluates to a node set and is not already part of some other change of scope operation.

Can't perform a step operation from a term that does not represent an element set.

Left hand side arguments to binary operators must be either attributes, nodes or variables and right hand side arguments must be constants.

A step operation must involve either a node test or, in the case of a predicate, an algebraic expression against which to test each node in the node set identified by the preceding node set can be evaluated.

This data type is currently unsupported.

A syntax error occurred at position %1!d!.

This operator is unsupported by this implementation of the filter.

The token encountered was unexpected.

The requested operation cannot be performed over an enabled direct channel. The channel must first be disabled before performing the requested operation.

Channel property %1!s! contains invalid value. The value has invalid type, is outside of valid range, can't be updated or is not supported by this type of channel.

Publisher property %1!s! contains invalid value. The value has invalid type, is outside of valid range, can't be updated or is not supported by this type of publisher.

The channel fails to activate.

The xpath expression exceeded supported complexity. Please simplify it or split it into two or more simple expressions.

the message resource is present but the message is not found in the string/message table.

The message id for the desired message could not be found.

The substitution string for insert index (%1) could not be found.

The description string for parameter reference (%1) could not be found.

The maximum number of replacements has been reached.

The event definition could not be found for event id (%1).

The locale specific resource for the desired message is not present.

The resource is too old to be compatible.

The resource is too new to be compatible.

The channel at index %1!d! of the query can't be opened.

The publisher has been disabled and its resource is not available. This usually occurs when the publisher is in the process of being uninstalled or upgraded.

Attempted to create a numeric type that is outside of its valid range.

The subscription fails to activate.

The log of the subscription is in disabled state, and cannot be used to forward events to. The log must first be enabled before the subscription can be activated.

When forwarding events from local machine to itself, the query of the subscription can't contain target log of the subscription.

The credential store that is used to save credentials is full.

The credential used by this subscription can't be found in credential store.

No active channel is found for the query.

The resource loader failed to find MUI file.

The resource loader failed to load MUI file because the file fail to pass validation.

The RC Manifest is corrupted with garbage data or unsupported version or missing required item.