SQL Server 2016

  1. The merge process was unable to change generation history at the '%1'. When troubleshooting, restart the synchronization ...
  2. The merge process was unable to create a new generation at the '%1'. Troubleshoot by restarting the synchronization with ...
  3. The merge process was unable to deliver the snapshot to the Subscriber. If using Web synchronization, the merge process may ...
  4. The merge process was unable to perform data validation on article '%1'. Check for SQL Server errors in the Windows application ...
  5. The merge process was unable to verify the existence of a generation at the '%1'. If this failure persists, reinitialize ...
  6. The MERGE statement attempted to UPDATE or DELETE the same row more than once. This happens when a target row matches more ...
  7. The message cannot be sent because the message type '%1!s!' is marked SENT BY INTITIATOR in the contract, however this service ...
  8. The message cannot be sent because the message type '%1!s!' is marked SENT BY TARGET in the contract, however this service ...
  9. The message cannot be sent because the service queue '%1!s!' associated with the dialog is currently disabled and retention ...
  10. The message could not be delivered because it could not be classified. Enable broker message classification trace to see ...
  11. The message received was sent by a Target service, but the message type '%1!s!' is marked SENT BY INITIATOR in the contract. ...
  12. The message received was sent by the initiator of the conversation, but the message type '%1!s!' is marked SENT BY TARGET ...
  13. The message string being posted by the managed error infrastructure contains a bad format specification. This is an internal ...
  14. The message with default language Id of destination is not present in destination and hence attempting to transfer the same ...
  15. The message {0}:{1} on conversation {2}:{3} from service {4} and broker instance {5} to service {6} and broker instance {7} ...
  16. The metadata could not be determined because every code path results in an error; see previous errors for some of these. ...
  17. The metadata could not be determined because remote metadata discovery failed for statement '%1!s!' in procedure '%2!s!'. ...
  18. The metadata could not be determined because statement '%1!s!' contains dynamic SQL. Consider using the WITH RESULT SETS ...
  19. The metadata could not be determined because statement '%1!s!' in procedure '%2!s!' contains dynamic SQL. Consider using ...
  20. The metadata could not be determined because statement '%1!s!' in procedure '%2!s!' does not support metadata discovery. ...
  21. The metadata could not be determined because statement '%1!s!' in procedure '%2!s!' invokes a CLR procedure. Consider using ...
  22. The metadata could not be determined because statement '%1!s!' in procedure '%2!s!' invokes an extended stored procedure. ...
  23. The metadata could not be determined because statement '%1!s!' in procedure '%2!s!' uses an undeclared parameter in a context ...
  24. The metadata could not be determined because statement '%1!s!' invokes a CLR procedure. Consider using the WITH RESULT SETS ...
  25. The metadata could not be determined because statement '%1!s!' uses a temp table. Metadata discovery only supports temp tables ...
  26. The metadata could not be determined because statement '%1!s!' uses an undeclared parameter in a context that affects its ...
  27. The metadata could not be determined because the statement '%1!s!' in procedure '%2!s!' is not compatible with the statement ...
  28. The metadata could not be determined because the statement '%1!s!' in procedure '%2!s!' is not compatible with the statement ...
  29. The metadata could not be determined because the statement '%1!s!' in the main batch is not compatible with the statement ...
  30. The metadata database appears to be in an inconsistent state. A reference was found to a %{typename/} object with ID %{id/} ...
  31. The metadata discovery operation {0} returned invalid content. Verify that the connection string and permissions are correct. ...
  32. The metadata element reference starting with '{0}' cannot be resolved due to too many levels of indirection. The last metadata ...
  33. The metadata file name "%1!s!" is invalid. Verify that the file exists and that the SQL Server service account has access ...
  34. The metadata for the statically linked %{typename/}, with the name of '%{name/}', cannot be verified against the source object. ...
  35. The metadata of the following output columns does not match the metadata of the external columns with which the output columns ...
  36. The metadata stored by the ObjectContext is different than the metadata stored by the ObjectContext's connection. This can ...
  37. The method "{0}" in class "{1}" marked as a server-level trigger cannot be auto deployed because server-level trigger deployment ...
  38. The method "{0}" in class "{1}" marked as a table-valued function must define a table definition in the SqlFunction attribute. ...
  39. The method '%1!s!' in class '%2!s!' in assembly '%3!s!' has some invalid parameter declaration for parameter number %4!s!. ...
  40. The method 'First' can only be used as a final query operation. Consider using the method 'FirstOrDefault' in this instance ...
  41. The method 'Skip' is only supported for sorted input in LINQ to Entities. The method 'OrderBy' must be called before the ...
  42. The method result type '{0}' is not supported for this method argument. A method that produces an instance of a DbExpression-derived ...
  43. The method was called on the wrong buffer. Buffers that are not used for component output do not support this operation. ...
  44. The method {0} on type {1} in extension with Id {2} could not be converted to a TestCondition delegate for use in the condition ...
  45. The method {0} on type {1} in extension with Id {2} could not be converted to a TestCondition delegate for use in the condition ...
  46. The method {0} used as a CreateCustomModifiers raised an exception when it was called. The modifiers from the source could ...
  47. The methods 'Single' and 'SingleOrDefault' can only be used as a final query operation. Consider using the method 'FirstOrDefault' ...
  48. The Microsoft .NET Framework 2.0 or 4.0 must be installed on your computer before you can install ProductShortName]. Please ...
  49. The Microsoft .NET Framework 3.5 or 4.0 must be installed on your computer before you can install ProductShortName]. Please ...
  50. The Microsoft .NET Framework 3.5 SP1 must be installed on your computer before you can install ProductShortName]. Microsoft ...
  51. The Microsoft .NET Framework 4.0 must be installed on your computer before you can install ProductShortName]. Please install ...
  52. The Microsoft Assessment and Planning (MAP) Toolkit can help with your migration to SQL Server by giving you a complete network ...
  53. The Microsoft Association algorithm uses correlation counting among attribute values or transaction items to analyze data. ...
  54. The Microsoft Association Rules algorithm builds rules describing which items are most likely to be appear together in a ...
  55. The Microsoft Clustering algorithm finds natural groupings of data in a multidimensional representation of attribute values. ...
  56. The Microsoft Clustering algorithm uses iterative techniques to group records from a dataset into clusters containing similar ...
  57. The Microsoft Data Classification and Recommendation Service detects the categories of data you've inserted in your Excel ...
  58. The Microsoft Data Classification and Recommendation Service is not enabled, not finished categorizing your data or could ...
  59. The Microsoft Decision Trees algorithm is a classification algorithm that works well for predictive modeling. The algorithm ...
  60. The Microsoft Distributed Transaction Coordinator (MS DTC) service could not be contacted. If you would like distributed ...
  61. The Microsoft Linear Regression algorithm is a regression algorithm that works well for regression modeling. This algorithm ...
  62. The Microsoft Logistic Regression algorithm is a regression algorithm that works well for regression modeling. This algorithm ...
  63. The Microsoft Naive Bayes algorithm considers all the input attributes to be independent and calculates the probability of ...
  64. The Microsoft Naive Bayes algorithm is a classification algorithm that is quick to build, and works well for predictive modeling. ...
  65. The Microsoft Neural Network algorithm uses a gradient method to optimize parameters of multilayer networks to predict multiple ...
  66. The Microsoft OLE DB Provider for Analysis Services {0} is not installed or is not valid. Do you want to reset the connection ...
  67. The Microsoft Online Services Sign-In Assistant could not be found. Install it from http://go.microsoft.com/fwlink/?LinkID=507574. ...
  68. The Microsoft Online Services Sign-In Assistant encountered a user-related error that cannot be resolved. Possible reasons ...
  69. The Microsoft Online Services Sign-In Assistant encountered an error that might not occur if retried. Possible reasons include ...
  70. The Microsoft Online Services Sign-In Assistant installation is corrupted. Repair the installation from http://go.micros ...
  71. The Microsoft Sequence Clustering algorithm combines two other data mining techniques: sequence analysis and clustering. ...
  72. The Microsoft Sequence Clustering algorithm is a combination of sequence analysis and clustering, which identifies clusters ...
  73. The Microsoft SQL Server 2012 Data Mining Add-ins for Office harness the power of the Analysis Services data mining engine. ...
  74. The Microsoft SQL Server 2012 Data Mining Add-ins for Office will not work correctly if you do not complete all the necessary ...
  75. The Microsoft SQL Server 2012 Enterprise Evaluation Edition is fully-functional 180-day trial software. Microsoft SQL Server ...