SQL Server 2016

  1. The conversation endpoint with ID '%1!s!' and is_initiator: %2!s! is referencing the invalid conversation group '%3!s!'. ...
  2. The conversation endpoint with ID '%1!s!' and is_initiator: %2!s! is referencing the invalid conversation handle '%3!s!'. ...
  3. The conversation endpoint with ID '%1!s!' and is_initiator: %2!s! is referencing the missing service contract with ID %3!s!. ...
  4. The conversation with ID '%1!s!' and initiator: %2!s! references a missing conversation group '%3!s!'. Run DBCC CHECKDB to ...
  5. The conversion of the result of the expression"%1!s!" from type "%2!s!" to a supported type failed with error code 3!8.8X!. ...
  6. The copy columns, "%1!s!" and "%2!s!", do not have equal data types or are not trivially convertible string types. This occurs ...
  7. The CPU architecture of installing feature(s) is different than the instance specified. To continue, add features to this ...
  8. The CPU architectures of feature(s) you selected to removed are different then Setup. To remove these features, Setup architecture ...
  9. The CPU architectures of upgrading feature(s) and this installation program are different. To upgrade these features, Setup ...
  10. The CPU platform for the {0} feature is inconsistent between the nodes of the cluster. To cluster an instance, the platform ...
  11. The CREATE %1!s! statement is missing the required parameter '%2!s!'. Validate the statement against the index-creation syntax. ...
  12. The Create command cannot be executed since it is attempting to create an object in a read only database with the name of ...
  13. The CREATE DATABASE statement failed. The primary file must be at least %1!s! MB to accommodate a copy of the model database. ...
  14. The CREATE INDEX or REBUILD INDEX statement failed for index '%1!s!' on table '%2!s!' because a distribution policy cannot ...
  15. The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name '%1!s!' and the index ...
  16. The Create Utility Control Point Wizard will help you to create a UCP on an instance of SQL Server to manage your SQL Server ...
  17. The CreateFolderOnSQLServer method has encountered OLE DB error code 1!8.8X! (%2!s!) The SQL statement issued has failed. ...
  18. The credential '{0}' specified either does not exist or does not have the authentication information to access the storage. ...
  19. The credential created might not be able to decrypt the database master key. Please ensure a database master key exists for ...
  20. The credential identity does not match the selected storage account. Please select a different credential or create a new ...
  21. The credentials used to connect to the data source for a tabular database in DirectQuery mode. These credentials are not ...
  22. The credentials you provided for the account ({0}) are not valid. To continue, enter a valid windows domain user name and ...
  23. The credentials you provided for the Analysis Services service are invalid. To continue, provide a valid account and password ...
  24. The credentials you provided for the Full-text service are invalid. To continue, provide a valid account and password for ...
  25. The credentials you provided for the Integration Services service are invalid. To continue, provide a valid account and password ...
  26. The credentials you provided for the Launchpad service are invalid. To continue, provide a valid account and password for ...
  27. The credentials you provided for the Reporting Services service are invalid. To continue, provide a valid account and password ...
  28. The credentials you provided for the SQL Server Agent service are invalid. To continue, provide a valid account and password ...
  29. The credentials you type need to have sufficient permissions to grant execute permissions to the RSExecRole for objects in ...
  30. The Cross Rowset check between clustered columnstore index and nonclustered index (object ID %1!s!, index ID %2!s!, partition ...
  31. The Cross Rowset check on nonclustered columnstore index object ID %1!s!, index ID %2!s!, partition number %3!s! failed. ...
  32. The cryptographic signature of the package failed verification due to error 1!8.8X! "%2!s!". This occurs when the signature ...
  33. The cube already contains a Key Performance Indicator (KPI) with the specified name. Provide a different name for the KPI. ...
  34. The cube attribute with ID '%{propertyid/}' and Name '%{propertyname/}' referenced by the cube dimension '%{cubedimension/}' ...
  35. The cube cannot be browsed. Either structural changes have been made to the cube that require it to be reprocessed, or the ...
  36. The cube contains a large number of measure groups. To improve performance, consider consolidating them into fewer measure ...
  37. The cube contains a semiadditive measure '%{name/}'. The time dimension in the relevant measure group contains more than ...
  38. The cube dimension '{0}' is not included as a fact dimension in the measure group '{1}'. All fact dimensions in a measure ...
  39. The cube dimensions, '{0}' and '{1}', do not have distinct hierarchy and attribute hierarchy names. The HierarchyUniqueNameStyle ...
  40. The cube does not have a source. The Currency Conversion Wizard can only be run if a source is present in the data source ...
  41. The cube has been reprocessed on the server. To prevent possible browsing errors, click *$*Reconnect*$*. To hide this message, ...
  42. The cube has been updated on the server. To prevent possible browsing errors, click *$*Reconnect*$*. To hide this message, ...
  43. The CUBE() and ROLLUP() grouping constructs are not allowed in the current compatibility mode. They are only allowed in 100 ...
  44. The Culture '%{culture/}' has more than one object translation defined for the object with ID: '%lu{objectID/}' and ObjectType: ...
  45. The cumulative lengths of the columns specified in the exact match joins exceeds the 900 byte limit for index keys. Fuzzy ...
  46. The current action cannot be completed. The user data source credentials do not meet the requirements to run this report ...
  47. The current action cannot be completed. The user data source credentials do not meet the requirements to run this report ...
  48. The current affinity setting specifies the use of more than 64 processors. Before you use sp_configure to change affinity ...
  49. The current amount of time, in milliseconds, elapsed from when transactions are applied at the Publisher to when they are ...
  50. The current amount of time, in milliseconds, elapsed from when transactions are delivered to the Distributor to when they ...
  51. The current Analysis Services connection does not point to a valid catalog. Click the 'Connection' button on the Analyze ...
  52. The current deployment mode does not support the use of parameters. To use parameters, convert the project to the Project ...
  53. The current edition of SQL Server cannot be upgraded because some of the specified features are not supported in the SQL ...
  54. The current event was not reported to the Windows Events log. Operating system error = %1!s!. You may need to clear the Windows ...
  55. The current implementation of memstore's SetSize() doesn't support increasing the size of the stream; store was requested ...
  56. The current implementation of memstore's SetSize() supports up to 4GB only; store was requested to set '%d{requestedSize/}' ...
  57. The current instance of SQL Server cannot be upgraded because it is running on a domain contoller and the service account ...
  58. The current instance of SQL Server cannot be upgraded because there are databases attached with FILESTREAM filegroups and ...
  59. The current instance of the SQL Server Analysis Services service cannot be upgraded because the Analysis Services service ...
  60. The current log shipping configuration is not functional because the required backup job cannot be found. You must drop the ...
  61. The current login '%1!s!' is not in the publication access list (PAL) of any publication at Publisher '%2!s!'. Use a login ...
  62. The current login does not have permissions to set the database owner to '{0}' The database was created successfully however. ...
  63. The current master key cannot be decrypted. If this is a database master key, you should attempt to open it in the session ...
  64. The current model can only be expressed when the client is requesting tabular view metadata with VERSION restriction of 2.0 ...
  65. The current monitor is not functional because the required alert job cannot be found. You can recreate the alert job by running ...
  66. The current node that is being added does not require any additional or new IP addresses. The IP addresses and subnets shown ...
  67. The current node {0} is at patch level {1}], which is lower than that of active node {2}: patch level {3}]. After completing ...
  68. The current notification method is set to SQL Server, but the data source is not a SQL Server. This method is only valid ...
  69. The current notification method is set to SQL Server, but the data source is not a SQL Server. This method is only valid ...
  70. The current notification method is set to SQL Server. This option requires that either the data source or the Analysis Services ...
  71. The current notification method is set to SQL Server. This option requires that either the data source or the Analysis Services ...
  72. The current notification method is set to SQL Server. This option requires that either the data source or the Analysis Services ...
  73. The current notification method is set to SQL Server. This option requires that either the data source or the Analysis Services ...
  74. The current number of message fragments received in transport receive I/O operations that have not been enqueued (or rejected) ...
  75. The current number of message fragments that are being marshalled, or marshalled and ready to be sent via the transport layer. ...