SQL Server 2016

  1. Could not grant SELECT permission for the change enumeration functions for capture instance '%1!s!' and source table '%2!s!.%3!s!' ...
  2. Could not identify the Publisher '%1!s!' at the Distributor '%2!s!'. Make sure that the server '%3!s!' is registered at the ...
  3. Could not increase the available registry space. 2 KB of free registry space is required for the installation of this application. ...
  4. Could not insert a backup or restore history/detail record in the msdb database. This may indicate a problem with the msdb ...
  5. Could not insert a row larger than the page size into a hash table. Resubmit the query using the ROBUST PLAN optimization ...
  6. Could not load the definition for constraint ID %1!s! in database ID %2!s!. Run DBCC CHECKCATALOG to verify the integrity ...
  7. Could not locate backup header information for database '%1!s!' in the specified backup device. Specify a backup device that ...
  8. Could not locate entry in sysdatabases for database '{0}'. No entry found with that name. Make sure that the name is entered ...
  9. Could not locate entry in sysdatabases for database '{0}'. No entry found with that name. Make sure that the name is entered ...
  10. Could not locate file '%1!s!' for database '%2!s!' in sys.database_files. The file either does not exist, or was dropped. ...
  11. Could not modify the the verbose logging status for table %1!s!. The failure occurred when executing the command '%2!s!'. ...
  12. Could not obtain SQL Server Service information. An attempt to connect to WMI on '{0}' failed with the following error: {1} ...
  13. Could not obtain the maximum LSN for the database from function 'sys.fn_cdc_get_max_lsn'. Refer to previous errors in the ...
  14. Could not obtain the minimum LSN of the change table associated with capture instance '%1!s!' from function 'sys.fn_cdc_get_min_lsn'. ...
  15. Could not open a handle to the remote process. Check that you have enough priviledges on this system to obtain PROCESS_ALL_ACCESS ...
  16. Could not open database %1!s!. Replication settings and system objects could not be upgraded. If the database is used for ...
  17. Could not open distribution database %1!s! because it is offline or being recovered. Replication settings and system objects ...
  18. Could not open File Control Block (FCB) for invalid file ID %1!s! in database '%2!s!'. Verify the file location. Execute ...
  19. Could not open key: 2]. { System error 3].} Verify that you have sufficient access to that key, or contact your support personnel. ...
  20. Could not open registry subkey: {1} in registry hive '{0}'. Examine if this subkey exists and has read-write permissions. ...
  21. Could not perform the operation because the database has reached its quota for in-memory tables. See 'http://go.microsoft.com/fwlink/?LinkID=623028' ...
  22. Could not perform the operation because the requested memory grant was not available in resource pool '%1!s!' (%2!s!). Rerun ...
  23. Could not post message '%1!s!' from server instance '%2!s!' because there is insufficient memory. Reduce non-essential memory ...
  24. Could not proceed with index DDL operation on %1!s! '%2!s!' because it conflicts with another concurrent operation that is ...
  25. Could not proceed with the DDL operation because it is referencing column '%1!s!' on table '%2!s!' and this conflicts with ...
  26. Could not process the operation. Always On Availability Groups does not have permissions to access the Windows Server Failover ...
  27. Could not process the operation. Always On Availability Groups failed to load the required Windows Server Failover Clustering ...
  28. Could not process the operation. Always On Availability Groups has not started because the instance of SQL Server is not ...
  29. Could not process the operation. Always On Availability Groups replica manager is disabled on this instance of SQL Server. ...
  30. Could not process the operation. Always On Availability Groups replica manager is waiting for the host computer to start ...
  31. Could not process the operation. The instance of SQL Server is running under WOW64 (Windows 32-bit on Windows 64-bit), which ...
  32. Could not read rid from data provided (missing column name, null reader object, or corrupted data). The index is probably ...
  33. Could not read security information for key 2]. { System error 3].} Verify that you have sufficient access to that key, or ...
  34. Could not read the queue data for the subscription (Publisher=%1!s!, PublisherDb=%2!s!, Publication=%3!s!, Subscriber=%4!s!, ...
  35. Could not read the Web Services Description Language (WSDL) file. The input WSDL file is not valid. The following error occurred ...
  36. Could not read value 2 from key 3]. { System error 4].} Verify that you have sufficient access to that key, or contact your ...
  37. Could not recover database '%1!s!' (database ID %2!s!) because of unresolved transaction outcomes. Microsoft Distributed ...
  38. Could not redo log record %1!s!, for transaction ID %2!s!, on page %3!s!, allocation unit %4!s!, database '%5!s!' (database ...
  39. Could not register font 2]. Verify that you have sufficient permissions to install fonts, and that the system supports this ...
  40. Could not remove captured column entries in the Change Data Capture metadata for capture instance '%1!s!' and source table ...
  41. Could not remove Change Data Capture metadata for capture instance '%1!s!' and source table '%2!s!.%3!s!'. Refer to previous ...
  42. Could not remove DDL history entries in the Change Data Capture metadata for capture instance '%1!s!' and source table '%2!s!.%3!s!'. ...
  43. Could not remove directory '%1!s!'. Check the security context of xp_cmdshell and close other processes that may be accessing ...
  44. Could not remove index column entries in the Change Data Capture metadata for capture instance '%1!s!' and source table '%2!s!.%3!s!'. ...
  45. Could not resolve the data source for the '%{partition/}' partition. Out of line objects have been provided. Please check ...
  46. Could not resolve the data source view for the '%{dimension/}' dimension. Out of line objects have been provided. Please ...
  47. Could not resolve the data source view for the '%{partition/}' partition. Out of line objects have been provided. Please ...
  48. Could not retrieve column information for index '%1!s!' of source table '%2!s!.%3!s!'. Refer to previous errors in the current ...
  49. Could not retrieve replication information for table %1!s!. Verify that the table has a primary key, and then rerun the Log ...
  50. Could not retrieve the intermediate relation between '{0}' and {1}'. A relation may not exist or the relation is ambiguous. ...
  51. Could not retrieve the Layered AG Configuration for database '%1!s!' (URI: '%2!s!', partition ID '%3!s!') . Encountered error ...
  52. Could not run BEGIN TRANSACTION in database '%1!s!' because the database is in emergency mode or is damaged and must be restarted. ...
  53. Could not save the backup of the model. The Data Backup property of the model has to be changed to "Do not backup to disk". ...
  54. Could not serialize the data for node '%1!s!' because it contains a character ( 2!s!) which is not allowed in XML. To retrieve ...
  55. Could not set file security for file '[3]'. Error: 2]. Verify that you have sufficient privileges to modify the security ...
  56. Could not set value for registry key '{2}' of type '{3}'. Examine if subkey '{1}' exists in registry hive '{0}' exists and ...
  57. Could not start distributed query using integrated login because the user is logged in using SQL Server authentication. Provide ...
  58. Could not start Service Broker for database id: %1!s!. A problem is preventing SQL Server from starting Service Broker. Check ...
  59. Could not start Service Broker manager. Check the SQL Server error log and the Windows error log for additional error messages. ...
  60. Could not start the Always On Availability Groups transport manager. This failure probably occurred because a low memory ...
  61. Could not start the network library because of an internal error in the network library. To determine the cause, review the ...
  62. could not start the Replication Conflict Viewer for server '%2' using the command line '%1'. Be sure that the command line ...
  63. could not start the Snapshot Agent to generate a new snapshot. You must start the Snapshot Agent manually before the subscription(s) ...
  64. Could not submit Change Role completion tasks for %1!s!' (URI: '%2!s!', partition ID '%3!s!') . Encountered error (error ...
  65. Could not submit logical reseeding task for '%1!s!' (URI: '%2!s!', partition id: '%3!s!') . Encountered error (error code: ...
  66. Could not subscribe to article '%1!s!' because heterogeneous Subscriber '%2!s!' does not support the @pre_creation_cmd parameter ...
  67. Could not successfully restore database. This request has been assigned a tracing ID of '%1!s!'. Provide this tracing ID ...
  68. Could not switch the model to DirectQuery mode. Correct the DirectQuery errors described in the Error List and try again. ...
  69. Could not terminate the Knowledge Base '{0}' activity because the Knowledge Base does not exist or is being deleted. Please ...
  70. Could not terminate the project '{0}' activity because the project does not exist or is being deleted. Please wait until ...
  71. Could not unhash buffer at 1!s! with a buffer page number of %2!s! and database ID %3!s! with HASHED status set. The buffer ...
  72. Could not update a list of fields for the query. Verify that you can connect to the data source and that your query syntax ...
  73. Could not update the cdc.captured_columns entry for column '%1!s!' of change table '%2!s!' to reflect a data type change ...
  74. Could not update the Change Data Capture metadata for capture instance '%1!s!' and source table '%2!s!.%3!s!'. Refer to previous ...
  75. Could not update the metadata for database %1!s! to indicate that a Change Data Capture job has been added. The failure occurred ...