SQL Server Errors or Failures from Error: 22957 to Error: 22977

Error: 22957, Severity: 16, LSN %s, specified as the new low end point for the change table associated with capture instance ‘%s’, is not within the Change Data Capture timeline [%s, %s].
Error: 22958, Severity: 16, Could not create the function to query for all changes for capture instance ‘%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
Error: 22959, Severity: 16, Could not create the function to query for net changes for capture instance ‘%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
Error: 22960, Severity: 16, Change data capture instance ‘%s’ has not been enabled for the source table ‘%s.%s’. Use sys.sp_cdc_help_change_data_capture to verify the capture instance name and retry the operation.
Error: 22961, Severity: 16, Could not create a nonclustered index to support net change tracking for capture instance ‘%s’ and source table ‘%s.%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
Error: 22962, Severity: 16, Two capture instances already exist for source table ‘%s.%s’. A table can have at most two capture instances. If the current tracking options are not appropriate, disable change tracking for the obsolete instance by using sys.sp_cdc_disable_table and retr
Error: 22963, Severity: 16, Parameter ‘%s’ cannot be null or empty. Specify a value for the named parameter and retry the operation.
Error: 22964, Severity: 16, LSN %s, specified as the new low end point for change table cleanup must represent the start_lsn value of a current entry in the cdc.lsn_time_mapping table. Choose an LSN value that satisfies this requirement.
Error: 22965, Severity: 16, A quoted column in the column list is not properly terminated. Verify that columns are correctly delimited and retry the operation. For more information, see ‘Delimited Identifiers’ in Books Online.
Error: 22966, Severity: 16, Could not create table dbo.systranschemas in database ‘%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
Error: 22967, Severity: 16, Could not create a clustered index for table dbo.systranschemas in database ‘%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
Error: 22968, Severity: 16, Could not create DDL trigger ‘%s’ when enabling Change Data Capture for database ‘%s’. Additional messages in the SQL Server error log and system event log may provide more detail.
Error: 22970, Severity: 16, The value for parameter @maxscans specified for the Change Data Capture job must be greater than 0.
Error: 22971, Severity: 16, Could not allocate memory for the log reader history cache. Verify that SQL Server has sufficient memory for all operations. Check the physical and virtual settings on the server and examine memory usage to see if another application is excessively consum
Error: 22972, Severity: 16, When calling stored procedure [sys].sp_cdc_help_change_data capture, if either @source_schema or @source_name is non-null and non-empty, the other parameter must also be non-null and non-empty.
Error: 22973, Severity: 16, The specified filegroup ‘%s’ is not a valid filegroup for database ‘%s’. Specify a valid existing filegroup or create the named filegroup, and retry the operation.
Error: 22974, Severity: 16, Tables contained in the cdc schema cannot be enabled for Change Data Capture.
Error: 22975, Severity: 16, Source table ‘%s’ contains one of the following reserved column names: __$start_lsn, __$end_lsn, __$seqval, __$operation, and __$update_mask. To enable Change Data Capture for this table, specify a captured column list and ensure that these columns are ex
Error: 22976, Severity: 16, Could not alter column ‘%s’ of change table ‘%s’ in response to a data type change in the corresponding column of the source table ‘%s’. The Change Data Capture meta data for source table ‘%s’ no longer accurately reflects the source table. Refer to previ
Error: 22977, Severity: 16, Unable to update DDL history information to reflect columns changes applied to the tracked table associated with change table ‘%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
This is applicable on below versions of SQL Server
SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014
Hope this was helpful.
Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.