SQL Server 2012

  1. A failure occurred while reading Metadata information from a Table-Valued Parameter Rowset. Failure occurred in the method ...
  2. A failure occurred while reading Metadata information from a Table-Valued Parameter Rowset. One of NUMBER, TYPE, FLAGS or ...
  3. A failure occurred while reading Metadata information from a Table-Valued Parameter Rowset. One of user-defined type catalog/schema/typename ...
  4. A failure occurred while reading Metadata information from a Table-Valued Parameter Rowset. One of xml type catalog/schema/"schema ...
  5. A failure occurred while reading Metadata information from a Table-Valued Parameter Rowset. The number of columns in the ...
  6. A failure occurred while reading Metadata information from a Table-Valued Parameter Rowset. The OLE DB type (%1!u!) for Column ...
  7. A failure occurred while sending row data for a Table-Valued Parameter Rowset. Error occurred in method IRowset::GetData ...
  8. A failure occurred while sending row data for a Table-Valued Parameter Rowset. Error occurred in method IRowset::GetNextRows ...
  9. A failure occurred while sending row data for a Table-Valued Parameter Rowset. Error occurred in method IRowset::ReleaseRows ...
  10. A failure occurred while sending row data for a Table-Valued Parameter Rowset. Error occurred in method IRowset::RestartPosition ...
  11. A failure occurred while sending row data for a Table-Valued Parameter Rowset. No data was provided for Row %1!Iu!, Column ...
  12. A failure occurred while sending row data for a Table-Valued Parameter Rowset. Null value was provided for Row %1!Iu!, Column ...
  13. A failure occurred while sending row data for a Table-Valued Parameter Rowset. The data provided for Row %1!Iu!, Column %2!Iu! ...
  14. A failure occurred while sending row data for a Table-Valued Parameter Rowset. The data provided for Row %1!Iu!, Column %2!Iu! ...
  15. A failure occurred while sending row data for a Table-Valued Parameter Rowset. The failure occurred at Row %1!Iu!, Column ...
  16. A failure occurred while sending row data for a Table-Valued Parameter Rowset. The length (%1!Iu!) for Row %2!Iu!, Column ...
  17. A failure occurred while sending row data for a Table-Valued Parameter Rowset. The length (%1!Iu!) for Row %2!Iu!, Column ...
  18. A failure occurred while sending row data for a Table-Valued Parameter Rowset. The length was not provided by the consumer ...
  19. A failure occurred while sending row data for a Table-Valued Parameter Rowset. The provider failed to convert data for Row ...
  20. A failure occurred while sending row data for a Table-Valued Parameter Rowset. The status (%1!u!) provided for Row %2!Iu!, ...
  21. A failure occurred while the file store was being cleared. Physical file: %{PhysicalFile/}. Logical file: %{LogicalFile/}. ...
  22. A fatal error occurred during a full-text population and caused the population to be cancelled. Population type is: %1!s!; ...
  23. A fatal error occurred in the .NET Framework common language runtime. SQL Server is shutting down. If the error recurs after ...
  24. A fatal error occurred while reading the input stream from the network. The maximum number of network packets in one request ...
  25. A fatal error occurred while reading the input stream from the network. The session will be terminated (input error: %1!s!, ...
  26. A fatal error occurred while trying to parse the script text. Verify that the script engine for the chosen language is installed ...
  27. A feature name is required to complete the merge. No feature name was provided. Database table: "{0}"; database keys = "{1}"; ...
  28. A feature required by the current database configuration for operation is not available in the current client library version. ...
  29. A field in the dataset {4}' has the name {3}'. Field names must be greater than 0 and less than or equal to {5} characters. ...
  30. A field that is referenced in either a group expression or a sort expression is missing from the query result set. The missing ...
  31. A file activation error occurred. The physical file name '%1!s!' may be incorrect. Diagnose and correct additional errors, ...
  32. A file age has not been specified. In this configuration, this task will delete all the files of the type specified regardless ...
  33. A file named "{0}" already exists in the destination folder. To continue, do one of the following: remove the existing file, ...
  34. A file of a different type already exists with the same name. Report Builder does not support having more than one file with ...
  35. A file store is full. It contains the maximum number of records allowed for its data type. If the file is a string store ...
  36. A file that is required cannot be installed because the cabinet file 2 has an invalid digital signature. This may indicate ...
  37. A file that is required cannot be installed because the cabinet file 2 is not digitally signed. This may indicate that the ...
  38. A file with name '{0}' already exists and is open in an editor. Please give a unique name to the item you are adding, or ...
  39. A FileStore error occurred while a record was being locked. This may be a read failure. Physical file: %{PhysicalFile/}. ...
  40. A FileStore error occurred. Read/Write mode can only be changed from Write to Read. Physical file: %{PhysicalFile/}. Logical ...
  41. A FILESTREAM transaction context could not be initialized. This might be caused by a resource shortage. Retry the operation. ...
  42. A filter expression cannot be specified while creating multiple partitions. Run the wizard separately for each partition. ...
  43. A filter expression for the {0} '{1}' includes a variable reference. Variable values cannot be used in {0} filter expressions. ...
  44. A filter has been applied to the '{0}' characteristic using a different hierarchy than the one selected in the query. This ...
  45. A filter value in the filter for {0} {1}' specifies a data type that is not supported by the '{3}' operator. Verify that ...
  46. A filtering type changed for the article. Any pending or future changes made in this article by a Subscriber in a given partition ...
  47. A full-text retry pass of %1!s! population started for table or indexed view '%2!s!'. Table or indexed view ID is '%3!s!'. ...
  48. A function '%{function/}' has been used in a True/False expression that is used as a table filter expression. This is not ...
  49. A function has a parameter with an unsupported data type. The type of the parameter cannot be implicitly cast into a compatible ...
  50. A function parameter cannot be converted to a static value. The parameter must be static and cannot contain dynamic elements ...
  51. A general exception generated by Time Series algorithm while working with the mining model, %{modelname/} - likely due to ...
  52. A generation that was expected to be in %1!s!.dbo.MSmerge_genhistory could not be found. If this error occurred in a subscription ...
  53. A group expression for the {0} '{1}' includes an aggregate function. Aggregate functions cannot be used in group expressions. ...
  54. A group expression for the {0} {1}' includes the Previous aggregate function. Previous cannot be used in group expressions. ...
  55. A group expression for the {0} {1}' includes the RunningValue aggregate function. RunningValue cannot be used in group expressions. ...
  56. A group expression for the {0} {1}' uses the RowNumber function with a scope parameter that is not valid. When used in a ...
  57. A grouping filter expression for the {0} {1}' uses aggregate function First, Last or Previous. These aggregate functions ...
  58. A grouping in the {0} {1}' has Parent and more than one group expressions. Parent is only allowed if the grouping has exactly ...
  59. A grouping in the {0} {1}' has the name {3}'. Grouping names must be greater than 0 and less than or equal to {3} characters. ...
  60. A high load-to-connection percentage indicates the server is loading a disproportionate number of workbooks relative to the ...
  61. A job step received an error at line {0} in a PowerShell script. The corresponding line is '{1}'. Correct the script and ...
  62. A job step received an error in a PowerShell script. Correct the script and reschedule the job. The error information returned ...
  63. A job step received an error while registering SQL Server snap - in {0}. Verify that the SQL Server snap - in was installed ...
  64. A key column is based on the DataColumn {0}].[{1} of type GUID. This is not supported, create a named column where you cast ...
  65. A key for type '{0}' cannot be created because parent relation '{1}' does not allow it to determine the parent type. The ...
  66. A large constant was found in the request, please be aware that these are now types as Large Value Types instead of legacy ...
  67. A large number of tables are selected for copying, and the wizard may not be able to copy all the tables in a session. Select ...
  68. A line chart displays a series as a set of points connected by a single line. Line charts are used to represent large amounts ...
  69. A linked measure group can be used only with linked dimensions from the same source database. It is recommended that you ...
  70. A list of actions for the selected items cannot be obtained because of the following error. {0} This error may have occurred ...
  71. A list of additional reports and other files related to the PowerPivot management data. Additional files can also be added ...
  72. A load event occurs when PowerPivot data is loaded into memory in response to a user request for that data. Data can be loaded ...
  73. A locale ID that is not supported was specified for a column with 'STATISTICAL_SEMANTICS'. Please verify that the locale ...
  74. A logical record relationship, specified by the @filter_type parameter, requires a one-to-one or a one-to-many join from ...
  75. A logical value: if TRUE, do not display commas in the returned text; if FALSE or omitted, display commas in the returned ...