A custom element was found that has no registered XML parser, which means the XML is invalid. The element namespace is {0} and the name is {1}.
A CPU with the id of {0} does not exist on this system. Use sys.dm_os_schedulers to locate valid CPUs for this system or ...
A cryptographic operation failed. This error indicates a serious problem with SQL Server. Check the SQL Server error log ...
A cursor plan could not be generated for the given statement because the textptr() function was used on a LOB column from ...
A custom data source is defined specifically for this data-driven subscription and cannot be used by other data-driven subscriptions. ...
A custom element was found that has no registered XML parser, which means the XML is invalid. The element namespace is {0} ...
A custom property in the {0} {1}' has the name "{2}". Custom property names cannot be null and must be unique within the ...
A custom property named "%1!s!" is invalid because there is a stock property with that name. A custom property cannot have ...
A custom role cannot contain both system-level and non-system-level tasks in the same role definition. You must specify different ...
A data source does not provide features such as caching metadata, adding relationships, adding calculations, and adding annotations. ...