The input trace file is not valid. Make sure that the trace file exists on controller(not on the Universal Naming Convention (UNC) path) and that the file is not corrupt.
The Input column collection for Data Flow element {0} is corrupted. Cross lineage information for destination column {1} ...
The input column lineage ID "%1!s!" referenced by property "%2!s!" on output column "%3!s!" could not be located in the input ...
The input or output type of user-defined aggregate/operator '{0}' doesn't match the extension method definition, whose input ...
The input trace file is missing, not valid or corrupt. Make sure that a local path on the controller is specified in the ...
The input trace file is not valid. Make sure that the trace file exists on controller(not on the Universal Naming Convention ...
The input XML does not conform to the schema. XML grammar is described in the API documentation. For XML in reports, refer ...
The insert column list used in the MERGE statement cannot contain multi-part identifiers. Use single part identifiers instead. ...
The insert failed. It conflicted with an identity range check constraint in database '%1!s!', replicated table '%2!s!'%3!s!%4!s!%5!s!. ...
The INSERT INTO statement can be used only for mining models that have no siblings in the same mining structure. Try using ...