SQL Server 2008

  1. The merge process could not retrieve the last generation received from the Publisher. If this failure persists, reinitialize ...
  2. The merge process could not store conflict information for article '%1'. Check the publication properties to determine where ...
  3. The merge process could not store delete conflict information for an article. Check the publication properties to determine ...
  4. The merge process could not update the last generation received from the Publisher. If this failure persists, reinitialize ...
  5. The merge process could not update the last sent generation sent to the Publisher. If this failure persists, reinitialize ...
  6. The merge process detected a mismatch while evaluating the subscriber partition validation expression. The problem can be ...
  7. The merge process failed because it detected a mismatch between the replication metadata of the two replicas, such that some ...
  8. The merge process failed to enumerate changes in articles with parameterized row filters. If this failure continues, increase ...
  9. The merge process failed to execute a query because the query timed out. If this failure continues, increase the query timeout ...
  10. The merge process failed to get correct information about the Interactive Resolver component from the registry. Verify that ...
  11. The merge process failed when obtaining a new identity range for the subscriber, or failed to determine if the subscriber ...
  12. The merge process timed out while making a connection. Increase the login timeout for this process (-LoginTimeOut). When ...
  13. The merge process was unable to access metadata at the '%1' that was needed to retry an operation. When troubleshooting, ...
  14. The merge process was unable to access row metadata at the '%1'. When troubleshooting, restart the synchronization with verbose ...
  15. The merge process was unable to change generation history at the '%1'. When troubleshooting, restart the synchronization ...
  16. The merge process was unable to create a new generation at the '%1'. Troubleshoot by restarting the synchronization with ...
  17. The merge process was unable to deliver the snapshot to the Subscriber. If using Web synchronization, the merge process may ...
  18. The merge process was unable to perform data validation on article '%1'. Check for SQL Server errors in the Windows application ...
  19. The merge process was unable to verify the existence of a generation at the '%1'. If this failure persists, reinitialize ...
  20. The MERGE statement attempted to UPDATE or DELETE the same row more than once. This happens when a target row matches more ...
  21. The message cannot be sent because the message type '%1!s!' is marked SENT BY INTITIATOR in the contract, however this service ...
  22. The message cannot be sent because the message type '%1!s!' is marked SENT BY TARGET in the contract, however this service ...
  23. The message cannot be sent because the service queue '%1!s!' associated with the dialog is currently disabled and retention ...
  24. The message could not be delivered because it could not be classified. Enable broker message classification trace to see ...
  25. The message received was sent by a Target service, but the message type '%1!s!' is marked SENT BY INITIATOR in the contract. ...
  26. The message received was sent by the initiator of the conversation, but the message type '%1!s!' is marked SENT BY TARGET ...
  27. The message string being posted by the managed error infrastructure contains a bad format specification. This is an internal ...
  28. The message with default language Id of destination is not present in destination and hence attempting to transfer the same ...
  29. The message {0}:{1} on conversation {2}:{3} from service {4} and broker instance {5} to service {6} and broker instance {7} ...
  30. The metadata file name "%1!s!" is invalid. Verify that the file exists and that the SQL Server service account has access ...
  31. The metadata for the statically linked %{typename/}, with the name of '%{name/}', cannot be verified against the source object. ...
  32. The metadata of the following output columns does not match the metadata of the external columns with which the output columns ...
  33. The method "{0}" in class "{1}" marked as a server-level trigger cannot be auto deployed because server-level trigger deployment ...
  34. The method "{0}" in class "{1}" marked as a table-valued function must define a table definition in the SqlFunction attribute. ...
  35. The method '%1!s!' in class '%2!s!' in assembly '%3!s!' has some invalid arguments. Value of type '%4!s!' is not valid for ...
  36. The Microsoft Association algorithm uses correlation counting among attribute values or transaction items to analyze data. ...
  37. The Microsoft Association Rules algorithm builds rules describing which items are most likely to be appear together in a ...
  38. The Microsoft Clustering algorithm finds natural groupings of data in a multidimensional representation of attribute values. ...
  39. The Microsoft Clustering algorithm uses iterative techniques to group records from a dataset into clusters containing similar ...
  40. The Microsoft Decision Trees algorithm is a classification algorithm that works well for predictive modeling. The algorithm ...
  41. The Microsoft Distributed Transaction Coordinator (MS DTC) service could not be contacted. If you would like distributed ...
  42. The Microsoft Linear Regression algorithm is a regression algorithm that works well for regression modeling. This algorithm ...
  43. The Microsoft Logistic Regression algorithm is a regression algorithm that works well for regression modeling. This algorithm ...
  44. The Microsoft Naive Bayes algorithm considers all the input attributes to be independent and calculates the probability of ...
  45. The Microsoft Naive Bayes algorithm is a classification algorithm that is quick to build, and works well for predictive modeling. ...
  46. The Microsoft Neural Network algorithm uses a gradient method to optimize parameters of multilayer networks to predict multiple ...
  47. The Microsoft OLE DB Provider for Analysis Services {0} has not been installed or is not valid. Do you want to reset the ...
  48. The Microsoft OLE DB Provider for Analysis Services {0} is not installed or is not valid. Do you want to reset the connection ...
  49. The Microsoft Sequence Clustering algorithm combines two other data mining techniques: sequence analysis and clustering. ...
  50. The Microsoft Sequence Clustering algorithm is a combination of sequence analysis and clustering, which identifies clusters ...
  51. The Microsoft SQL Server 2008 Data Mining Add-ins for Office 2007 harness the power of the Analysis Services data mining ...
  52. The Microsoft SQL Server 2008 Data Mining Add-ins for Office 2007 will not work correctly if you do not complete all the ...
  53. The Microsoft SQL Server 2008 Enterprise Evaluation Edition is fully-functional 180-day trial software. Microsoft SQL Server ...
  54. The Microsoft Time Series algorithm analyzes time-related data to discover patterns based on time series analysis, such as ...
  55. The Microsoft Time Series algorithm uses a combination of ARIMA analysis and linear regression based on decision trees to ...
  56. The Microsoft Windows HTTP Services (WinHTTP) returned error code %1!d!. Unable to find a message in WinHTTP module corresponding ...
  57. The Migration Wizard cannot continue because the DSO client is not installed on this computer. Close the current Migration ...
  58. The minimum space required for the temporary objects is proportional to the size of the input dataset. Additional space beyond ...
  59. The minimum storage space required for the existing physical design structures (PDS) you have selected to keep is larger ...
  60. The minimum storage space required for the selected physical design structures exceeds the default storage space selected ...
  61. The MINIMUM_ITEMSET_SIZE parameter for the '%{modelname/}' model is not valid. MINIMUM_ITEMSET_SIZE must be between 1 and ...
  62. The MINIMUM_PROBABILITY parameter for the '%{modelname/}' model is not valid. MINIMUM_PROBABILITY must be between 0 and 1. ...
  63. The MINIMUM_SUPPORT parameter for the '%{modelname/}' model is not valid. MINIMUM_SUPPORT must be greater than or equal to ...
  64. The MINIMUM_SUPPORT parameter is negative in the '%{modelname/}' Microsoft Sequence Clustering model. MINIMUM_SUPPORT must ...
  65. The mining model , %{name/} is already trained and does not support incremental updates. Before using the INSERT INTO statement, ...
  66. The mining model cannot be added as a temporary model because the '{0}' mining structure is not temporary. Temporary models ...
  67. The mining model content you are currently viewing appears to be out of date. Would you like to refresh the mining model ...
  68. The mining model must be added as a temporary model because the '{0}' mining structure is temporary. Only temporary models ...
  69. The mining structure , %{name/} is already trained and does not support incremental updates. Before using the INSERT INTO ...
  70. The mining structure, '{0}', has a holdout greater than 0, therefore the '{1}' algorithm cannot be used in new mining models. ...
  71. The MINING_MODEL_CONTENT schema rowset describes the patterns that were discovered when the mining models were processed. ...
  72. The MINING_MODEL_XML schema rowset contains, in an XML format, the patterns that were discovered when the mining models were ...
  73. The MINING_SERVICE_PARAMETERS schema rowset identifies the parameters that can be used to create models for each type of ...
  74. The MinSimilarity threshold property on the Fuzzy Lookup transformation must be a value greater than or equal to 0.0 but ...
  75. The mirror and witness server instances cannot be the same instance of SQL Server. Select another instance as the witness ...