Server Error Messages 1700-1799


Creating table ’%.*s’ failed because the minimum row size would be %d bytes. This exceeds the maximum allowable size of a row for this table, %d bytes.
 %s failed because definition of column ’%.*s’ in table ’%.*s’ exceeds the limit of %d columns per table.
 Failed to allocate disk space for a work table in database `%.*s'.  You may be able to free up space by using the DUMP TRANsaction command, or you may want to extend the size of the database by using the ALTER DATABASE command.
 Only the SA can create the system table `%.*s'.
 Must create system table `%.*s' in the Master Database.
 System table `%.*s' was not created, because ad-hoc updates to system catalogs are not enabled.
 Could not create system table `%.*s'.
 Warning: Row size (%d bytes) could exceed row size limit, which is %d bytes.
 Referenced table name missing in a referential constraint declaration on table `%.*s'.
 Referenced table `%.*s' specified in a referential constraint declared on `%.*s' does not exist in the database `%.*s'.
 There is no unique constraint on the referenced columns in the referenced table `%.*s' specified in referential constraint declaration on the table `%.*s'.
 Internal inconsistency - constraint exists in sysconstraints table, but not sysobjects table, id = %d.
 Exceeded maximum allowed referenced columns, %d, in a single referential constraint declaration, table = ’%.*s’, database = ’%.*s’.
 The number of columns in a foreign key column list and primary key/referenced column list not the same in referential constraint declaration on table `%.*s', in database `%.*s'.
 Invalid system table given for status update, this is an internal error.
 System catalog column/table specified for status change not found.
 The number of columns in a forign key column list is less than  a  primary/referential column list in a referential constraint declaration, table = `%.*s', data base =  `%.*s'.
 Primary key does not exist for the table referenced in a referential constraint declaration, table = `%.*s', data base =  `%.*s'.
 A column referenced in a referential constraint declaration does not exist, referencing table = `%.*s', data base =  `%.*s'.
 Column types of referencing and referenced columns don't match. referencing column = `%.*s', referenced column = `%.*s'.
 Column lengths of string type referencing and referenced columns don't match. referencing column = `%.*s', referenced column = `%.*s'.
 Column precision and scale of numeric referencing and referenced columns don't match. referencing column = `%.*s', referenced column = `%.*s'.
 The number of columns in a forign key column list is greater than  a  primary/referential column list in a referential constraint declaration, table = `%.*s', data base =  `%.*s'.
 SELECT INTO failed because column %d in table `%.*s' has a null column name. Null column names are not allowed.
 Internal inconsistency:  database id %d sent to crt_main() does not match Pss->pcurdb value of %d.
 The crt_main() function is trying to put too many lock requests in the lock_requests[] array.
 An object with the same name, but owned by a different user, is already being replicated. The table `%.*s' is not marked as replicated.
 Due to an internal error the table `%.*s' is not marked as replicated. Please contact your System Administrator (SA) for help.
 Failed to reserve/initialize allocation hints space in table `%.*s'.
 You cannot specify both a default value of NULL and a NOT NULL constraint for column `%.*s' in table `%.*s'. Retry your command with only one of these column options.
 Cannot create auditing-related tables in any database other than sybsecurity database.
 Cannot create tables starting with `sysaudits_'.
Creating this referential constraint would result in the total number of referential constraints of table %.*s exceeding %d. Please run: 'sp_helpconstraint %.*s' to find out the number of referential constraints that this table has.
 Warning: Parameter `exp_row_size' is not applicable to table `%.*s' in allpages locking scheme
 Warning: Parameter `max_rows_per_page' is not applicable to table `%.*s' in `datapages' or `datarows' locking scheme
 Warning: Parameters `exp_row_size' and `max_rows_per_page' both specified for table `%.*s'. Only parameter appropriate to lock scheme specified will be used internally, but both are stored. See users manual for more information.
Expected row size specified on table '%.*s' is invalid. Expected row size should be either 0, 1 or between  minrow length %d and maxrow length %d
Multiple lock schemes specified on the table '%.*s'. Lock scheme has to unique. 
Internal error: Dataonly Lock scheme is not supported on this system table '%.*s'. Contact sybase technical support for help. 
Failed to reserve attribute space for table '%.*s'. 
Failed to initialize attribute space for table '%.*s'. 
Table '%.*s' has fixed length schema. Parameter 'exp_row_size' is not applicable to tables with fixed length schema. 
DELETE STATISTICS failed on table '%.*s' see error log for more information. 
DELETE STATISTICS duplicate column '%.*s' specified, column can only be referenced once. 
DELETE STATISTICS column name '%.*s' not found. 
syscolumns cannot be read.  
UPDATE STATISTICS - could not obtain required locks on table '%.*s 
UPDATE STATISTICS failed to complete on table '%.*s 
UPDATE STATISTICS number of step values requested '%d' must be greater than or equal to '%d' values  
UPDATE STATISTICS - index and column list cannot be specified at the same time  
Deadlock detected on '%.*s' while processing statistics 
Cannot insert rows into sysstatistics 
Cannot insert rows into sysstatistics, due to multiple equal frequency values, please contact Sybase Techn ical Support 
Failed to insert row into worktable, when projecting base table on to work table for collecting statistics .  
Unable to start a level zero scan on table '%.*s' for UPDATE STATISTICS. This can happen if some DDL command like ALTER/CREATE INDEX/REORG/DROP is active on the table. 
Cannot create syscoordinations tables in any database other than sybsystemdb. 
Number of variable length columns exceeds limit of %d for allpage locked tables. %s for ’%.*s’ failed.
Warning: Potential offset of column ’%.*s’ (%d bytes) and subsequent variable-length columns in table %.*s exceeds limit of %d bytes for column-offset of variable-length columns in DOL tables. Future inserts to this table may fail.
Variable-length column ’%.*s’ starts at column-offset %d bytes and is non-nullable. This will prevent inserting any data into that column as the column offset exceeds the limit of %d bytes for column-offsets in DOL tables. %s ’%.*s’ failed.
%s failed. Addition of column ’%.*s’ to table ’%.*s’ exceeds maximum row width. Rows must be between %d bytes and %d bytes.
Warning: Maximum row size exceeds allowable width. It is being rounded down to %d bytes.
Warning: Update of SYSSTATISTICS row (sequence no %d, format ID %d, column IDs: %s) failed. Statistics row deleted. Regenerate statistics for these columns.

Number	Severity	Text and Explanation
1701	16	Creating table ’%.s’ failed because the minimum row size would be %d bytes. This exceeds the maximum allowable size of a row for this table, %d bytes. Explanation:* Adaptive Server could not perform the requested action. Rewrite the query to conform to the requirement specified in the error message.
1702	16	%s failed because definition of column ’%.s’ in table ’%.s’ exceeds the limit of %d columns per table. Explanation: Refer to the writeup for this error.
1703	17	Failed to allocate disk space for a work table in database `%.s'. You may be able to free up space by using the DUMP TRANsaction command, or you may want to extend the size of the database by using the ALTER DATABASE command. Explanation:* Command failed due to resource limitation. Modify the command to fit available resources, retry when the resource is available, or contact your System Administrator to address the resource problem.
1704	16	Only the SA can create the system table `%.s'. Explanation:* Adaptive Server could not perform the requested action. The command violates a permission or privilege restriction. Check the command and working database context.
1705	16	Must create system table `%.s' in the Master Database. Explanation:* Command failed due to invalid or illegal request, check current database. System table shown in the message should be created in master database.
1706	16	System table `%.s' was not created, because ad-hoc updates to system catalogs are not enabled. Explanation:* Adaptive Server could not perform the requested action. The command violates a permission or privilege restriction. Check the command and working database context.
1707	18	Could not create system table `%.s'. Explanation:* Command failed due to internal Adaptive Server problem. Perform any diagnostic action indicated by message. Report the error to your System Administrator.
1708	16	Warning: Row size (%d bytes) could exceed row size limit, which is %d bytes. Explanation: Adaptive Server could not perform the requested action. Modify your table schema to meet the requirement indicated in the error message.
1709	16	Referenced table name missing in a referential constraint declaration on table `%.s'. Explanation:* Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
1710	16	Referenced table `%.s' specified in a referential constraint declared on `%.s' does not exist in the database `%.s'. Explanation:* Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
1711	16	There is no unique constraint on the referenced columns in the referenced table `%.s' specified in referential constraint declaration on the table `%.s'. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
1712	18	Internal inconsistency - constraint exists in sysconstraints table, but not sysobjects table, id = %d. Explanation: Command failed due to internal Adaptive Server problem. Perform any diagnostic action indicated by message. Report the error to your System Administrator.
1714	16	Exceeded maximum allowed referenced columns, %d, in a single referential constraint declaration, table = ’%.s’, database = ’%.s’. Explanation: Adaptive Server could not perform the requested action. Modify your command to meet the requirement for the objects or variables shown in the error message.
1715	16	The number of columns in a foreign key column list and primary key/referenced column list not the same in referential constraint declaration on table `%.s', in database `%.s'. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
1716	18	Invalid system table given for status update, this is an internal error. Explanation: Command failed due to internal Adaptive Server problem. Perform any diagnostic action indicated by message. Report the error to your System Administrator.
1717	16	System catalog column/table specified for status change not found. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
1718	16	The number of columns in a forign key column list is less than a primary/referential column list in a referential constraint declaration, table = `%.s', data base = `%.s'. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
1719	16	Primary key does not exist for the table referenced in a referential constraint declaration, table = `%.s', data base = `%.s'. Explanation: Adaptive Server could not perform the requested action. Check your command for missing or incorrect database objects, variable names, and/or input data.
1720	16	A column referenced in a referential constraint declaration does not exist, referencing table = `%.s', data base = `%.s'. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
1721	16	Column types of referencing and referenced columns don't match. referencing column = `%.s', referenced column = `%.s'. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
1722	16	Column lengths of string type referencing and referenced columns don't match. referencing column = `%.s', referenced column = `%.s'. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
1723	16	Column precision and scale of numeric referencing and referenced columns don't match. referencing column = `%.s', referenced column = `%.s'. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
1724	16	The number of columns in a forign key column list is greater than a primary/referential column list in a referential constraint declaration, table = `%.s', data base = `%.s'. Explanation: Command failed due to invalid or illegal request. Check syntax, semantics, and permissions. Take any corrective action indicated by message.
1725	16	SELECT INTO failed because column %d in table `%.s' has a null column name. Null column names are not allowed. Explanation:* Adaptive Server could not perform the requested action. Rewrite the command to conform to the requirement specified in the error message.
1726	18	Internal inconsistency: database id %d sent to crt_main() does not match Pss->pcurdb value of %d. Explanation: Command failed due to internal Adaptive Server problem. Perform any diagnostic action indicated by message. Report the error to your System Administrator.
1727	20	The crt_main() function is trying to put too many lock requests in the lock_requests[] array. Explanation: Adaptive Server encountered an internal error affecting the current process. Reconnect to Adaptive Server. Report the error to your System Administrator so dbcc diagnostics can be run.
1729	10	An object with the same name, but owned by a different user, is already being replicated. The table `%.s' is not marked as replicated. Explanation:* This is an informational message. Unless otherwise specified, no action is required. Contact your System Administrator about any warning issued in the message.
1730	10	Due to an internal error the table `%.s' is not marked as replicated. Please contact your System Administrator (SA) for help. Explanation:* There may be a potential problem with a database or database object. Contact your System Administrator.
1732	20	Failed to reserve/initialize allocation hints space in table `%.s'. Explanation:* See the writeup for Error 1732.
1734	16	You cannot specify both a default value of NULL and a NOT NULL constraint for column `%.s' in table `%.s'. Retry your command with only one of these column options. Explanation: The SQL statement is semantically incorrect. Choose either NULL or NOT NULL.
1736	16	Cannot create auditing-related tables in any database other than sybsecurity database. Explanation: This message is generated when an SSO tries to create audit tables in a database other than sybsecurity.
1737	16	Cannot create tables starting with `sysaudits_'. Explanation: This message is generated when a user tries to create a table starting with sysaudits_. This is not allowed.
1738	16	Creating this referential constraint would result in the total number of referential constraints of table %.s exceeding %d. Please run: 'sp_helpconstraint %.s' to find out the number of referential constraints that this table has. Explanation: Adaptive Server could not perform the requested action.
1739	10	Warning: Parameter `exp_row_size' is not applicable to table `%.s' in allpages locking scheme Explanation:* Retry the command if necessary. Do not specify exp_row_size on an allpages-locked table. Use this parameter only for tables that use the data-only-locked scheme and contain variable length rows.
1740	10	Warning: Parameter `max_rows_per_page' is not applicable to table `%.s' in `datapages' or `datarows' locking scheme Explanation:* Do not specify max_rows_per_page on a data-only-locked table. Use this parameter only for tables that use the allpages-locked scheme.
1741	10	Warning: Parameters `exp_row_size' and `max_rows_per_page' both specified for table `%.s'. Only parameter appropriate to lock scheme specified will be used internally, but both are stored. See users manual for more information. Explanation:* You cannot mix parameters for data-only-locked tables and all-pages-locked tables in one DDL command.
1742	16	Expected row size specified on table '%.s' is invalid. Expected row size should be either 0, 1 or between minrow length %d and maxrow length %d Explanation:* Adaptive Server could not perform the requested action. Rewrite the command to conform to the requirement specified in the error message.
1743	10	Multiple lock schemes specified on the table '%.s'. Lock scheme has to unique. Explanation:* Adaptive Server could not perform the requested action. Rewrite the command to conform to the requirement specified in the error message.
1744	10	Internal error: Dataonly Lock scheme is not supported on this system table '%.s'. Contact sybase technical support for help. Explanation:* There may be a potential problem with a database or database object. Contact your System Administrator.
1750	20	Failed to reserve attribute space for table '%.s'. Explanation:* Adaptive Server encountered an internal error affecting the current process. Report the error to your System Administrator.
1751	20	Failed to initialize attribute space for table '%.s'. Explanation:* Adaptive Server encountered an internal error affecting the current process. Report the error to your System Administrator.
1752	16	Table '%.s' has fixed length schema. Parameter 'exp_row_size' is not applicable to tables with fixed length schema. Explanation:* Cannot specify an expected row size for fixed-length tables. See the writeup for Error 1739.
1753	16	DELETE STATISTICS failed on table '%.s' see error log for more information. Explanation:* Command failed due to invalid or illegal request. Check syntax, semantics, and permissions.
1754	16	DELETE STATISTICS duplicate column '%.s' specified, column can only be referenced once. Explanation:* Command failed due to invalid or illegal request. Check syntax, semantics, and permissions.
1755	16	DELETE STATISTICS column name '%.s' not found. Explanation:* Command failed due to invalid or illegal request. Check syntax, semantics, and permissions.
1756	18	syscolumns cannot be read. Explanation: Command failed due to internal Adaptive Server problem. Perform any diagnostic action indicated by the message. Report the error to your System Administrator.
1757	10	UPDATE STATISTICS - could not obtain required locks on table '%.s Explanation:* Report this error to your System Administrator.
1758	10	UPDATE STATISTICS failed to complete on table '%.s Explanation:* Report this error to your System Administrator.
1759	16	UPDATE STATISTICS number of step values requested '%d' must be greater than or equal to '%d' values Explanation: Adaptive Server could not perform the requested action. Rewrite the command to conform to the requirement specified in the error message.
1760	16	UPDATE STATISTICS - index and column list cannot be specified at the same time Explanation: Adaptive Server could not perform the requested action. Rewrite the command to conform to the requirement specified in the error message.
1761	13	Deadlock detected on '%.s' while processing statistics Explanation:* Rerun the command that raised this error.
1762	18	Cannot insert rows into sysstatistics Explanation: Command failed due to internal Adaptive Server problem. Perform any diagnostic action indicated by the message. Report the error to your System Administrator.
1763	18	Cannot insert rows into sysstatistics, due to multiple equal frequency values, please contact Sybase Techn ical Support Explanation: Command failed due to internal Adaptive Server problem. Perform any diagnostic action indicated by the message. Report the error to your System Administrator.
1764	18	Failed to insert row into worktable, when projecting base table on to work table for collecting statistics . Explanation: Command failed due to internal Adaptive Server problem. Perform any diagnostic action indicated by the message. Report the error to your System Administrator.
1765	10	Unable to start a level zero scan on table '%.s' for UPDATE STATISTICS. This can happen if some DDL command like ALTER/CREATE INDEX/REORG/DROP is active on the table. Explanation:* Retry the scan after completing the DDL command.
1766	16	Cannot create syscoordinations tables in any database other than sybsystemdb. Explanation: Adaptive Server could not perform the requested action. Modify your command to meet the Adaptive Server requirement for the objects or variables shown in the error message.
1767	16	Number of variable length columns exceeds limit of %d for allpage locked tables. %s for ’%.s’ failed. Explanation:* Adaptive Server could not perform the requested action. Modify your command to meet the Adaptive Server requirement for the objects or variables shown in the error message.
1768	10	Warning: Potential offset of column ’%.s’ (%d bytes) and subsequent variable-length columns in table %.s exceeds limit of %d bytes for column-offset of variable-length columns in DOL tables. Future inserts to this table may fail. Explanation: This informational messages indicates that your DDL command may cause problems at future inserts into the DOL table. Check and modify the DDL to meet the Adaptive Server requirement shown in the error message.
1769	16	Variable-length column ’%.s’ starts at column-offset %d bytes and is non-nullable. This will prevent inserting any data into that column as the column offset exceeds the limit of %d bytes for column-offsets in DOL tables. %s ’%.s’ failed. Explanation: Modify your DDL command to meet the Adaptive Server requirement for the objects or variables shown in the error message.
1770	16	%s failed. Addition of column ’%.s’ to table ’%.s’ exceeds maximum row width. Rows must be between %d bytes and %d bytes. Explanation: Adaptive Server could not perform the requested action. Modify your DDL command to meet the Adaptive Server requirement for the objects or variables shown in the error message.
1771	10	Warning: Maximum row size exceeds allowable width. It is being rounded down to %d bytes. Explanation: This informational message indicates that your DDL is being modified to meet the Adaptive Server requirement for the objects or variables shown in the error message.
1772	10	Warning: Update of SYSSTATISTICS row (sequence no %d, format ID %d, column IDs: %s) failed. Statistics row deleted. Regenerate statistics for these columns. Explanation: Adaptive Server could not perform the requested action. Modify your command to meet the Adaptive Server requirement for the objects or variables shown in the error message.