SQL Server 2016

  1. The CanProcess method of the component (ID: %1!d!) returned false for all inputs. No further input data can be processed. ...
  2. The capture job cannot be used by Change Data Capture to extract changes from the log when transactional replication is also ...
  3. The Cardinality property for the {0} is One, but the default value Expression for "{1}" returns a set. The default value ...
  4. The cartridge for the '%{datasource}' datasource does not support table-aliasing, but querying a parent-child dimension requires ...
  5. The cartridge generated a statement that is not valid because more than one text statement was generated, the statement was ...
  6. The case dimension should be the same dimension referenced by the key column of the mining model on which the source dimension ...
  7. The case filter for the mining model, '%{model/}' , is invalid. The specified filter expression evaluates to the following ...
  8. The case filter is invalid because the referenced column '%{ColumnName/}' has content type KEY. You cannot filter on a key ...
  9. The case-sensitive or binary collation '%1!s!' cannot be used with the COLLATE_FILENAME option. Change the collation to a ...
  10. The CASELIKELIHOOD_NORMALIZATION_METHOD parameter for the '%{modelname/}' model is not valid. CASELIKELIHOOD_NORMALIZATION_METHOD ...
  11. The cases cache of the model has been cleared by either setting ClearAfterProcessing cache mode or by issuing a direct DMX ...
  12. The cast to value type '{0}' failed because the materialized value is null. Either the result type's generic parameter or ...
  13. The catalog backup file '{0}' could not be accessed. Make sure the database file exists, and the SQL Server service account ...
  14. The catalog database is in SharePoint integrated mode. That is no longer supported by this instance of Reporting Services. ...
  15. The catalog protects data using encryption. A key is needed for this encryption. Enter a password to protect the encryption ...
  16. The category selected has the {0} data type. However, the column selected has the {1} data type. This may cause unexpected ...
  17. The cell writeback operation cannot be committed, because the '%{measuregroup/}' measure group does not have a write-enabled ...
  18. The cell writeback operation has a non-trivial slice and measure expression, on the '%{measuregroup/}' measure group. Cell ...
  19. The cell writeback operation has a non-trivial slice on the '%{cubedimension/}' dimension, which is not associated with the ...
  20. The cell writeback operation has a non-trivial slice on the '%{measuregroupdimension/}' data mining measure group dimension, ...
  21. The cell writeback operation has a non-trivial slice on the '%{measuregroupdimension/}' many-to-many measure group dimension, ...
  22. The cell writeback operation has a non-trivial slice on the '%{measuregroupdimension/}' reference measure group dimension, ...
  23. The cell writeback operation has failed because the underlying relational storage has a table whose number of columns differ ...
  24. The cell writeback operation has the non-sum measure named '%{measure/}' as the current coordinate, which is not allowed. ...
  25. The certificate '%1!s!' is not valid for endpoint authentication. The certificate must have a private key encrypted with ...
  26. The certificate and symmetric key used to encrypt project '%1!s!' does not exist or you do not have sufficient permissions. ...
  27. The certificate associated with the specified column master key is invalid for encrypting a column encryption key, or you ...
  28. The certificate specified by name in MY store cannot be found (error: %1!s!). This occurs in CPackage::LoadUserCertificateByName. ...
  29. The certificate used by server {0} for authentication is not deployed on server {1}. The Public role will be checked for ...
  30. The certificate, asymmetric key, or private key file is not valid or does not exist; or you do not have permissions for it. ...
  31. The change cannot be tracked because the state of the object changed from '{0}' to '{1}' since the previous call to EntityMemberChanging ...
  32. The Change Data Capture '%1!s!' job does not exist in the system table 'msdb.dbo.cdc_jobs'. Use the stored procedure 'sys.sp_cdc_add_job' ...
  33. The Change Data Capture job table containing job information for database '%1!s!' cannot be found in the msdb system database. ...
  34. The change for the row with article nickname %1!d! (%2), rowguidcol {%3} could not be applied at the destination. Further ...
  35. The change role completion notification for logical server '%1!s!', ag id '%2!s!', local database id '%3!s!' was ignored ...
  36. The change to the attribute group cannot be saved. The entity is the target of a sync relationship. You use the sync process ...
  37. The change to the entity member(s) cannot be saved. The entity version is the target of a sync relationship. You use the ...
  38. The changed value in this cell was not recognized as valid. .Net Framework Data Type: {0} Error Message: {1} Type a value ...
  39. The changes contained in the message downloaded from Publisher '%1' will be applied after having collected and displayed ...
  40. The changes that were uploaded to the Publisher are being discarded since the Subscriber has been marked for reinitialization. ...
  41. The changes to the database were committed successfully, but an error occurred while updating the object context. The ObjectContext ...
  42. The Channel Bindings from this client are missing or do not match the established Transport Layer Security (TLS) Channel. ...
  43. The Channel Bindings from this client do not match the established Transport Layer Security (TLS) Channel. The service might ...
  44. The character at which to start the search; if omitted, StartPosition = 1. The first character in WithinText is character ...
  45. The character length %1!Iu! specified for type "%2" for column %3!Iu! exceeded the maximum SQL Server allowed length of %4!d! ...
  46. The chart series {0} is missing and cannot be deserialized. You can use Chart.CallbackStateContent='All' to preserve all ...
  47. The check constraint '{0}.{1}.{2}' will not be scripted for article '{3}' because it references the unpublished column '{4}'. ...
  48. The check for a Publisher needing a new identity range allocation failed on table %1!s!. This check occurs every time the ...
  49. The checkpoint file "%1!s!" is locked by another process. This may occur if another instance of this package is currently ...
  50. The checksum function used by the merge process to perform data validation on article '%1' returned an invalid checksum value. ...
  51. The CircularString input is not valid because it does not have enough points. A CircularString must have at least three points. ...
  52. The Claims to Windows Token service is used to extract a Windows user identity from a SharePoint claims token during PowerPivot ...
  53. The client cannot connect to the server because the requested instance was not available. Use SQL Server Configuration Manager ...
  54. The client code page %1!u! does not have a corresponding SQL Server Collation. The Table-Valued Parameter could not be sent. ...
  55. The client components on this workstation must be upgraded before a connection can be established to this instance of Analysis ...
  56. The client library requires a different version of the database schema ({0}). Install the required version of the database ...
  57. The client library requires a newer version of the database schema ({1}). The current database schema version is ({0}). Install ...
  58. The client version is incompatible with the database version. Ask your administrator to upgrade the client components, the ...
  59. The client was unable to join a session with SPID %1!s!. This error may have been caused by an earlier operation failing ...
  60. The client was unable to reuse a session with SPID %1!s!, which had been reset for connection pooling. The failure ID is ...
  61. The client's metadata is out of sync with the engine's metadata. The reference returned by the engine is unknown in the client: ...
  62. The Cloud Adapter public endpoint is configured with the different port {0}. Verify the virtual machine endpoint configurations. ...
  63. The Cloud Adapter public endpoint is not configured for the virtual machine. Verify the virtual machine endpoint configurations. ...
  64. The CLR procedure/function/type being signed refers to an assembly that is not signed either by a strong name or an assembly. ...
  65. The CLR type referenced by column "%1!s!" of table variable "%2!s!" has been dropped during the execution of the batch. Run ...
  66. The CLSID registry key indicating that the Oracle OLEDB Provider for Oracle, OraOLEDB.Oracle, has been registered is not ...
  67. The cluster disk '{0}' can not be owned by the node(s) {1} so it cannot be used as a cluster disk. To use this disk, add ...
  68. The cluster disk '{0}' can not be used as a cluster disk. Analysis Services on WFC cluster cannot have files on Clustered ...
  69. The cluster disk '{0}' can not be used as a cluster disk. Clustered Shared Volume (CSV) is not supported on Windows Server ...
  70. The cluster disk '{0}' cannot be selected because it is mounted on the following cluster resources: {1}. Choose the root ...
  71. The cluster disk '{0}' could not be brought online. The disk must be online in order for the SQL Server failover cluster ...
  72. The cluster disk '{0}' is not owned by the local node so it cannot be used as a cluster disk. To use this disk, move it to ...
  73. The cluster disk device name '{0}' is not valid. Supported devices names include drive letters, OS object name, and volume ...
  74. The cluster disk resource '{0}' is not online. Some operations may fail if the disk cannot be brought online for disk operations. ...
  75. The cluster either has not been verified or there are errors or failures in the verification report. Refer to KB953748 or ...