SQL Server 2008 R2

  1. The machine is clustered, but the cluster is not online or cannot be accessed from one of its nodes. To continue determine ...
  2. The magnitude of the result of a function call was too big to fit in the result type, and overflowed the type of the operand. ...
  3. The main assembly has the same public key as the components installed by SQL Server Setup, you cannot use it as the main ...
  4. The main assembly has the same public key as the components installed by SQL Server Setup. You cannot use it as the main ...
  5. The Management Data Warehouse version "%s" is not supported by the current data collector. Please upgrade the Management ...
  6. The Management Data Warehouse version is incompatible with the current reports. Please contact the administrator for the ...
  7. The Many-to-many and Many-to-one conversion options are not valid because a single currency has been selected as the base ...
  8. The map, {0}, was detected in the report. SQL Server 2008 Reporting Services does not support map report items. Either reduce ...
  9. The mapping for column '%1' of article '%2', publication '%3' is not suitable for parameterized commands. Change the mapping ...
  10. The marked transaction "%1!s!" failed. A timeout occurred while attempting to place a mark in the log by committing the marked ...
  11. The Master Data Manager virtual directory name is not configured. To configure the directory, specify a name or use the default ...
  12. The Master Data Services database cannot be installed on the specified database server. Select a database server running ...
  13. The Master Data Services service must be running to configure the Windows service account. Do you want to start the service ...
  14. The Master Data Services Web service is not configured, so default values are provided. To accept the default values, click ...
  15. The master server operator will be created on the master server and each of the target servers. Multiserver jobs can only ...
  16. The matrix {1}' contains a different number of MatrixColumn elements than the number of StaticColumn elements. If the matrix ...
  17. The matrix {1}' contains a different number of MatrixRow elements than the number of StaticRow elements. If the matrix contains ...
  18. The matrix {1}' has a MatrixRow that contains a different number of MatrixCell elements than the number of StaticColumn elements ...
  19. The maximum allow integer identity value has been reached. Consider re-building the error tolerant index to use any gaps ...
  20. The maximum amount of time, in minutes, that Database Engine Tuning Advisor will spend tuning. In general, longer times produce ...
  21. The Maximum insert commit size property of the OLE DB destination "%1!s!" is set to 0. This property setting can cause the ...
  22. The Maximum insert commit size property of the OLE DB destination "{0}" is set to 0. This property setting can cause the ...
  23. The maximum number of days that a stored parameter can be stored. Valid values are 1 through 2,147,483,647. The default value ...
  24. The maximum number of snapshots that are stored for a report. Valid values are -1 and 1 through 2,147,483,647. If the value ...
  25. The maximum system-generated unique value for a duplicate group was exceeded for index with partition ID %1!s!. Dropping ...
  26. The maximum time, in seconds, that the principal server instance waits for a PING message from another instance in the mirroring ...
  27. The MAXIMUM_BUCKETS_FOR_CONTINUOUS_SPLIT parameter for the '%{modelname/}' model is not valid. MAXIMUM_BUCKETS_FOR_CONTINUOUS_SPLIT ...
  28. The MAXIMUM_CLUSTER_COUNT parameter is negative in the '%{modelname/}' Microsoft Sequence Clustering model. MAXIMUM_CLUSTER_COUNT ...
  29. The MAXIMUM_CONTINUOUS_INPUT_ATTRIBUTES parameter for the %{modelname/} model is not valid. MAXIMUM_CONTINUOUS_INPUT_ATTRIBUTES ...
  30. The MAXIMUM_INPUT_ATTRIBUTES parameter for the %{modelname/} model is not valid. MAXIMUM_INPUT_ATTRIBUTES must be at least ...
  31. The MAXIMUM_INPUT_ATTRIBUTES parameter for the '%{modelname/}' model is not valid. MAXIMUM_INPUT_ATTRIBUTES must be at least ...
  32. The MAXIMUM_INPUT_ATTRIBUTES parameter for the '%{modelname/}' model is not valid. MAXIMUM_INPUT_ATTRIBUTES must be greater ...
  33. The MAXIMUM_ITEMSET_COUNT parameter for the '%{modelname/}' model is not valid. MAXIMUM_ITEMSET_COUNT must be greater than ...
  34. The MAXIMUM_ITEMSET_SIZE parameter for the '%{modelname/}' model is not valid. MAXIMUM_ITEMSET_SIZE must be between 0 and ...
  35. The MAXIMUM_OUTPUT_ATTRIBUTES parameter for the %{modelname/} model is not valid. MAXIMUM_OUTPUT_ATTRIBUTES must be at least ...
  36. The MAXIMUM_OUTPUT_ATTRIBUTES parameter for the '%{modelname/}' model is not valid. MAXIMUM_OUTPUT_ATTRIBUTES must be at ...
  37. The MAXIMUM_STATES parameter for the '%{modelname/}' model is not supported. MAXIMUM_STATES must be 0, 2, or at most %d{Max/}. ...
  38. The MAXIMUM_STATES parameter for the '%{modelname/}' model is not valid. MAXIMUM_STATES must be 0, or between 2 and %d{Max/}. ...
  39. The MAXIMUM_STATES parameter for the '%{modelname/}' model is not valid. MAXIMUM_STATES must be between %d{Min/} and %d{Max/} ...
  40. The MDX script contains one or more syntax errors. New calculation properties cannot be specified until the errors are resolved. ...
  41. The measure group dimension with ID of '%{detaildimensionid/}', Name of '%{name/}' referenced by the '%{measure/}' measure ...
  42. The measure group has zero dimensional overlap with all of the other measure groups in the cube. Consider moving it to a ...
  43. The media family on device '%1!s!' is marked as nonappendable. Reissue the statement using the INIT option to overwrite the ...
  44. The media family on device '%1!s!' was created using Microsoft Tape Format version %2!s!.%3!s!. SQL Server supports version ...
  45. The media loaded on "%1!s!" is formatted to support %2!s! media families, but %3!s! media families are expected according ...
  46. The member count of the source attribute, '{0}', is the same as the member count of the related attribute, '{1}'. This attribute ...
  47. The Merge Agent could not apply a batch of changes at the '%1' using Web synchronization. Ensure that there is sufficient ...
  48. The Merge Agent could not connect to the URL '%1' during Web synchronization. Please verify that the URL, Internet login ...
  49. The Merge Agent could not reinitialize all subscriptions to a republishing Subscriber. When troubleshooting, restart the ...
  50. The Merge Agent could not retrieve version information from the Publisher. When troubleshooting, ensure that the Publisher ...
  51. The Merge Agent encountered an error when executing code in the '%2' method implemented in the business logic handler '%1'. ...
  52. The Merge Agent encountered an error when executing code in the CommitHandler method implemented in the business logic handler ...
  53. The Merge Agent encountered an error when executing code in the HandledChangeStates property implemented in the business ...
  54. The Merge Agent encountered an error when executing code in the Initialize method implemented in the business logic handler ...
  55. The Merge Agent encountered an error when executing code in the PhaseBegin method implemented in the business logic handler ...
  56. The merge agent encountered an error while initializing the Business Logic resolver. Verify that Microsoft.SqlServer.Rep ...
  57. The Merge Agent failed after detecting that retention-based metadata cleanup has deleted metadata at the Publisher for changes ...
  58. The Merge Agent failed after detecting that retention-based metadata cleanup has deleted metadata at the Subscriber for changes ...
  59. The Merge Agent failed because the schema of the article at the Publisher does not match the schema of the article at the ...
  60. The Merge Agent failed to add an application header to a message during Web synchronization. When troubleshooting, restart ...
  61. The Merge Agent failed to add or update the subscription entry in the distribution database. When troubleshooting, restart ...
  62. The Merge Agent failed to apply replication metadata. When troubleshooting, increase the -OutputVerboseLevel setting and ...
  63. The Merge Agent failed to connect to the Internet proxy server for user '%1' during Web synchronization. Ensure that the ...
  64. The Merge Agent failed to connect to the Web server or Internet proxy server using authentication mode %1. Ensure that the ...
  65. The Merge Agent failed to create a partitioned snapshot job for this subscription. When troubleshooting, use SQL Profiler ...
  66. The Merge Agent failed to delete a batch of rows because of the following error: %1. When troubleshooting, use SQL Profiler ...
  67. The Merge Agent failed to determine if the subscription has expired. When troubleshooting, use SQL Profiler or restart the ...
  68. The Merge Agent failed to determine the location of the partitioned snapshot generated for this subscription. When troubleshooting, ...
  69. The Merge Agent failed to drop the table used to store retry information. This can occur when there is too much activity ...
  70. The Merge Agent failed to enumerate retry information. This can occur when there is too much activity on the tempdb system ...
  71. The Merge Agent failed to generate a request message during Web synchronization. When troubleshooting, restart the Merge ...
  72. The Merge Agent failed to insert a batch of rows because of the following error: %1. When troubleshooting, use SQL Profiler ...
  73. The Merge Agent failed to locate the partitioned snapshot for this subscription in the expected location. If the publication ...
  74. The Merge Agent failed to obtain a new set of identity ranges for the Subscriber. When troubleshooting, restart the Merge ...
  75. The Merge Agent failed to retrieve article information for publication '%1'. Increase the -QueryTimeOut parameter and restart ...