SQL Server 2012

  1. The MAXIMUM_INPUT_ATTRIBUTES parameter for the '%{modelname/}' model is not valid. MAXIMUM_INPUT_ATTRIBUTES must be at least ...
  2. The MAXIMUM_INPUT_ATTRIBUTES parameter for the '%{modelname/}' model is not valid. MAXIMUM_INPUT_ATTRIBUTES must be greater ...
  3. The MAXIMUM_ITEMSET_COUNT parameter for the '%{modelname/}' model is not valid. MAXIMUM_ITEMSET_COUNT must be greater than ...
  4. The MAXIMUM_ITEMSET_SIZE parameter for the '%{modelname/}' model is not valid. MAXIMUM_ITEMSET_SIZE must be between 0 and ...
  5. The MAXIMUM_OUTPUT_ATTRIBUTES parameter for the %{modelname/} model is not valid. MAXIMUM_OUTPUT_ATTRIBUTES must be at least ...
  6. The MAXIMUM_OUTPUT_ATTRIBUTES parameter for the '%{modelname/}' model is not valid. MAXIMUM_OUTPUT_ATTRIBUTES must be at ...
  7. The MAXIMUM_STATES parameter for the '%{modelname/}' model is not supported. MAXIMUM_STATES must be 0, 2, or at most %d{Max/}. ...
  8. The MAXIMUM_STATES parameter for the '%{modelname/}' model is not valid. MAXIMUM_STATES must be 0, or between 2 and %d{Max/}. ...
  9. The MAXIMUM_STATES parameter for the '%{modelname/}' model is not valid. MAXIMUM_STATES must be between %d{Min/} and %d{Max/} ...
  10. The MDX script contains one or more syntax errors. New calculation properties cannot be specified until the errors are resolved. ...
  11. The measure '%{deptable/}'[%{depcolumn/} depends on another measure named '%{srctable/}'[%{srccolumn/} which has an dependency ...
  12. The measure '%{deptable/}'[%{depcolumn/} depends on another measure named '%{srctable/}'[%{srccolumn/} which has an error: ...
  13. The measure group dimension with ID of '%{detaildimensionid/}', Name of '%{name/}' referenced by the '%{measure/}' measure ...
  14. The measure group has zero dimensional overlap with all of the other measure groups in the cube. Consider moving it to a ...
  15. The media family on device '%1!s!' is marked as nonappendable. Reissue the statement using the INIT option to overwrite the ...
  16. The media family on device '%1!s!' was created using Microsoft Tape Format version %2!s!.%3!s!. SQL Server supports version ...
  17. The media loaded on "%1!s!" is formatted to support %2!s! media families, but %3!s! media families are expected according ...
  18. The member cannot be saved. Either enter a code or have an administrator set up automatic code generation for the entity. ...
  19. The member code is already used by a member that was deleted. Pick a different code or ask an administrator to remove the ...
  20. The member count of the source attribute, '{0}', is the same as the member count of the related attribute, '{1}'. This attribute ...
  21. The member {0} could not be converted to a CreateCustomModifiers delegate as the method does not have a compatible signature. ...
  22. The Merge Agent could not apply a batch of changes at the '%1' using Web synchronization. Ensure that there is sufficient ...
  23. The Merge Agent could not connect to the URL '%1' during Web synchronization. Please verify that the URL, Internet login ...
  24. The Merge Agent could not reinitialize all subscriptions to a republishing Subscriber. When troubleshooting, restart the ...
  25. The Merge Agent could not retrieve version information from the Publisher. When troubleshooting, ensure that the Publisher ...
  26. The Merge Agent encountered an error when executing code in the '%2' method implemented in the business logic handler '%1'. ...
  27. The Merge Agent encountered an error when executing code in the CommitHandler method implemented in the business logic handler ...
  28. The Merge Agent encountered an error when executing code in the HandledChangeStates property implemented in the business ...
  29. The Merge Agent encountered an error when executing code in the Initialize method implemented in the business logic handler ...
  30. The Merge Agent encountered an error when executing code in the PhaseBegin method implemented in the business logic handler ...
  31. The merge agent encountered an error while initializing the Business Logic resolver. Verify that Microsoft.SqlServer.Rep ...
  32. The Merge Agent failed after detecting that retention-based metadata cleanup has deleted metadata at the Publisher for changes ...
  33. The Merge Agent failed after detecting that retention-based metadata cleanup has deleted metadata at the Subscriber for changes ...
  34. The Merge Agent failed because the schema of the article at the Publisher does not match the schema of the article at the ...
  35. The Merge Agent failed to add an application header to a message during Web synchronization. When troubleshooting, restart ...
  36. The Merge Agent failed to add or update the subscription entry in the distribution database. When troubleshooting, restart ...
  37. The Merge Agent failed to apply replication metadata. When troubleshooting, increase the -OutputVerboseLevel setting and ...
  38. The Merge Agent failed to connect to the Internet proxy server for user '%1' during Web synchronization. Ensure that the ...
  39. The Merge Agent failed to connect to the Web server or Internet proxy server using authentication mode %1. Ensure that the ...
  40. The Merge Agent failed to create a partitioned snapshot job for this subscription. When troubleshooting, use SQL Profiler ...
  41. The Merge Agent failed to delete a batch of rows because of the following error: %1. When troubleshooting, use SQL Profiler ...
  42. The Merge Agent failed to determine if the subscription has expired. When troubleshooting, use SQL Profiler or restart the ...
  43. The Merge Agent failed to determine the location of the partitioned snapshot generated for this subscription. When troubleshooting, ...
  44. The Merge Agent failed to drop the table used to store retry information. This can occur when there is too much activity ...
  45. The Merge Agent failed to enumerate retry information. This can occur when there is too much activity on the tempdb system ...
  46. The Merge Agent failed to generate a request message during Web synchronization. When troubleshooting, restart the Merge ...
  47. The Merge Agent failed to insert a batch of rows because of the following error: %1. When troubleshooting, use SQL Profiler ...
  48. The Merge Agent failed to locate the partitioned snapshot for this subscription in the expected location. If the publication ...
  49. The Merge Agent failed to obtain a new set of identity ranges for the Subscriber. When troubleshooting, restart the Merge ...
  50. The Merge Agent failed to retrieve article information for publication '%1'. Increase the -QueryTimeOut parameter and restart ...
  51. The Merge Agent failed to retrieve information about received generations for server subscriptions from the '%1' database. ...
  52. The Merge Agent failed to retrieve information for resolver '%1' with CLSID '%2'. When troubleshooting, use SQL Profiler ...
  53. The Merge Agent failed to retrieve Publisher properties. When troubleshooting, use SQL Profiler or restart the agent with ...
  54. The Merge Agent failed to retrieve replication state information from the '%1' database. When troubleshooting, use SQL Profiler ...
  55. The Merge Agent failed to retrieve the Publisher's comparison style. When troubleshooting, use SQL Profiler or restart the ...
  56. The Merge Agent failed to retrieve the Publisher's location identifier. When troubleshooting, use SQL Profiler or restart ...
  57. The Merge Agent failed to retrieve the snapshot schema script file '%1'. Run the Snapshot Agent to regenerate the snapshot ...
  58. The Merge Agent failed to update a batch of rows because of the following error: %1. When troubleshooting, use SQL Profiler ...
  59. The Merge Agent failed to update received generation information in the '%1' database. When troubleshooting, use SQL Profiler ...
  60. The Merge Agent failed to update replication state information in the '%1' database. When troubleshooting, use SQL Profiler ...
  61. The Merge Agent failed to update retry information. This can occur when there is too much activity on the tempdb system database. ...
  62. The Merge Agent failed to upgrade triggers, metadata and stored procedures on the Subscriber to versions compatible with ...
  63. The Merge Agent failed when initializing the Snapshot Agent to create the snapshot. When troubleshooting, check the Snapshot ...
  64. The Merge Agent failed while registering the publication id in the snapshot progress table. When troubleshooting, restart ...
  65. The Merge Agent has encountered an unanticipated empty string on line %1!d! of file %2. When troubleshooting, ensure that ...
  66. The Merge Agent has encountered an unanticipated null pointer on line %1!d! of file %2. When troubleshooting, ensure that ...
  67. The Merge Agent process could not write Web synchronization metadata in the message header. Verify that there is sufficient ...
  68. The Merge Agent received the following error status and message from the Internet Information Services (IIS) server during ...
  69. The Merge Agent was unable to connect to the Publisher using SQL Server Authentication. Ensure that the Publisher login used ...
  70. The Merge Agent was unable to determine if another subscription exists for the same partition. Restart the synchronization, ...
  71. The Merge Agent was unable to generate a partitioned snapshot for this subscription; either the Snapshot Agent failed to ...
  72. The Merge Agent was unable to mark the subscription as validated. When troubleshooting, use SQL Profiler or restart the agent ...
  73. The Merge Agent was unable to obtain a required lock on the table article '%1' needed to perform data validation. Restart ...
  74. The merge agent was unable to replicate one or more deletes to the '%1'. When troubleshooting, look for errors executing ...
  75. The Merge Agent was unable to start the SQL Server Agent job to generate the partitioned snapshot for this subscription. ...