SQL Server 2008

  1. A fatal error occurred in the .NET Framework common language runtime. SQL Server is shutting down. If the error recurs after ...
  2. A fatal error occurred while reading the input stream from the network. The maximum number of network packets in one request ...
  3. A fatal error occurred while reading the input stream from the network. The session will be terminated (input error: %1!s!, ...
  4. A fatal error occurred while trying to parse the script text. Verify that the script engine for the chosen language is installed ...
  5. A feature name is required to complete the merge. No feature name was provided. Database table: "{0}"; database keys = "{1}"; ...
  6. 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. ...
  7. A file activation error occurred. The physical file name '%1!s!' may be incorrect. Diagnose and correct additional errors, ...
  8. A file age has not been specified. In this configuration, this task will delete all the files of the type specified regardless ...
  9. A file named "{0}" already exists in the destination folder. To continue, do one of the following: remove the existing file, ...
  10. A file that is required cannot be installed because the cabinet file 2 has an invalid digital signature. This may indicate ...
  11. A file that is required cannot be installed because the cabinet file 2 is not digitally signed. This may indicate that the ...
  12. A FileStore error from WriteFile occurred. Physical file: %{PhysicalFile/}. Logical file: %{LogicalFile/}. %1[: %{External/}%]%[, ...
  13. A FileStore error occurred while a record was being locked. This may be a read failure. Physical file: %{PhysicalFile/}. ...
  14. A FileStore error occurred. Read/Write mode can only be changed from Write to Read. Physical file: %{PhysicalFile/}. Logical ...
  15. A FILESTREAM transaction context could not be initialized. This might be caused by a resource shortage. Retry the operation. ...
  16. A filter expression cannot be specified while creating multiple partitions. Run the wizard separately for each partition. ...
  17. A filter expression for the {0} '{1}' includes a variable reference. Variable values cannot be used in {0} filter expressions. ...
  18. A filter has been applied to the '{0}' characteristic using a different hierarchy than the one selected in the query. This ...
  19. A filtering type changed for the article. Any pending or future changes made in this article by a Subscriber in a given partition ...
  20. 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!'. ...
  21. A function has a parameter with an unsupported data type. The type of the parameter cannot be implicitly cast into a compatible ...
  22. A function parameter cannot be converted to a static value. The parameter must be static and cannot contain dynamic elements ...
  23. A general exception generated by Time Series algorithm while working with the mining model, %{modelname/} - likely due to ...
  24. A generation that was expected to be in %1!s!.dbo.MSmerge_genhistory could not be found. If this error occurred in a subscription ...
  25. A group expression for the {0} '{1}' includes a variable reference. Variable values cannot be used in group expressions. ...
  26. A group expression for the {0} '{1}' includes an aggregate function. Aggregate functions cannot be used in group expressions. ...
  27. A group expression for the {0} {1}' includes the aggregate function Previous. Previous cannot be used in group expressions. ...
  28. A group expression for the {0} {1}' includes the aggregate function RunningValue. RunningValue cannot be used in group expressions. ...
  29. A group expression for the {0} {1}' uses the RowNumber function with a scope parameter that is not valid. When used in a ...
  30. A grouping filter expression for the {0} {1}' uses aggregate function First, Last or Previous. These aggregate functions ...
  31. A grouping in the {0} {1}' has Parent and more than one group expressions. Parent is only allowed if the grouping has exactly ...
  32. 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. ...
  33. A job step received an error at line {0} in a PowerShell script. The corresponding line is '{1}'. Correct the script and ...
  34. A key column is based on the DataColumn {0}].[{1} of type GUID. This is not supported, create a named column where you cast ...
  35. A large constant was found in the request, please be aware that these are now types as Large Value Types instead of legacy ...
  36. 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 ...
  37. A line chart displays a series as a set of points connected by a single line. Line charts are used to represent large amounts ...
  38. A linked measure group can be used only with linked dimensions from the same source database. It is recommended that you ...
  39. A list of actions for the selected items cannot be obtained because of the following error. {0} This error may have occurred ...
  40. A logical record relationship, specified by the @filter_type parameter, requires a one-to-one or a one-to-many join from ...
  41. A loop involving the member with the key %1[%{key/}%]%[, %{key/}%], was detected in the parent-child relationship between ...
  42. A mapping in the file, "%1!s!", is not valid. Values cannot be null or empty. The tag is "%2!s!", the key is "%3!s!", and ...
  43. A mapping in the file, "{0}", is not valid. Values cannot be null or empty. The tag is "{1}", the key is "{2}", and the value ...
  44. A meaningful named query cannot be generated based on the current selection. Select a chart series, chart series value, or ...
  45. A measure group with writeback partitions cannot have measures bound to unsigned columns or measures whose AggregateFunction ...
  46. A measure with 'ByAccount' aggregation function requires exactly one dimension with Type = 'Accounts' with exactly one attribute ...
  47. A member in the '%{attr/}' attribute has the unsupported '%{uop/}' unary operator value. Only the following unary operator ...
  48. A member of the db_owner role must use the database diagramming functionality in order to setup the required database diagramming ...
  49. A member of the db_owner role must use the Visual Studio 2005 database diagramming functionality in order to set up the required ...
  50. A merge conflict occurred during the merge. Database table: "{0}"'; database keys = "{1}"; module table: "{2}"; module keys: ...
  51. A MERGE statement is not valid if it triggers both the 'ON DELETE SET NULL' and 'ON UPDATE CASCADE' actions for a referential ...
  52. A message of type '%1!s!' failed XML validation on the target service. %2!s! This occurred in the message with Conversation ...
  53. A message of type '%1!s!' was received and failed XML validation. %2!s! This occurred in the message with Conversation ID ...
  54. A Mining Accuracy Chart cannot be displayed for mining model column content types of continuous and discrete at the same ...
  55. A mining structure with this name already exists. You can accept the suggested mining structure name, {0}, or type a new ...
  56. A model exception has occurred: Distribution for the '{0}' cluster has a shape different from its marginal distribution. ...
  57. A model with this name already exists. You can accept the suggested model name, {0}, or type a new model name. Then, click ...
  58. A Multidimensional Expressions (MDX) expression that defines the default member for the attribute. If no default member is ...
  59. A name column must be specified when a composite key is used. If not already present, it is recommended to create a named ...
  60. A name for the '%{strAttrID/}' attribute ID was not specified. Attribute names must always be specified for new attributes. ...
  61. A name that indicates which culture should be used when presenting culturally-sensitive data, such as formatting numbers ...
  62. A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed in a SELECT statement that is not the immediate source ...
  63. A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed inside another nested INSERT, UPDATE, DELETE, or MERGE ...
  64. A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed on either side of a UNION, INTERSECT, or EXCEPT operator. ...
  65. A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found ...
  66. A new column with name %1!s! has been added to the external database table. Use advanced editor to refresh available destination ...
  67. A new connection was established with the same peer. This connection lost the arbitration and it will be closed. All traffic ...
  68. A new connection was rejected because the maximum number of connections on session ID %1!s! has been reached. Close an existing ...
  69. A non-key column in time series model, %{modelname/}, has date/time/timestamp data type. This is not allowed. Recommend modeling ...
  70. A non-parent attribute has been specified as the 'Account' type. If you proceed with this selection, it may not be possible ...
  71. A Notification Services instance cannot be hosted by SQL Server versions earlier than SQL Server 2000. When you register ...
  72. A null attribute key was converted to an unknown member when processing: %1[Table: '%{Table/}', Column: '%{Column/}', Value: ...
  73. A null attribute key was converted to an unknown member. Attribute: %{Property/} of Dimension: %{Dimension/} from Database: ...
  74. A number from 1-5 indicating the current memory state of the server. 1:No pressure, 2:Low Pressure,3:Medium Pressure,4:High ...
  75. A page that should have been constant has changed (expected checksum: %1!s!, actual checksum: %2!s!, database %3!s!, file ...