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