# Codes 7xxx

*Advantage Error Guide*

## Contents

- [7000 General Advantage server Error Code. Refer to the associated specific Error Code for more information](#7000-general-advantage-server-error-code-refer-to-the-associated-specific-error-code-for-more-information)
- [7001 No memory available](#7001-no-memory-available)
- [7002 Configuration error](#7002-configuration-error)
- [7003 Maximum number of users exceeded](#7003-maximum-number-of-users-exceeded)
- [7004 Maximum number of work areas exceeded](#7004-maximum-number-of-work-areas-exceeded)
- [7005 Maximum number of tables exceeded](#7005-maximum-number-of-tables-exceeded)
- [7006 Maximum number of index files exceeded](#7006-maximum-number-of-index-files-exceeded)
- [7007 Maximum number of locks exceeded](#7007-maximum-number-of-locks-exceeded)
- [7008 Advantage server file open failure](#7008-advantage-server-file-open-failure)
- [7009 Problem with Advantage server file write](#7009-problem-with-advantage-server-file-write)
- [7010 Problem with Advantage server file read](#7010-problem-with-advantage-server-file-read)
- [7011 Problem with Advantage server file seek](#7011-problem-with-advantage-server-file-seek)
- [7012 Problem with Advantage server file offset](#7012-problem-with-advantage-server-file-offset)
- [7013 Advantage server file access error](#7013-advantage-server-file-access-error)
- [7014 Invalid DBF table](#7014-invalid-dbf-table)
- [7015 Corrupt NTX](#7015-corrupt-ntx)
- [7016 Corrupt table](#7016-corrupt-table)
- [7017 Corrupt IDX, CDX, or ADI index](#7017-corrupt-idx-cdx-or-adi-index)
- [7018 Corrupt index: empty page](#7018-corrupt-index-empty-page)
- [7019 Corrupt memo field](#7019-corrupt-memo-field)
- [7020 User logged out](#7020-user-logged-out)
- [7021 Maximum tags exceeded](#7021-maximum-tags-exceeded)
- [7022 Maximum index levels](#7022-maximum-index-levels)
- [7023 Index expression not supported](#7023-index-expression-not-supported)
- [7024 Removing ghost connection](#7024-removing-ghost-connection)
- [7025 Semaphore connection file path too long](#7025-semaphore-connection-file-path-too-long)
- [7026 Communication packet checksum failed](#7026-communication-packet-checksum-failed)
- [7027 User not logged in](#7027-user-not-logged-in)
- [7028 Invalid open mode](#7028-invalid-open-mode)
- [7029 Index Sort Buffer Size too small](#7029-index-sort-buffer-size-too-small)
- [7030 Missing Advantage configuration file, ADS.CFG or ADSLOCAL.CFG](#7030-missing-advantage-configuration-file-ads-cfg-or-adslocal-cfg)
- [7031 Could not get Advantage configuration information](#7031-could-not-get-advantage-configuration-information)
- [7032 Error in Advantage configuration parameter/value/data](#7032-error-in-advantage-configuration-parameter-value-data)
- [7033 Maximum Number of Connections Exceeded](#7033-maximum-number-of-connections-exceeded)
- [7034 Not a Compound Index File](#7034-not-a-compound-index-file)
- [7035 Record not visible](#7035-record-not-visible)
- [7036 Failed transaction recovery error](#7036-failed-transaction-recovery-error)
- [7037 Error with key in custom index](#7037-error-with-key-in-custom-index)
- [7038 Invalid record number](#7038-invalid-record-number)
- [7039 File already open](#7039-file-already-open)
- [7040 File creation error](#7040-file-creation-error)
- [7041 File not found](#7041-file-not-found)
- [7042 Invalid bits set in the TPS semaphore byte](#7042-invalid-bits-set-in-the-tps-semaphore-byte)
- [7043 Advantage Database Server for Windows is paused](#7043-advantage-database-server-for-windows-is-paused)
- [7044 Advantage Server already on network](#7044-advantage-server-already-on-network)
- [7045 Serial number and validation code mismatch](#7045-serial-number-and-validation-code-mismatch)
- [7046 Evaluation period expired](#7046-evaluation-period-expired)
- [7047 Invalid bits set in the deleted byte](#7047-invalid-bits-set-in-the-deleted-byte)
- [7048 EXTEND.CHR or ANSI.CHR file not found at load time by the Advantage Local Server](#7048-extend-chr-or-ansi-chr-file-not-found-at-load-time-by-the-advantage-local-server)
- [7049 Error occurred when the Advantage Local Server attempted to use the EXTEND.CHR or ANSI.CHR file](#7049-error-occurred-when-the-advantage-local-server-attempted-to-use-the-extend-chr-or-ansi-chr-file)
- [7050 The user is not connected to the Advantage server](#7050-the-user-is-not-connected-to-the-advantage-server)
- [7051 The file is not open on the Advantage server](#7051-the-file-is-not-open-on-the-advantage-server)
- [7052 Cannot operate on the same table as source and destination](#7052-cannot-operate-on-the-same-table-as-source-and-destination)
- [7053 VarChar fields are not supported with this operation](#7053-varchar-fields-are-not-supported-with-this-operation)
- [7054 Field data type mismatch](#7054-field-data-type-mismatch)
- [7055 Field size mismatch](#7055-field-size-mismatch)
- [7056 Invalid Connection Path](#7056-invalid-connection-path)
- [7057 Record update failed](#7057-record-update-failed)
- [7058 Corrupt ADI index](#7058-corrupt-adi-index)
- [7059 Unique index creation error](#7059-unique-index-creation-error)
- [7060 Invalid Password](#7060-invalid-password)
- [7061 Encryption Version Mismatch](#7061-encryption-version-mismatch)
- [7063 Query table full](#7063-query-table-full)
- [7064 The IP protocol is not installed on the current machine](#7064-the-ip-protocol-is-not-installed-on-the-current-machine)
- [7065 Updates to records must meet the conditions of the SQL SELECT statement because the Constrained option has been selected](#7065-updates-to-records-must-meet-the-conditions-of-the-sql-select-statement-because-the-constrained-option-has-been-selected)
- [7066 Old Encryption Version](#7066-old-encryption-version)
- [7068 Encryption password is required for this operation](#7068-encryption-password-is-required-for-this-operation)
- [7069 The latest version of the Advantage client software is required with this version of the Advantage Database Server](#7069-the-latest-version-of-the-advantage-client-software-is-required-with-asd)
- [7071 File is too large to be opened with the given settings](#7071file-is-too-large-to-be-opened-with-the-given-settings)
- [7072 The memo file associated with this table is corrupt](#7072the-memo-file-associated-with-this-table-is-corrupt)
- [7073 The maximum number of memo blocks has been reached](#7073-the-maximum-number-of-memo-blocks-has-been-reached)
- [7074 The table ID stored in the ADT table does not match the ID stored in the Advantage Data Dictionary file](#7074-the-table-id-stored-in-the-adt-table-does-not-match-the-id-stored-in-the-advantage-data-dictionary-file)
- [7075 The Advantage Local Server version allows a maximum of 5 users to access a file at one time.](#7075-the-advantage-local-server-version-allows-a-maximum-of-5-users-to-access-a-file-at-one-time-the-limit-has-been-exceeded)
- [7076 No Primary key was found for the foreign key](#7076-no-primary-key-was-found-for-the-foreign-key)
- [7077 The Advantage Data Dictionary cannot be opened](#7077-the-advantage-data-dictionary-cannot-be-opened)
- [7078 The Advantage Database Server cannot authenticate the user](#7078-the-advantage-database-server-cannot-authenticate-the-user)
- [7079 The user does not have read permission to the table](#7079-the-user-does-not-have-read-permission-to-the-table)
- [7080 The user does not have write rights to the table](#7080-the-user-does-not-have-write-rights-to-the-table)
- [7081 The encrypted table is using an older encryption method](#7081-the-encrypted-table-is-using-an-older-encryption-method)
- [7082 Internet access disabled](#7082-internet-access-disabled)
- [7083 An Advantage Data Dictionary connection is required](#7083-an-advantage-data-dictionary-connection-is-required)
- [7084 Compression not allowed](#7084-compression-not-allowed)
- [7085 Invalid UNC server name](#7085-invalid-unc-server-name)
- [7086 Cannot open table directly](#7086-cannot-open-table-directly)
- [7087 Permission not granted for the requested operation](#7087-permission-not-granted-for-the-requested-operation)
- [7088 The user could not be disconnected at this time](#7088-the-user-could-not-be-disconnected-at-this-time)
- [7089 Index creation aborted by the user](#7089-index-creation-aborted-by-the-user)
- [7090 Copy table or alter table operation aborted by user](#7090-copy-table-or-alter-table-operation-aborted-by-user)
- [7091 Collation sequence used to create the index differs from current collation sequence](#7091-collation-sequence-used-to-create-the-index-differs-from-current-collation-sequence)
- [7092 The index is not Advantage compatible](#7092-the-index-is-not-advantage-compatible)
- [7093 Maximum number of recursion levels exceeded](#7093-maximum-number-of-recursion-levels-exceeded)
- [7094 The full text search condition has an unclosed phrase](#7094-the-full-text-search-condition-has-an-unclosed-phrase)
- [7095 The full text search condition has an unclosed expression](#7095-the-full-text-search-condition-has-an-unclosed-expression)
- [7096 The full text search condition is missing a phrase or word](#7096-the-full-text-search-condition-is-missing-a-phrase-or-word)
- [7097 The full text search condition is not valid](#7097-the-full-text-search-condition-is-not-valid)
- [7098 The full text search condition has invalid operands specified for the NEAR operator](#7098-the-full-text-search-condition-has-invalid-operands-specified-for-the-near-operator)
- [7099 The full text search condition has an invalid distance specified for the NEAR operator](#7099-the-full-text-search-condition-has-an-invalid-distance-specified-for-the-near-operator)
- [7100 Unrecognized full text search index version](#7100-unrecognized-full-text-search-index-version)
- [7101 Failed Transaction Recovery successful](#7101-failed-transaction-recovery-successful)
- [7102 No full text search indexes found](#7102-no-full-text-search-indexes-found)
- [7103 The full text search condition is empty](#7103-the-full-text-search-condition-is-empty)
- [7104 Transaction processing is not available on current connection](#7104-transaction-processing-is-not-available-on-current-connection)
- [7105 Full Text Search Index Requires Newer Client](#7105-full-text-search-index-requires-newer-client)
- [7106 The table is read only and cannot be encrypted](#7106-the-table-is-read-only-and-cannot-be-encrypted)
- [7107 The client's memo data is out of sync with the server](#7107-the-client-s-memo-data-is-out-of-sync-with-the-server)
- [7108 Unrecognized ADI version](#7108-unrecognized-adi-version)
- [7109 Database logins are disabled](#7109-database-logins-are-disabled)
- [7110 Large key size requires newer client](#7110-large-key-size-requires-newer-client)
- [7111 The temporary table is in use](#7111-the-temporary-table-is-in-use)
- [7112 The temporary table cannot be found](#7112-the-temporary-table-cannot-be-found)
- [7113 Database logins for this user have been disabled](#7113-database-logins-for-this-user-have-been-disabled)
- [7114 Unable to split index page](#7114-unable-to-split-index-page)
- [7115 Unable to obtain OS file lock](#7115-unable-to-lock-file)
- [7116 Unrecognized ADT table version](#7116-unrecognized-adt-table-version)
- [7117 Unrecognized ADM version](#7117-unrecognized-adm-version)
- [7118 RI Cascade Operation Failed](#7118-ri-cascade-operation-failed)
- [7119 Encryption Not Available](#7119-encryption-not-available)
- [7120 Index Requires Dictionary Connection](#7120-index-requires-dictionary-connection)
- [7121 The client failed to respond while transferring data via inter-process communications](#7121-the-client-failed-to-respond-while-transferring-data-via-inter-process-communications)
- [7122 Local server failed to rebuild index](#7122-local-server-failed-to-rebuild-index)
- [7123 Unreconginzed Field Type](#7123-unreconginzed-field-type)
- [7124 Incorrect Record Count](#7124-incorrect-record-count)
- [7126 Backup in-memory table read failed](#7126-backup-in-memory-table-read-failed)
- [7127 Backup in-memory table write failed](#7127-backup-in-memory-table-write-failed)
- [7128 Backup index file copy failed](#7128-backup-index-file-copy-failed)
- [7129 Savepoint Not Found](#7129-savepoint-not-found)
- [7130 Illegal Operation Inside of Trigger](#7130-illegal-operation-inside-of-trigger)
- [7131 Table is involved in another active backup command](#7131-table-is-involved-in-another-active-backup-command)
- [7132 Subscription Information is Inconsistent](#7132-subscription-information-is-inconsistent)
- [7133 Triggers are not allowed on live views](#7133-triggers-are-not-allowed-on-live-views)
- [7134 Non-standard character used in table name or column name for replication](#7134-non-standard-character-used-in-table-name-or-column-name-for-replication)
- [7135 No trigger defined for update type](#7135-no-trigger-defined-for-update-type)
- [7136 Serial number and replication code mismatch](#7136-serial-number-and-replication-code-mismatch)
- [7137 Unexpected number of records modified during a replication update](#7137-unexpected-number-of-records-modified-during-a-replication-update)
- [7138 Record Not Locked](#7138-record-not-locked)
- [7139 Invalid Packet Data Size](#7139-invalid-packet-data-size)
- [7140 Connection is already a debugger or debuggee](#7140-connection-is-already-a-debugger-or-debuggee)
- [7141 The name is not a valid temporary table name](#7141-the-name-is-not-a-valid-temporary-table-name)
- [7142 The maximum number of debuggees was exceeded](#7142-the-maximum-number-of-debuggees-was-exceeded)
- [7143 Cannot make a connection a debuggee](#7143-cannot-make-a-connection-a-debuggee)
- [7144 Collation Repository Not Found](#7144-collation-repository-not-found)
- [7145 Collation Load Failed](#7145-collation-load-failed)
- [7146 Collation Name Not Unique](#7146-collation-name-not-unique)
- [7147 Collation Name Not Found](#7147-collation-name-not-found)
- [7148 Collation Not Recognized](#7148-collation-not-recognized)
- [7149 Invalid Packet](#7149-invalid-packet)
- [7150 Collation Is Corrupt](#7150-collation-is-corrupt)
- [7151 Invalid Table Type](#7151-invalid-table-type)
- [7153 Key Cannot Be Null](#7153-key-cannot-be-null)
- [7154 Index Automatically Rebuilt](#7154-index-automatically-rebuilt)
- [error 7156 Auto Re-Indexing is Active](#7156-auto-re-indexing-is-active)
- [7157 Maximum number of active Unicode collators for a connection have been exceeded.](#7157-maximum-number-of-active)
- [error 7158 The server cannot determine the default ANSI/OEM Unicode collation locale](#7158-the-server-cannot-d)
- [error 7159 Cannot determine the code page for the default ANSI/OEM character set](#7159-cannot-determine-th)
- [7160 Unable to Load SSL](#7160-unable-to-load-ssl)
- [7161 Unable to Verify Signature](#7161-unable-to-verify-si)
- [7162 Unable to Load SSL Entrypoint](#7162-unable-to-load-ssl)
- [7163 SSL Library Error](#7163-ssl-library-error)
- [7164 Unrecognized Cipher](#7164-unrecognized-cipher)
- [7165 FIPS Mode Failed](#7165-fips-mode-failed)
- [7166 FIPS Not Allowed](#7166-fips-not-allowed)
- [7167 FIPS Required](#7167-fips-required)
- [7168 Table does not Support Strong Encryption](#7168-table-does-not-supp)
- [7169 FIPS Mode Violation](#7169-fips-mode-violation)
- [error_7171_ANSI_UNICODE_INCONSISTENT](#7171-ansi-unicode-incons)
- [7172 Invalid TLS Certificate](#7172-invalid-tls-certifi)
- [7173 Too Many Fields](#7173-too-many-fields)
- [7175 Online Pack Already Active](#7175-online-pack-already)
- [7176 Online Pack Timeout](#7176-online-pack-timeout)
- [7177 Online Pack Extra Indexes](#7177-online-pack-extra-i)
- [7178 Online Reindex Already Active](#7178-online-reindex-alre)
- [7179 Permission Denied](#7179-permission-denied)
- [7180 Maximum Number of Advantage Web Platform Users Exceeded](#7180-stateless-connectio)
- [7181 Maximum Number of Connected (Stateful) Users Exceeded](#7181-stateful-connection)
- [7182 Online Operation Index Collation Mismatch](#7182-online-operation-in)
- [7183 Online Alter Already Active](#7183-online-alter-alread)
- [7184 Online Alter Replication Failure](#7184-online-alter-replic)
- [7185 Online Alter Extra Indexes](#7185-online-alter-extra)
- [7200 Advantage SQL Error](#7200-advantage-sql-error)
- [7201 The parameter number given exceeds the number of parameters in the SQL statement](#7201-the-parameter-number-given-exceeds-the-number-of-parameters-in-the-sql-statement)
- [7202 Data that resulted from the SQL statement is too long to be returned in a cursor](#7202-data-that-resulted-from-the-sql-statement-is-too-long-to-be-returned-in-a-cursor)
- [7203 Data that resulted from the SQL statement has an unknown length](#7203-data-that-resulted-from-the-sql-statement-has-an-unknown-length)
- [7204 Too many columns exist in the SQL SELECT statement](#7204-too-many-columns-exist-in-the-sql-select-statement)
- [7205 Cannot establish a connection to the Advantage SQL engine](#7205-cannot-establish-a-connection-to-the-advantage-sql-engine)
- [7206 Cannot convert data from SQL format to Advantage format](#7206-cannot-convert-data-from-sql-format-to-advantage-format)
- [7207 Unexpected error from the Advantage Server Agent](#7207-unexpected-error-from-the-advantage-server-agent)
- [7208 One or more columns in the SQL SELECT statement contain a data type not supported by Advantage](#7208-one-or-more-columns-in-the-sql-select-statement-contain-a-data-type-not-supported-by-advantage)
- [7209 SQL query aborted by user](#7209-sql-query-aborted-by-user)
- [7211 Advantage cannot sort the SQL result set based on the ORDER BY clause because of internal limitation](#7211-advantage-cannot-sort-the-sql-result-set-based-on-the-order-by-clause-because-of-internal-limitation)
- [7213 Server detected possible client communication failure](#7213-server-detected-pos)
- [7215 ROWID Invalidated During Pack](#7215-rowid-invalidated-d)
- [7600 Advantage Replication Error](#7600-advantage-replication-error)

## 7000 General Advantage server Error Code. Refer to the associated specific Error Code for more information {#7000-general-advantage-server-error-code-refer-to-the-associated-specific-error-code-for-more-information}

## 7001 No memory available {#7001-no-memory-available}

***Problem:*** If connected to the Advantage Database Server, there is not enough available free RAM on the server. If connected to the Advantage Local Server, there is not enough available free RAM on the client.

***Solution***:** If using the Advantage Database Server, lower Advantage Database Server configurable settings (via the Advantage Configuration Utility for the Advantage Database Server for Windows or ADS.CONF for the Advantage Database Server for Linux) so that less memory is required or add RAM to the server. Then re-load/re-start the Advantage Database Server. If using the Advantage Local Server, lower Advantage Local Server configurable settings via ADSLOCAL.CFG so that less memory is required or add RAM to the client. Then re-start the application using the Advantage Local Server.

## 7002 Configuration error {#7002-configuration-error}

***Problem:*** Invalid command line parameter.

***Solution:*** Consult your *Advantage Database Server Guide* for configuration parameters, then restart/reload the Advantage server with valid command line parameters.

## 7003 Maximum number of users exceeded {#7003-maximum-number-of-users-exceeded}

***Problem:*** The maximum number of users are already connected to the Advantage server.

***Solution:*** Upgrade to a version of the Advantage Database Server that allows more users or wait until a current user logs out.

!!!DANGER
ADS license upgrades are no longer available due to the discontinuation of the Advantage Database Server by SAP
!!!

## 7004 Maximum number of work areas exceeded {#7004-maximum-number-of-work-areas-exceeded}

**Advantage Database Server for Windows**

***Problem:*** The maximum number of configured work areas are already in use and the Advantage server was unable to allocate more resources for additional work areas.

***Solution:*** Increase the setting for the "Number of Work Areas" using the Advantage Configuration Utility. If you don't wish to use the Advantage Configuration Utility, increase the setting for the WORKAREAS configuration value in the Advantage Database Server configuration registry key using the Registry Editor. The Advantage Database Server Configuration Registry Key is located in the Registry at: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Advantage\Configuration. Then re-start the Advantage Database Server for Windows.

**Advantage Local Server**

***Problem:*** The maximum number of configured work areas are already in use and the Advantage server was unable to allocate more resources for additional work areas.

***Solution:*** Increase the setting for the WORKAREAS configuration value in the Advantage Local Server configuration file, ADSLOCAL.CFG. If no WORKAREAS configuration key exists in ADSLOCAL.CFG, add one and set the value to larger than the number of CONNECTIONS multiplied by 25 (which is the default value for the number of work areas if no WORKAREAS configuration key exists). Then re-start the application that uses the Advantage Local Server.

## 7005 Maximum number of tables exceeded {#7005-maximum-number-of-tables-exceeded}

**Advantage Database Server for Windows**

***Problem:*** The maximum number of configured tables are already in use and the Advantage server was unable to allocate more resources for additional tables.

***Solution:*** Increase the setting for the "Number of Tables" using the Advantage Configuration Utility. If you don't wish to use the Advantage Configuration Utility, increase the setting for the TABLES configuration value in the Advantage Database Server configuration registry key using the Registry Editor. The Advantage Database Server Configuration Registry Key is located in the Registry at: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Advantage\Configuration. Then re-start the Advantage Database Server for Windows.

**Advantage Local Server**

***Problem:*** The maximum number of configured tables are already in use and the Advantage server was unable to allocate more resources for additional tables.

***Solution:*** Increase the setting for the TABLES configuration value in the Advantage Local Server configuration file, ADSLOCAL.CFG. Then re-start the application that uses the Advantage Local Server.

## 7006 Maximum number of index files exceeded {#7006-maximum-number-of-index-files-exceeded}

**Advantage Database Server for Windows**

***Problem:*** The maximum number of configured index files are already in use and the Advantage server was unable to allocate more resources for additional index files.

***Solution:*** Increase the setting for the "Number of Index Files" using the Advantage Configuration Utility. If you don't wish to use the Advantage Configuration Utility, increase the setting for the INDEXES configuration value in the Advantage Database Server configuration registry key using the Registry Editor. The Advantage Database Server Configuration Registry Key is located in the Registry at: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Advantage\Configuration. Then re-start the Advantage Database Server for Windows.

**Advantage Local Server**

***Problem:*** The maximum number of configured index files are already in use and the Advantage server was unable to allocate more resources for additional index files.

***Solution:*** Increase the setting for the INDEXES configuration value in the Advantage Local Server configuration file, ADSLOCAL.CFG. Then re-start the application that uses the Advantage Local Server.

## 7007 Maximum number of locks exceeded {#7007-maximum-number-of-locks-exceeded}

**Advantage Database Server for Windows**

***Problem:*** The maximum number of configured locks are already in use and the Advantage server was unable to allocate more resources for additional locks.

***Solution:*** Increase the setting for the "Number of Data Locks" using the Advantage Configuration Utility. If you don't wish to use the Advantage Configuration Utility, increase the setting for the LOCKS configuration value in the Advantage Database Server configuration registry key using the Registry Editor. The Advantage Database Server Configuration Registry Key is located in the Registry at: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Advantage\Configuration. Then re-start the Advantage Database Server for Windows.

**Advantage Local Server**

***Problem:*** The maximum number of configured locks are already in use and the Advantage server was unable to allocate more resources for additional locks.

***Solution:*** Increase the setting for the LOCKS configuration value in the Advantage Local Server configuration file, ADSLOCAL.CFG. Then re-start the application that uses the Advantage Local Server.

## 7008 Advantage server file open failure {#7008-advantage-server-file-open-failure}

***Problem 1:*** The specified table, memo file, or index file was unable to be opened.

***Solution 1:*** Verify the following:

| · | The file exists and the user has sufficient access rights to open the file. (The location and name of the file that received the 7008 error can be found in the ADS_ERR.ADT or ADS_ERR.DBF file.) |
| --- | --- |

| · | The file is not already open exclusively by another Advantage user. |
| --- | --- |

| · | When opening a table, index, or memo file, verify a non-Advantage application does not already have the file open. If this scenario exists, a file open error will be logged in the Advantage Database Server error log, ADS_ERR.ADT or ADS_ERR.DBF. If an error sequence in consecutive records in the error log exists with error codes 32 and 7008 (for the Advantage Database Server for Windows), this indicates that a non-Advantage application already has the file open, and the Advantage application is attempting to open the file using Advantage Proprietary Locking or in an Exclusive mode. Note that the other application that has the file open could also be backup software or a report writer. If opening a DBF table in a writeable mode, and that DBF is to be shared with a non-Advantage database application, make sure to open the table using Advantage Compatible Locking mode. |
| --- | --- |

| · | When creating a table, index, or memo file, verify that it already exists and another application does not have it opened. |
| --- | --- |

| · | If re-indexing or packing a table using Advantage Data Architect, verify the index, table or memo file is not opened by another application. |
| --- | --- |

| · | If attempting to open a table via the Advantage Local Server, make sure it is not already opened by another connection via the Advantage Database Server. |
| --- | --- |

| · | If attempting to open a table previously referenced by an SQL query, verify that the handle to the query (the cursor handle) was explicitly closed by calling AdsCloseSQLStatement after the executing the query. If the cursor handle was not explicitly closed by calling AdsCloseSQLStatement, the underlying table(s) will remain open in a "cached open" state by the Advantage server to improve the performance of subsequent queries. However, this "cached open" state will cause subsequent attempts to open the underlying table(s) in an exclusive mode to fail with a 7008 error. |
| --- | --- |

***Problem 2:*** This error can occur when the connection to the Advantage Data Dictionary was made using a local-drive-letter path and tables within the dictionary are not on the same drive. Advantage stores the file path of the table relative to the data dictionary file in the data dictionary. If the file path of the table cannot be converted to a relative path, this error is returned.

***Solution 2:*** Open the Advantage Data Dictionary using UNC or through a network drive (the network drive will be converted to UNC). This allows the tables and indexes to be located on a different drive then the one the data dictionary is on. Note that the files must be accessible using a UNC path (i.e., the must be on a share).

***Problem 3:*** This error can occur when making a connection or opening a table from inside a server-side module (such as an extended procedure or a trigger) on a Windows server and using a drive letter. Services cannot resolve a drive letter to a local path, which can lead to a 7008 error.

***Solution 3:*** Use UNC (\\SERVERNAME\SHARE) when making connections or opening tables from inside a server-side module. Also use UNC for any TDataSet aliases that are used from inside a server-side module.

***Problem 4***: This error can occur if you have a trigger on the table you are trying to open, or if you have a trigger that uses the table you are trying to open.

***Solution 4***: Triggers often cache the statement they use to execute the trigger code. If this cached statement references the table you are trying to open exclusively, you can get a 7008 error. All users who have modified the table with the trigger need to close the table (the table the trigger is defined on) before you can gain exclusive access to ANY table modified inside the trigger.

## 7009 Problem with Advantage server file write {#7009-problem-with-advantage-server-file-write}

***Problem 1:*** The Advantage server was unable to write to the specified file.

***Solution1:*** Check the network volume for available disk space.

***Problem 2:*** The data table has exceeded 4 gigabytes and the version of Advantage Database Server doesn't support files over 4 gigabytes.

***Solution 2:*** Upgrade to a version of Advantage Database Server that supports files larger than 4 gigabytes. Contact your Advantage sales representative or distributor for more information.

## 7010 Problem with Advantage server file read {#7010-problem-with-advantage-server-file-read}

***Problem 1:*** The Advantage server was unable to read from the specified file.

***Solution 1:*** Check the status of the network and repeat the command.

***Problem 2:*** An Advantage application may receive 7010 errors if:

| · | DBF tables with FPT memo files are being used. |
| --- | --- |

| · | The FPT memo file was created with a memo block size of 32 or less. |
| --- | --- |

| · | The FPT memo file was created with a database driver that is not completely FoxPro-compatible, such as SuccessWare's SIXCDX RDD, CA-Clipper's DBFCDX RDD, Loadstone's COMIX RDD, Vista Software's Apollo CDX driver, or the Halcyon CDX driver. |
| --- | --- |

Advantage, FoxPro, and any other FoxPro-compatible driver will not be compatible with such an FPT memo file. The above named non-Advantage database drivers do not obey the FoxPro-defined standard with memo blocks of size 32 or less. A block size of 32 is often the default when creating FPT memo files with these non-Advantage database drivers, so it is likely you will run into this incompatibility if the FPT memo files were created by these non-Advantage database drivers.

***Solution 2:*** To alleviate the problem with 7010 errors with DBF tables and FPT memo files created by non-FoxPro compatible database drivers:

| · | Create a new DBF and FPT using an Advantage database driver. |
| --- | --- |

| · | Copy all data from the old DBF and FPT to the new DBF and FPT using the non-Advantage database drivers. |
| --- | --- |

| · | Delete the old DBF and FPT and use the new DBF and FPT. The new DBF and FPT (that were created by the Advantage driver) should be fully functional with both Advantage and non-Advantage database drivers. |
| --- | --- |

***Problem 3:*** 7010 errors may occur when reading an index if the index is corrupt.

***Solution 3:*** If the 7010 error occurs when performing a database operation that uses an index, or if the Advantage error log (ADS_ERR.ADT or ADS_ERR.DBF) indicates the 7010 error occurred when reading an index file, re-building the index will eliminate the index corruption and should eliminate the 7010 error.

## 7011 Problem with Advantage server file seek {#7011-problem-with-advantage-server-file-seek}

***Problem:*** The Advantage server was unable to position to the desired file offset.

***Solution:*** Check the status of the network and repeat the command.

## 7012 Problem with Advantage server file offset {#7012-problem-with-advantage-server-file-offset}

***Problem:*** The Advantage server tried to access an index file on a illegal index page boundary.

***Solution:*** Rebuild the current index.

## 7013 Advantage server file access error {#7013-advantage-server-file-access-error}

***Problem 1:*** The user does not have sufficient access rights to open the specified file.

***Solution 1:*** If you are using the Advantage Database Server for Windows, and your data files are located on a drive using NTFS, that PC’s "system" group must have full access to the share that contains the data in order for the Advantage Database Server service to have access to that data. Note that it must be that PC’s system group that has full access, **not** the domain’s system group.

***Problem 2***: The file(s) is marked read-only.

***Solution 2***:** Remove the read-only attribute on the file(s).

## 7014 Invalid DBF table {#7014-invalid-dbf-table}

***Problem:*** The first byte in the specified DBF table does not indicate a valid DBF table.

***Solution:*** Make sure the file is a valid DBF table.

## 7015 Corrupt NTX {#7015-corrupt-ntx}

***Problem:*** The current NTX index file contains corrupt or invalid data.

***Solution:*** Rebuild the index.

## 7016 Corrupt table {#7016-corrupt-table}

***Problem:*** The specified table contains corrupted data in the file or field headers.

***Solution 1:*** Make sure the specified file is a valid table. Also, make sure you are not attempting to open a DBF table with an ADT table type, or vice versa.

***Solution 2:*** If the table is an ADT (Advantage Proprietary Table), run the ADT table repair utility (ADTFIX.EXE) against the offending ADT table. This utility is available for download from the Advantage Developer Zone Web site in the "Tools & Utilities" section, **http://DevZone.AdvantageDatabase.com**. Once the table is fixed, all indexes on the table must then be rebuilt.

## 7017 Corrupt IDX, CDX, or ADI index {#7017-corrupt-idx-cdx-or-adi-index}

***Problem:*** The current CDX, IDX, or ADI index file contains corrupt or invalid data.

***Solution:*** Rebuild the index.

## 7018 Corrupt index: empty page {#7018-corrupt-index-empty-page}

***Problem:*** The current index file contains an illegal empty page.

***Solution:*** Rebuild the index.

## 7019 Corrupt memo field {#7019-corrupt-memo-field}

***Problem:*** The current record's memo field does not contain an end-of-field marker. The memo field's length is unknown.

***Solution:*** Rebuild the memo file.

## 7020 User logged out {#7020-user-logged-out}

***Problem:*** The watchdog process detected a failed connection and disconnected the user from the Advantage server. All resources acquired by that user have been released.

***Solution:*** The user must reconnect.

## 7021 Maximum tags exceeded {#7021-maximum-tags-exceeded}

***Problem:*** Attempted to open a CDX or ADI file that contains more than 256 tags.

***Solution:*** Use a CDX or ADI file with 256 tags or less.

## 7022 Maximum index levels {#7022-maximum-index-levels}

***Problem:*** The current index is unbalanced. This problem is most likely to occur when using very long index keys and new keys are being added to the index. This error could also occur if the index is corrupt.

***Solution:*** Reindex the file. The reindexed file will be built using the minimum number of levels. This will speed up all future operations using the index. If this does not resolve the problem, reindex with a larger page size (see Index Page Size, or see the API AdsReindex61 in the Advantage Client Engine Help or the method AdsIndexPageSize in the Advantage TDataSet Descendant Help). With a larger index page size, more keys will be stored in each page and will thus reduce the number of levels required. For specific equations showing the correlation between key and page size, see Index Key Size and Page Size Relationships.

## 7023 Index expression not supported {#7023-index-expression-not-supported}

***Problem:*** Attempted to open an index file with an index expression that is not supported by the Advantage Database Server.

***Solution:*** There is no solution. This index cannot be used by Advantage.

## 7024 Removing ghost connection {#7024-removing-ghost-connection}

***Problem***: The client never opened a connection semaphore file. Busy network.

***Solution:*** None. This is a valid occurrence on a busy network. This error is not logged in the error log but is visible by the Advantage Management Utility.

## 7025 Semaphore connection file path too long {#7025-semaphore-connection-file-path-too-long}

***Problem:*** The path to the table being opened is too long to be used for the path when creating the semaphore connection file.

***Solution:*** Shorten the path.

## 7026 Communication packet checksum failed {#7026-communication-packet-checksum-failed}

***Problem:*** Corruption was detected in communication packet.

***Solution:*** None. Communication code will resend the packet. This error is not logged in the error log but is visible by the Advantage Management Utility.

## 7027 User not logged in {#7027-user-not-logged-in}

***Problem:*** The Advantage server received a packet from a user who was not logged into the Advantage server.

***Solution:*** None. This is a valid occurrence on a busy network. This error is not logged in the error log but is visible by the Advantage Management Utility.

## 7028 Invalid open mode {#7028-invalid-open-mode}

***Problem:*** A data or index file was attempted to be opened in a different Advantage Locking mode than it was originally opened. Advantage Locking modes cannot be mixed.

***Solution:*** Check that you are not trying to mix Advantage Locking modes on the data or index file in question. Correct the problem by using the same Advantage Locking mode.

## 7029 Index Sort Buffer Size too small {#7029-index-sort-buffer-size-too-small}

***Problem:*** The Index Sort Buffer Size is not large enough for an index to be built on the server.

***Solution:*** Restart/reload the Advantage server with a larger Index Sort Buffer Size. The Index Sort Buffer Size configuration key word is SORT_BUFFER. The default sort buffer size is 8192 Kbytes. The range for this setting is 1 to 65535 Kbytes. The equation for calculating the minimum Index Sort Buffer Size is located in an Index Sort Buffer Size entry in the Advantage knowledge base. Search for SORT_BUFFER.

## 7030 Missing Advantage configuration file, ADS.CFG or ADSLOCAL.CFG {#7030-missing-advantage-configuration-file-ads-cfg-or-adslocal-cfg}

***Problem:*** This error is applicable to the Advantage Local Server only. The Advantage configuration file, ADSLOCAL.CFG, was not found when the Advantage Local Server DLL was loaded. The ADSLOCAL.CFG configuration file must be located in the current working directory, the Windows system directory, or the client's search path. If the ADSLOCAL.CFG file is not found when the Advantage Local Server DLL is loaded, the configuration defaults will get used and no error will be generated other than this 7030 warning in the error log file.

***Solution:*** Put ADSLOCAL.CFG in the current working directory, the Windows system directory, or the client's search path.

## 7031 Could not get Advantage configuration information {#7031-could-not-get-advantage-configuration-information}

**Advantage Database Server for Windows**

***Problem:*** The Advantage Configuration Registry Key could not be opened when the Advantage Database Server Service was started.

***Solution:*** Make sure the Advantage Configuration Registry Key exists. The Advantage Configuration Registry Key is located in the Registry at: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Advantage\Configuration. The Registry can be viewed via the Registry Editor.

**Advantage Database Server for Linux**

***Problem:*** The Advantage Database Server for Linux configuration file, ads.conf, could not be opened when the Advantage Database Server was loaded.

***Solution:*** Make sure no one is viewing or editing the Advantage Database Server configuration file, ads.conf, when the Advantage Database Server is being loaded.

**Advantage Local Server**

***Problem:*** The Advantage Local Server configuration file, ADSLOCAL.CFG, could not be opened when the Advantage Local Server DLL was loaded. If the ADSLOCAL.CFG could not be opened when the Advantage Local Server DLL is loaded, the configuration defaults will get used and no error will be generated other than this 7031 warning in the error log file.

***Solution:*** Make sure no one is viewing or editing the Advantage Local Server configuration file, ADSLOCAL.CFG, when the Advantage Local Server DLL is being loaded.

## 7032 Error in Advantage configuration parameter/value/data {#7032-error-in-advantage-configuration-parameter-value-data}

**Advantage Database Server for Linux**

***Problem:*** An invalid Advantage Database Server configuration parameter or parameter value was detected in the Advantage Database Server configuration file (ads.conf) when the Advantage Database Server was loaded.

***Solution:*** Correct the configuration file parameter or parameter value in question and then load the Advantage Database Server. The configuration file line number containing the error is displayed on the file server system console screen when the Advantage Database Server was attempted to be loaded.

**Advantage Database Server for Windows**

***Problem:*** An invalid Advantage Database Server configuration value or value data was detected in the Advantage Database Server configuration registry key when the Advantage Database Server service was started.

***Solution:*** To correct the configuration value data, use the Advantage Database Server Configuration Utility. To correct or remove invalid configuration values, use the Registry Editor. The Advantage Database Server Configuration Registry Key is located in the Registry at: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Advantage\Configuration.

**Advantage Local Server**

***Problem:*** An invalid Advantage Local Server configuration parameter or parameter value was detected in the Advantage Local Server configuration file (ADSLOCAL.CFG) when the Advantage Local Server DLL (ADSLOC32.DLL) was loaded.

***Solution:*** Correct the configuration file parameter or parameter value in question and then re-start the application using the Advantage Local Server.

## 7033 Maximum Number of Connections Exceeded {#7033-maximum-number-of-connections-exceeded}

**Advantage Database Server for Linux**

***Problem:*** The maximum number of connections are already connected to the Advantage server and the Advantage server was unable to allocate more resources for additional connections.

***Solution:*** Increase the setting for the CONNECTIONS configuration value in the Advantage Database Server for Linux configuration file, ads.conf. Then re-load the Advantage Database Server for Linux.

**Advantage Database Server for Windows**

***Problem:*** The maximum number of connections are already connected to the Advantage server and the Advantage server was unable to allocate more resources for additional connections.

***Solution:*** Increase the setting for the "Number of Connections" using the Advantage Configuration Utility. If you don't wish to use the Advantage Configuration Utility, increase the setting for the CONNECTIONS configuration value in the Advantage Database Server configuration registry key using the Registry Editor. The Advantage Database Server Configuration Registry Key is located in the Registry at: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Advantage\Configuration. Then re-start the Advantage Database Server for Windows.

**TCP/IP Connections To Advantage Database Server**

***Problem:*** The maximum number of TCP connections are already connected to the Advantage server. .

***Solution:*** The maximum number of concurrent TCP connection to the Advantage Database server is 3000 in 9.x and later release, 1000 in earlier releases. This limit cannot be adjusted. To avoid too many TCP connections to the server, configure the clients to use UDP/IP for communication.

**Advantage Local Server**

***Problem:*** The maximum number of connections are already connected to the Advantage server and the Advantage server was unable to allocate more resources for additional connections.

***Solution:*** Increase the setting for the CONNECTIONS configuration value in the Advantage Local Server configuration file, ADSLOCAL.CFG. Then re-start the application that uses the Advantage Local Server.

## 7034 Not a Compound Index File {#7034-not-a-compound-index-file}

***Problem:*** A tag was being added to a file that is not a compound index file (CDX file).

***Solution:*** Use a compound index file for operation.

## 7035 Record not visible {#7035-record-not-visible}

***Problem:*** The application is trying to GOTO a record number that is being appended by another application during a transaction.

***Solution:*** The user will be positioned to EOF. This behavior exists because records appended during another client’s transactions are "invisible" to all other users until that transaction is committed.

## 7036 Failed transaction recovery error {#7036-failed-transaction-recovery-error}

***Problem:*** A failed transaction recovery was not successful.

***Solution:*** Make sure the table or index files associated with the failed transaction were not opened by another application. This error can also occur if the transaction log file could not be opened. Refer to the error log file (ADS_ERR.ADT or ADS_ERR.DBF) for more specific errors related to this failure.

## 7037 Error with key in custom index {#7037-error-with-key-in-custom-index}

***Problem:*** Attempted to add a key for the current record into the custom index and the key already exists.

***Solution:*** You cannot add a key to a custom index more than once for a single record. Do not call the AX_KeyAdd() function if a key already exists in the custom index for the current record.

## 7038 Invalid record number {#7038-invalid-record-number}

***Problem:*** Attempted to read a record and the record number is greater than the number of records in the file. This error often results from using an index that contains more keys than the table has records. This can occur if a Pack or Zap is performed on the table when the index file(s) was closed.

***Solution:*** Reposition to a valid record number. Reindex the index(es) that contain more keys than the table has records.

## 7039 File already open {#7039-file-already-open}

A sharing mode mismatch has occurred. Another user or connection has the file in question opened with a conflicting sharing mode.

***Problem1:*** The user attempted to open a table or an index file for EXCLUSIVE use when another user already had the file open in SHARED mode.

***Solution1:*** Determine which user(s) has the specified file open in SHARED mode and have that user(s) close the file before attempting to open the file for EXCLUSIVE use.

***Problem2:*** The user attempted to open a table or an index file for SHARED use when another user already had the file open in EXCLUSIVE mode.

***Solution2:*** Determine which user(s) has the specified file open in EXCLUSIVE mode and have that user(s) close the file before attempting to open the file

***Problem3:*** The user attempted to open a table or an index file for EXCLUSIVE use when another user already had the file open in EXCLUSIVE mode.

***Solution3:*** Determine which user(s) has the specified file open in EXCLUSIVE mode and have that user(s) close the file before attempting to open the file.

***Problem4:*** The user attempted to open an index file that was already open on another table.

***Solution4:*** A single index file can only be associated with one table. The error log's MORE_INFO field will contain the name of the original table that opened the index.

## 7040 File creation error {#7040-file-creation-error}

***Problem:*** An error occurred when attempting to create a table or an index file.

***Solution:*** Verify the directory where the file is to be created is accurate and exists. If the file already exists, verify no other users currently have the specified file open. Make sure the user has sufficient access rights to create and open the specified file (if using Advantage "check rights" security with free tables).

## 7041 File not found {#7041-file-not-found}

***Problem:*** The table or index file to be opened does not exist.

***Solution:*** Make sure the directory where the file is to be opened is accurate and exists.

## 7042 Invalid bits set in the TPS semaphore byte {#7042-invalid-bits-set-in-the-tps-semaphore-byte}

***Problem:*** With DBF tables, the byte being used for the Transaction Processing System (TPS) semaphore byte (either the "deleted" byte or the AXS_TPS field, if one exists) has bits set that are invalid for that byte.

With ADT tables, the bytes being used to store TPS information contains invalid data for those bytes. This error usually has nothing to do with the use of transaction processing itself. For some reason, data in the TPS semaphore byte(s) is being corrupted.

With DBF tables, a non-Advantage product is most likely causing the corruption. With ADT tables, the server likely crashed in the midst of a transaction, and the transaction was not properly recovered from when the Advantage Database Server was restarted. The previous Advantage Database Server error log file (ADS_ERR.ADT or ADS_ERR.DBF) entry contains the record number of the record that has invalid bits in its TPS semaphore byte(s) in the error_code field.

***Solution for DBF tables:*** When not in a transaction, clear the invalid bits in the TPS semaphore byte. If the semaphore byte is the "deleted" byte, open the DBF table via a non-Advantage driver. Then loop through all records in the table re-marking all records for deletion that are currently marked for deletion and recalling all records that are not currently marked for deletion. If the TPS semaphore byte is the AXS_TPS field, open the table (doesn't matter which driver is used), and then loop through all records in the DBF table and clear all contents in the AXS_TPS field by replacing the field with a single space " ". If 7042 errors keep recurring, determine what product or operation corrupts the TPS semaphore byte, and have the product fixed or the operation altered.

***Solution for ADT tables:*** Run the ADT table repair utility (ADTFIX.EXE) against the offending ADT table. This utility is available for download from the Advantage Developer Zone Web site in the "Tools & Utilities" section, **http://DevZone.AdvantageDatabase.com**.

## 7043 Advantage Database Server for Windows is paused {#7043-advantage-database-server-for-windows-is-paused}

***Problem***: The Advantage Database Server for Windows is paused and is not accepting database requests.

***Solution***: Un-pause the Advantage Database Server for Windows.

## 7044 Advantage Server already on network {#7044-advantage-server-already-on-network}

***Problem:*** When the Advantage server was started/loaded, another Advantage server with an identical serial number was found on the network.

***Solution:*** Additional copies (each with its own serial number) must be purchased in order for multiple copies of the Advantage Database Server to be running simultaneously on the network.

## 7045 Serial number and validation code mismatch {#7045-serial-number-and-validation-code-mismatch}

***Problem:*** The serial number does not match the validation code.

***Solution:*** Reinstall the Advantage Database Server.

## 7046 Evaluation period expired {#7046-evaluation-period-expired}

***Problem:*** The evaluation period of the Advantage Database Server has expired.

***Solution***: Contact iAnywhere or your local Advantage distributor and purchase a full copy of Advantage Database Server.

## 7047 Invalid bits set in the deleted byte {#7047-invalid-bits-set-in-the-deleted-byte}

***Problem:*** The "deleted" byte, which is the first byte in a table record that is used to indicate whether the record is marked for deletion or not, has bits set that are invalid for that byte. The previous log file entry contains the record number of the record that has invalid bits in its "deleted" byte.

***Solution:*** Clear the invalid bits in the "deleted" byte. Open the table exclusively via a non-Advantage driver. Then loop through all records in the table re-marking all records for deletion that are currently marked for deletion and recalling all records that are not currently marked for deletion.

## 7048 EXTEND.CHR or ANSI.CHR file not found at load time by the Advantage Local Server {#7048-extend-chr-or-ansi-chr-file-not-found-at-load-time-by-the-advantage-local-server}

***Problem:*** When the Advantage Local Server DLL was loaded, the EXTEND.CHR or ANSI.CHR file could not be found. The Advantage Local Server will not be available to the Advantage application.

***Solution:*** Put the EXTEND.CHR or ANSI.CHR file somewhere in your client PC's search path (e.g., your \WINDOWS\SYSTEM) directory.

## 7049 Error occurred when the Advantage Local Server attempted to use the EXTEND.CHR or ANSI.CHR file {#7049-error-occurred-when-the-advantage-local-server-attempted-to-use-the-extend-chr-or-ansi-chr-file}

***Problem:*** The Advantage Local Server had a problem when using the EXTEND.CHR or ANSI.CHR file. Either it could not be opened, could not be read from, or did not contain the expected data.

***Solution:*** Verify the OEM_CHAR_SET configuration setting in ADSLOCAL.CFG is a valid OEM character set language available in EXTEND.CHR. Also verify the ANSI_CHAR_SET configuration setting in ADSLOCAL.CFG is a valid ANSI character set language available in ANSI.CHR. Re-install the EXTEND.CHR or ANSI.CHR from the installation diskette.

## 7050 The user is not connected to the Advantage server {#7050-the-user-is-not-connected-to-the-advantage-server}

***Problem:*** The user specified in an Advantage Management API is not currently connected to the Advantage server.

***Solution:*** Specify a user who is connected to the Advantage server.

## 7051 The file is not open on the Advantage server {#7051-the-file-is-not-open-on-the-advantage-server}

***Problem:*** The file specified in an Advantage Management API is not currently open on the Advantage server.

***Solution:*** Specify a file that is open on the Advantage server. The file name should be specified using the path that corresponds to the client making the Advantage Management API call. Look up the associated 7051 error in the Advantage error log file, and verify the filename in that log entry is what you expect it to be.

## 7052 Cannot operate on the same table as source and destination {#7052-cannot-operate-on-the-same-table-as-source-and-destination}

***Problem:*** A Copy To or Append From operation was attempted where the source table and the destination table are the same table.

***Solution:*** Specify different source and destination tables before attempting the Copy To or Append From operations.

## 7053 VarChar fields are not supported with this operation {#7053-varchar-fields-are-not-supported-with-this-operation}

***Problem***: A Copy To, Append From, Copy Table, Copy Table Contents, or Memo Pack operation was attempted but the table contained at least one VarChar field (a.k.a. weakly-typed VariField). The Copy To, Append From, Copy Table, Copy Table Contents, and Memo Pack operations cannot handle VarChar fields.

***Solution***:** Specify tables that do not contain VarChar fields before attempting the Copy To, Append From, Copy Table, Copy Table Contents, or Memo Pack operations. This error will result if a pack operation is performed on an encrypted table. To perform the pack operation, first decrypt the table. Once finished, the table may be encrypted again.

## 7054 Field data type mismatch {#7054-field-data-type-mismatch}

***Problem:*** A Copy To or Append From operation was attempted where the source table and the destination table contained fields with the same name, but of different data type.

***Solution***: Do not use source and destination tables that contain fields with the same name but different data types when attempting the Copy To or Append From operations.

## 7055 Field size mismatch {#7055-field-size-mismatch}

***Problem:*** A Copy To or Append From operation was attempted where the source table and the destination table contained numeric fields with the same name, but of different width or number of decimals.

***Solution:*** Do not use source and destination tables that contain numeric fields with the same name but different width or decimals before attempting the Copy To or Append From operations.

## 7056 Invalid Connection Path {#7056-invalid-connection-path}

***Problem 1:*** An invalid path was specified when connecting to the Advantage Database Server. The Advantage Database Server was unable to create the semaphore connection file.

***Problem 2***: An invalid path (catalog) was specified when connecting to the Advantage Database Server by the JDBC Client.

***Solution:*** Specify a valid path (catalog) when connecting to the Advantage Database Server.

## 7057 Record update failed {#7057-record-update-failed}

***Problem***: The key value produced from this record was not unique, and the index for the current table has the UNIQUE property.

***Solution***: Replace the key value field(s) with a unique value(s). If this is not possible, cancel the operation. When using the Advantage Client Engine API directly, call AdsCancelUpdate. When using the Advantage TDataSet Descendant, use the TTable.Cancel method.

## 7058 Corrupt ADI index {#7058-corrupt-adi-index}

***Problem***: The current ADI index file contains corrupt or invalid data. It is possible that the index file was created with a version of Advantage Database Server greater than the version you are currently using. For example, if Advantage Database Server 7.0 or greater is used to build a full text search (FTS) index, it is not possible to open that index file with prior versions of Advantage.

***Solution***: Rebuild the index.

## 7059 Unique index creation error {#7059-unique-index-creation-error}

***Problem***: An index with the UNIQUE property was not able to be created because data in the table produced non-unique key values.

***Solution***: Make sure that the table data used to create the unique index is unique. When the record(s) was found that would cause a non-unique key to be place in the index, an error was logged in the Advantage error log (ADS_ERR.ADT or ADS_ERR_.DBF). That error log entry will indicate the record number, the tag name, and the index name associated with the non-unique index value. Use the Advantage error log to determine which records are in violation of the uniqueness property.

## 7060 Invalid Password {#7060-invalid-password}

***Problem:*** An invalid or incorrect password was specified when enabling encryption. Thus, the encryption is not enabled and the encrypted records in the table cannot be decrypted or updated.

***Solution:*** Specify a valid password when enabling encryption. The encryption password of a table is set the first time encryption is enabled on the table by a user. The password can be cleared by decrypting the table with the correct password.

***Problem:*** An invalid password for AES encryption was provided via the SE_Passwords server configuration option or the equivalent /SEPasswords command line parameter.

***Solution:*** Verify that the SE_Passwords configuration parameter value is correct. The error log should show which dictionary or table the invalid password was applied to.

## 7061 Encryption Version Mismatch {#7061-encryption-version-mismatch}

***Problem:*** Some records in the table are already encrypted using an encryption method that is not supported by this version of the Advantage Database Server. Thus, the Advantage Database Server was unable to enable encryption on this table.

***Solution:*** The table must be decrypted using the version of the Advantage Database Server and the Advantage client that encrypted the records in the table originally.

## 7063 Query table full {#7063-query-table-full}

***Problem***: The maximum number of configured query elements is already in use.

***Solution***: The maximum number of configured query elements is the same as the configured work areas. There are two possible solutions: 1) Restart/reload the Advantage server with a larger value for number of work areas; 2) Make sure that query handles are freed after they are no longer used.

## 7064 The IP protocol is not installed on the current machine {#7064-the-ip-protocol-is-not-installed-on-the-current-machine}

This is an informational error log entry. Only be concerned if the IP protocol is supposed to be installed and functioning.

## 7065 Updates to records must meet the conditions of the SQL SELECT statement because the Constrained option has been selected {#7065-updates-to-records-must-meet-the-conditions-of-the-sql-select-statement-because-the-constrained-option-has-been-selected}

***Problem***: The updated record did not meet the WHERE clause of the SQL SELECT statement.

***Solution***: To correct this, turn off the CONSTRAINED option of the Advantage Client Engine SQL statement.

## 7066 Old Encryption Version {#7066-old-encryption-version}

***Problem***: Either the encryption algorithm used to encrypt data in this table used an old and obsolete algorithm, or the Advantage client is attempting to use old and obsolete encryption APIs.

***Solution***: Either convert your tables to have encrypted data via the latest encryption algorithm, or upgrade your Advantage client software to the version that uses the latest encryption technology.

## 7068 Encryption password is required for this operation {#7068-encryption-password-is-required-for-this-operation}

***Problem:*** The attempted operation requires modifying encrypted records but the encryption password is not supplied.

***Solution:*** Supply the encryption password before performing the operation.

***Problem:*** An attempt was made to connect to a data dictionary encrypted with AES without providing a dictionary password.

***Solution:*** Provide the dictionary password either in the SE_Passwords server configuration parameter or the DDPassword connection option.

***Problem:*** The server fails to start and logs a 7068 error. This may signify that failed transaction log files exist that are encrypted with AES.

***Solution:*** Provide the dictionary password (or free table passwords) either in the SE_Passwords server configuration parameter or the equivalent /SEPasswords command line parameter.

## 7069 The latest version of the Advantage client software is required with this version of the Advantage Database Server {#7069-the-latest-version-of-the-advantage-client-software-is-required-with-asd}

***Problem***: An operation was attempted that requires a newer version of the Advantage client software.

***Solution***: Upgrade your Advantage Client Engine-based product to the version that matches the Advantage Database Server version. In general, newer versions of the server are compatible with older clients, but if the application attempts to access new functionality, it may require a client update.

## 7071 File is too large to be opened with the given settings {#7071file-is-too-large-to-be-opened-with-the-given-settings}

***Problem***: An open table greater than 4GB in size was attempted with compatibility locking. Due to lock offsets required to implement record locking that can be shared across applications (either non-Advantage applications or applications that use Advantage Local Server), the table cannot be opened.

***Solution***: If you are using Advantage Database Server, open the table with proprietary locking. With Advantage Local Server, it is necessary to open the table in exclusive mode.

**Note** For information about table sizes with each operating system, see Advantage Proprietary File Format Specifications.

## 7072 The memo file associated with this table is corrupt {#7072the-memo-file-associated-with-this-table-is-corrupt}

***Problem:*** The memo file associated with this table is corrupt.

***Solution:*** If you are using ADT tables, download the **adtfix** utility from the Advantage Developer Zone (devzone.advantagedatabase.com) and run the utility on the ADT table that logged this error. If you are using DBF tables, use a third-party DBF repair utility to repair the table and memo file.

## 7073 The maximum number of memo blocks has been reached {#7073-the-maximum-number-of-memo-blocks-has-been-reached}

***Problem***: The number of blocks in the memo file has reached the 4,294,967,296 block (4 GB) limit.

***Solution 1***: Create a new table with the same structure as the table in question, but with a larger memo block size. Copy all data from the old table into the new table. See documentation in your client help file for more information on choosing a memo block size.

***Solution 2***: It is possible that memo blocks can be orphaned in memo files. Packing the table will free these orphaned blocks and allow them to be used again.

## 7074 The table ID stored in the ADT table does not match the ID stored in the Advantage Data Dictionary file {#7074-the-table-id-stored-in-the-adt-table-does-not-match-the-id-stored-in-the-advantage-data-dictionary-file}

***Problem:*** When opening a database table, the table ID stored in the .ADT table header does not match the corresponding table ID stored in the Advantage Data Dictionary. The cause of this error is likely the result of overwriting an existing .ADT table or overwriting an existing data dictionary file.

***Solution:*** Avoid using the file system to overwrite an existing database table file or data dictionary file. Use the Advantage Client Engine API or the Advantage Data Dictionary Management Utility to copy a table and modify the data dictionary file. If a table file is inadvertently deleted without it being removed from the Advantage Data Dictionary first, it can be restored by using the table's auto-creation property. The Advantage Data Architect also has this functionality built into it and can be accessed in the table's properties.

## 7075 The Advantage Local Server version allows a maximum of 5 users to access a file at one time. {#7075-the-advantage-local-server-version-allows-a-maximum-of-5-users-to-access-a-file-at-one-time-the-limit-has-been-exceeded}

***Problem:*** The maximum of five (5) licensed users for Advantage Local Server has been exceeded.

***Solution 1:*** A maximum of five concurrent users are allowed to access the Advantage Local Server. Have any users not currently using the Advantage Local Server logout to allow access by another user. To allow more than five concurrent users, contact your Advantage Database Server reseller to expand the number of concurrent users.

***Solution 2:*** If an application does not terminate properly and close each table it has open, the tables it had open may be left with an incorrect open count. To resolve this problem, either open and close the table from the same workstation as the application improperly terminated, or open the table exclusively from any workstation to reset the open count to one.

## 7076 No Primary key was found for the foreign key {#7076-no-primary-key-was-found-for-the-foreign-key}

***Problem:*** No primary key was found for the foreign key being inserted or modified.

***Solution:*** Modify the record and re-post it with a correct foreign key value.

## 7077 The Advantage Data Dictionary cannot be opened {#7077-the-advantage-data-dictionary-cannot-be-opened}

***Problem 1:*** The auto-created ADT table cannot be opened from the command line or Windows Explorer using Advantage Data Architect.

***Solution 1:*** Select File|Open Table and specify the path to the Advantage Data Dictionary the table is bound to. This error only affects Advantage Data Architect.

***Problem 2:*** The file is not a valid Advantage Data Dictionary file.

***Solution 2:*** Make sure the connect path specifies a directory instead of a file.

***Problem 3:*** The specified data dictionary file is already opened by the Advantage Local Server and the Advantage Database Server is trying to open the same data dictionary.

***Solution 3:*** Change the configuration of all users to use the same server type to connect to the data dictionary.

***Problem 4:*** The specified data dictionary file is already opened by the Advantage Database Server and the Advantage Local Server is trying to open the same data dictionary.

***Solution 4:*** Change the configuration of all users to use the same server type to connect to the data dictionary.

***Problem 5:*** This error can occur when making a connection or opening a table from inside a server-side module (such as an extended procedure or a trigger) on a Windows server and using a drive letter. Services cannot resolve a drive letter to a local path, which can lead to a 7008 error.

***Solution 5:*** Use UNC (\\SERVERNAME\SHARE) when making connections or opening tables from inside a server-side module. Also use UNC for any TDataSet aliases that are used from inside a server-side module.

## 7078 The Advantage Database Server cannot authenticate the user {#7078-the-advantage-database-server-cannot-authenticate-the-user}

***Problem:*** This error was caused by one of the following.

| · | The user name and password supplied when connecting to an Advantage Data Dictionary were incorrect. |
| --- | --- |

| · | The user name and password were not supplied but the Data Dictionary has been set up to require user authentication. |
| --- | --- |

***Solution:***

| · | Verify the user name and password is correct. |
| --- | --- |

| · | Set up the Advantage Data Dictionary so that it does not require user authentication. |
| --- | --- |

## 7079 The user does not have read permission to the table {#7079-the-user-does-not-have-read-permission-to-the-table}

***Problem:*** The database has been set up to verify user’s access rights when opening a table or view. The user who is attempting to open the table or view for read access has not been granted read permission to the specified table or view.

***Solution:*** Use the data dictionary administrative API or the Advantage Data Dictionary Management Utility to grant proper permission to the user.

## 7080 The user does not have write rights to the table {#7080-the-user-does-not-have-write-rights-to-the-table}

***Problem:*** The database has been set up to verify user’s access rights when opening a table or view. The user who is attempting to open the table for read and write access has not been granted write right to the specified table or view.

***Solution:*** Use the data dictionary administrative API or the Advantage Data Dictionary Management Utility to grant proper rights to the user.

## 7081 The encrypted table is using an older encryption method {#7081-the-encrypted-table-is-using-an-older-encryption-method}

***Problem:*** The table was encrypted using an older encryption method (40-bit encryption) that only used the first five characters of the password to encrypt the table. With version 6.0 or greater of the Advantage Database Server, the first 20 characters (160-bit encryption) are used to encrypt the table. If the password is longer than five characters and the table was encrypted using 40-bit encryption, a 7081 error is logged in the error log file.

***Solution:*** This error is not returned to the Advantage client because it is an informational error only. This error can be ignored. The server and client will automatically support the old encryption method.

To stop the errors being logged to the error log file, use one of the following methods.

| · | To use ***160-bit encryption***, make sure all clients are at least version 6.0 or greater. Decrypt the table and then encrypt the table. The table will now be encrypted using the first 20 characters of the password. |
| --- | --- |

| · | To continue to use ***40-bit encryption***, enter only five characters of the password as the password. The server will no longer log the 7081 errors since the password is not more than five characters long. |
| --- | --- |

## 7082 Internet access disabled {#7082-internet-access-disabled}

***Problem:*** This error indicates that the Internet access has been disabled and can be caused by the following:

| · | The Advantage Data Dictionary does not have Internet access enabled. |
| --- | --- |

| · | The user object in the Advantage Data Dictionary does not have Internet access enabled. |
| --- | --- |

| · | An Internet user has failed a successful login after several consecutive failed attempts. This causes Internet access for that user to be disabled. |
| --- | --- |

***Solution***:** Check the following:

| · | Make sure that the Advantage Data Dictionary is enabled for Internet access. |
| --- | --- |

| · | Make sure that the user in the Advantage Data Dictionary is enabled for Internet access. |
| --- | --- |

| · | If the user was disabled after several failed login attempts, someone may be trying to break in to the system. |
| --- | --- |

## 7083 An Advantage Data Dictionary connection is required {#7083-an-advantage-data-dictionary-connection-is-required}

***Problem 1***: When connecting to the Advantage Database Server through an Internet connection, a 7083 error is returned and the connection fails.

***Solution 1:*** The Advantage Data Dictionary contains user names, passwords, and other necessary information required for a secure connection over the Internet. All Internet connections require an Advantage Data Dictionary connection. In the connection path, specify the full path and file name of the Advantage Data Dictionary.

***Problem 2***: When connecting to the Advantage Database Server with a non-Internet connection, a 7083 error is returned and the connection fails. This error will occur if the Advantage Database Server has been configured to disallow free connections.

***Solution 2***: In the connection path, specify the full path and file name of the Advantage Data Dictionary, or turn off the DISABLE_FREE_CONNECTIONS configuration parameter.

***Problem 3***: Advantage Database Server failed to get a connection to the target database to perform a replication update. If this occurs, the error class will be 7600.

***Solution 3***: An Advantage Data Dictionary is required for performing replication updates. Edit the subscription and verify that the target database is a valid Advantage data dictionary.

## 7084 Compression not allowed {#7084-compression-not-allowed}

This error code should never be seen by a client application. It is logged for informational purposes when Advantage Database Server is configured to disallow compression (COMPRESSION=Never) and the client specifically attempts to turn compression on. See Communications Compression for more information.

## 7085 Invalid UNC server name {#7085-invalid-unc-server-name}

Remote Server

***Problem:*** A UNC path passed to the server does not match the server’s computer name.

***Solution:*** This indicates an internal error. Contact Advantage Technical Support.

Local Server

***Problem:*** There was an error reading the UNC server name from the REPLACE_UNC_SERVER key in the ads.ini file. Either the ads.ini file could not be found or the server name specified was not found.

***Solution:*** Verify the ads.ini file is in the search path and that an entry exists for the server used in the connection string.

## 7086 Cannot open table directly {#7086-cannot-open-table-directly}

***Problem:*** The database table cannot be opened directly for navigational access because the database administrator has set up the table to be accessed through SQL only.

***Solution:*** Use SQL "SELECT ... " statement to access the table. If navigational access is required, the database administrator must change the table permission level to allow such access.

## 7087 Permission not granted for the requested operation {#7087-permission-not-granted-for-the-requested-operation}

***Problem:*** An operation on a database table failed because it requires permission not granted to the user performing the operation. Some of the possible causes are:

| · | Attempting to update an existing row in the table but the UPDATE permission was not granted on the table or not granted on some columns to be modified, |
| --- | --- |

| · | Attempting to insert a new row in the table but the INSERT permission was not granted on the table |
| --- | --- |

| · | Attempting to delete a row in a table but the DELETE permission was not granted on the table |
| --- | --- |

| · | Attempting to set a filter or scope on a table but the filter expression or the scope index contains columns that the user has no READ permission |
| --- | --- |

***Solution:*** If the requested operation is necessary, the database administrator must grant the user the appropriate permission.

***Problem:*** An attempt to open a free table failed because access to free table is restricted on this database connection.

***Solution:*** If the requested operation is necessary, the application must not set the CheckFreeTableAccess option to true when connecting to the data dictionary.

## 7088 The user could not be disconnected at this time {#7088-the-user-could-not-be-disconnected-at-this-time}

***Problem:*** When attempting to disconnect a user from the server by performing a "kill user" management operation, a 7088 error occurs.

***Solution:*** The "kill user" management operation failed because the server is processing a request from the user that cannot be stopped at this time. Retry the "kill user" operation at some later time when the user's current operation has completed.

## 7089 Index creation aborted by the user {#7089-index-creation-aborted-by-the-user}

***Problem:*** An index creation was aborted by the user.

***Solution***:** Re-issue the index creation operation if you'd like the index to exist.

## 7090 Copy table or alter table operation aborted by user {#7090-copy-table-or-alter-table-operation-aborted-by-user}

***Problem:*** A copy table or alter table operation was aborted by the user.

***Solution***:** Re-issue the copy table or alter table operation if you'd like the table data to be copied or the alter table to continue.

## 7091 Collation sequence used to create the index differs from current collation sequence {#7091-collation-sequence-used-to-create-the-index-differs-from-current-collation-sequence}

***Problem:*** Advantage detected a mismatch between the collation sequence used to create the index file and the current collation sequence.

***Solution:*** See error code [5175](5xxx-errors.md#5175-ae-index-collation-mismatch) for more information about this error. The 7091 error is only written to the error log. If you are using a client that is version 6.2 or greater, the client will also detect the mismatch and return a 5175 error.

## 7092 The index is not Advantage compatible {#7092-the-index-is-not-advantage-compatible}

***Problem:*** Advantage has detected that the index was not built with an Advantage-compatible format. This problem can occur if the original index was built with the CA-Clipper 5.3 DBFCDX RDD, which does not create FoxPro-compatible indexes.

***Solution:*** Rebuild the index with Advantage. For example, open the table with Advantage Data Architect and click the re-index button, or choose **Re-Index** from the Table menu.

If you get this error when using the Advantage proprietary table format (.ADT/.ADI), report the error to Advnatage Technical Support.

## 7093 Maximum number of recursion levels exceeded {#7093-maximum-number-of-recursion-levels-exceeded}

The maximum number of recursion levels has been exceeded. This means a server-side process (such as an extended procedure, trigger, etc.) has re-entered the server too many times. The recursion was stopped to avoid a run-away server thread.

## 7094 The full text search condition has an unclosed phrase {#7094-the-full-text-search-condition-has-an-unclosed-phrase}

***Problem:*** The full text search condition specified in a CONTAINS() function has an unclosed word or phrase.

***Solution:*** Verify that quoted words and phrases have closing quotes. Words and phrases that are opened with double quote values must be closed. To include a double quote character in the search condition, specify two of them in a row.

## 7095 The full text search condition has an unclosed expression {#7095-the-full-text-search-condition-has-an-unclosed-expression}

***Problem:*** The full text search condition specified in a CONTAINS() function has an unclosed expression.

***Solution:*** Verify that the parentheses are balanced in the search condition. For example, the search condition "medical and (doctor or nurse" is not valid because there is no closing parenthesis.

## 7096 The full text search condition is missing a phrase or word {#7096-the-full-text-search-condition-is-missing-a-phrase-or-word}

***Problem:*** The full text search condition specified in a CONTAINS() function is not formed correctly. It is missing an expected search word or sub-expression.

***Solution:*** Verify that the search condition is not empty and that logical operators are balanced with search words. For example, the search condition "medical and or doctor" is not valid because a search word or condition is expected after the logical operator "and".

## 7097 The full text search condition is not valid {#7097-the-full-text-search-condition-is-not-valid}

***Problem:*** The full text search condition specified in a CONTAINS() function has extraneous information at the end of the condition, or it does not have balanced parentheses.

***Solution:*** Verify that the parentheses and logical operators are balanced. For example, the search condition "medical and doctor)" is not valid because it does not have an opening parenthesis.

## 7098 The full text search condition has invalid operands specified for the NEAR operator {#7098-the-full-text-search-condition-has-invalid-operands-specified-for-the-near-operator}

***Problem:*** The full text search condition specified in a CONTAINS() function has invalid operands specified for the NEAR operator. The NEAR operator cannot have a NOT condition as an operand..

***Solution:*** Verify the operands to the NEAR operator do not contain NOT conditions. For example, the following two search conditions are not valid:

"(medical and not doctor) near hospital"

"landscaping near () (not shrubbery)"

The following two are valid:

"medical near hospital and not (doctor near hospital)"

"not (landscaping near shrubbery)"

## 7099 The full text search condition has an invalid distance specified for the NEAR operator {#7099-the-full-text-search-condition-has-an-invalid-distance-specified-for-the-near-operator}

***Problem:*** The full text search condition specified in a CONTAINS() function has an invalid distance parameter specified for the NEAR operator.

***Solution:*** Verify that the NEAR parameter value is numeric. The NEAR operator can have an optional distance value specified in parentheses. The distance value must be a numeric value. For example, the following search condition is not valid because the parser expects the distance operator to be given:

dog near (cat and mouse)

The following search conditions are valid:

dog near() (cat and mouse)

dog near(5) cat

dog near cat

## 7100 Unrecognized full text search index version {#7100-unrecognized-full-text-search-index-version}

***Problem:*** The full text search index version is not recognized by this release of the software.

***Solution:*** Make sure the version of Advantage you are using is the same as or greater than the version that created the full text search index.

## 7101 Failed Transaction Recovery successful {#7101-failed-transaction-recovery-successful}

***Problem:*** The Advantage Database Server successfully performed a Failed Transaction Recovery upon server startup. This warning will typically be logged to the Advantage Database Server error log file, when a failed transaction recovery was necessary due to a server crash while one or more transactions were in progress. If this warning is logged, it means that upon restarting, the Advantage Database Server was able to successfully recover all transactional data, and the database should be a known and stable state. This warning is logged for informational purposes only. See Advantage Transaction Processing System Features for additional information.

***Solution:*** None.

## 7102 No full text search indexes found {#7102-no-full-text-search-indexes-found}

***Problem:*** Use of CONTAINS( *, 'condition' ) requires at least one full text search index. The asterisk (*) indicates that all fields that have full text search indexes are to be searched, but the table does not have any full text search indexes available or the user does not have read permissions to any of the columns that have full text search indexes.

***Solution:*** Create at least one full text search index or specify a particular field to search in the CONTAINS condition. If using a data dictionary with permissions checking turned on, verify that the user has read permission to at least one column that has a full text search index. Note that specifying a specific field to search that does not have a full text search index forces a low level search of the data, which can be slow.

## 7103 The full text search condition is empty {#7103-the-full-text-search-condition-is-empty}

***Problem:*** The full text search condition does not have any valid search words. It is possible, for example, to specify a search condition that contains only noise words. The full text search engine ignores noise words that are in the search condition. If the condition consists of nothing but noise words, or words that are shorter than the minimum word length, then the engine has nothing to search for.

***Solution:*** Verify that the search condition consists of at least one non-noise word.

## 7104 Transaction processing is not available on current connection {#7104-transaction-processing-is-not-available-on-current-connection}

## 7105 Full Text Search Index Requires Newer Client {#7105-full-text-search-index-requires-newer-client}

***Problem:*** The index file contains a full text search (FTS) index, and an Advantage client prior to version 7.0 attempted to open it. Full text search indexes require Advantage clients 7.0 or greater.

***Solution:*** Update the client to 7.0 or greater.

## 7106 The table is read only and cannot be encrypted {#7106-the-table-is-read-only-and-cannot-be-encrypted}

***Problem:*** The table cannot be encrypted because is it read only.

***Solution 1:*** Make sure the table was not opened with the read-only option.

***Solution 2:*** Make sure the OS file access restrictions allow read/write access to the table.

## 7107 The client's memo data is out of sync with the server {#7107-the-client-s-memo-data-is-out-of-sync-with-the-server}

***Problem:*** Advantage server detected a mismatch between the client's expected memo or blob data length and the amount of actual available data. This error is possible with the Advantage thin clients, such as JDBC driver, when live/updateable result set (cursor) is used.

***Solution:*** Refresh the client's record data after receiving this error to make it in sync with the server. To avoid this error, use static cursor.

## 7108 Unrecognized ADI version {#7108-unrecognized-adi-version}

***Problem:*** The version number of the ADI (Advantage proprietary index file) is not recognized by this version of the software. The index file was most likely created by a newer version of Advantage.

***Solution:*** Rebuild the index file using your existing version of Advantage, or upgrade the Advantage software to the latest release if the new features are required.

## 7109 Database logins are disabled {#7109-database-logins-are-disabled}

***Problem:*** The database administrator currently has logins on this database disabled.

***Solution:*** Login at a different time or contact your administrator.

## 7110 Large key size requires newer client {#7110-large-key-size-requires-newer-client}

***Problem:*** The index file contains an index order with a key size larger than what is supported by the client. The larger key size requires Advantage clients 7.1 or greater.

***Solution:*** Update the client to 7.1 or greater.

## 7111 The temporary table is in use {#7111-the-temporary-table-is-in-use}

***Problem:*** The temporary table is already in use. There are two possible causes for this error:

| *a.* | An attempt was made to open a temporary table as a regular table using the table path directly when the temporary table is already in use. *Or* |
| --- | --- |

| *b.* | An attempt was made to open a temporary table when the table has already been opened as a regular table using the table path directly. |
| --- | --- |

***Solution:*** Avoid opening temporary tables as regular tables.

## 7112 The temporary table cannot be found {#7112-the-temporary-table-cannot-be-found}

***Problem:*** The Advantage Database Server cannot find the temporary table.

***Solution:*** Make sure the temporary table has been created on the current connection and the temporary table has not been deleted.

## 7113 Database logins for this user have been disabled {#7113-database-logins-for-this-user-have-been-disabled}

***Problem:*** The database administrator currently has logins disabled for this user.

***Solution:*** Login at a different time or contact your database administrator.

## 7114 Unable to split index page {#7114-unable-to-split-index-page}

***Problem:*** The current update operation required an index page split, but it was not possible to split the page.

***Solution:*** This problem can occur if the key size is close (within a few bytes) of the maximum possible key size for the index page size and the key data cannot be compressed. If this error occurs with the ADT table type, rebuild the index with a larger page size.

## 7115 Unable to obtain OS file lock {#7115-unable-to-lock-file}

***Problem:*** Advantage server failed to obtain a lock on a file from OS. This error is returned by Advantage Local Server or Advantage Database Server with compatibility lock mode. In such environment, a lock requirement on an index file or a memo file can only be fully satisfied by obtaining a lock on the file from the OS. If the OS lock request fails for any reason, Advantage will retry the lock request for about 2 minutes. If the lock cannot be obtained after 2 minutes, the 7115 error is returned. A known case for this error is when the file is hosted on a Linux server and the Advantage process does not have sufficient permission to obtain the lock.

***Solution:*** The problem can be avoided by using Advantage database server with proprietary locking when possible. If using compatibility locking or local server on Linux, make sure that the user (Advantage user on remote server) has read and write permission to the files.

## 7116 Unrecognized ADT table version {#7116-unrecognized-adt-table-version}

***Problem***: The version number of the ADT (Advantage proprietary table) is not recognized by this version of the software. The table was either created by a newer version of Advantage, or it has been corrupted.

***Solution***: If the table was created with a newer version of Advantage, it will be necessary to use that version of Advantage to access the table. If the table was not created by a newer version of Advantage, run the ADT table repair utility (ADTFIX.EXE) against the offending ADT table. This utility is available for download from the Advantage Developer Zone Web site in the "Tools & Utilities" section, **http://DevZone.AdvantageDatabase.com**.

## 7117 Unrecognized ADM version {#7117-unrecognized-adm-version}

***Problem***: The version number of the ADM (Advantage proprietary memo file) is not recognized by this version of the software. The table and associated memo file were likely created by a newer version of Advantage.

***Solution***: This is primarily a warning code that is written to the error log. The memo file is structurally compatible with the current version of Advantage, but it will not be able to benefit from the new features. If the new features are necessary, use a newer version of the Advantage software.

## 7118 RI Cascade Operation Failed {#7118-ri-cascade-operation-failed}

***Problem:*** A referential integrity rule could not cascade a change to the child table. This can happen if the record in the child table is currently part of a transaction owned by another user.

***Solution:*** Attempt the record update at another time.

## 7119 Encryption Not Available {#7119-encryption-not-available}

***Problem***: The table opened requires encryption, but the encryption key has not been setup.

***Solution***: If the table is bound to a data dictionary, make sure that the table is being opened on a data dictionary connection.

## 7120 Index Requires Dictionary Connection {#7120-index-requires-dictionary-connection}

***Problem***: The index file is encrypted and it can only be opened on a data dictionary connection.

***Solution***: Open the table and index on a data dictionary connection.

## 7121 The client failed to respond while transferring data via inter-process communications {#7121-the-client-failed-to-respond-while-transferring-data-via-inter-process-communications}

While communicating with Advantage Database Server, a client running on the same workstation failed to respond while transferring request or response data. This error is logged for informational purposes and is not returned to the client. If a client application is terminated abnormally, it can result in this error.

## 7122 Local server failed to rebuild index {#7122-local-server-failed-to-rebuild-index}

***Problem***: Advantage Local server attempted to rebuild a corrupt index but the parent table was not opened exclusively. If the Advantage Database Server shutdown abnormally, it is possible that some updates to index files were not saved to disk. The next time such an index is opened, Advantage will attempt to rebuild the index automatically. To do this the table (and index) must be opened exclusively or by Advantage Remote Server.

***Solution***: Open the parent table and the index exclusively or using remote server. In the future, avoid shutting down the Advantage Database Server when index files are still open or disable the caching of index updates by setting the MAX_CACHE_MEMORY configuration value to zero.

## 7123 Unreconginzed Field Type {#7123-unreconginzed-field-type}

***Problem:*** An unrecognized field type was found in the table. The table was either created by a newer version of Advantage, or it has been corrupted.

***Solution:*** Verify the version of Advantage Database Server supports the field type. If not, upgrade the server to a newer version that does. If it already does support the field type, then the table is most likely physically corrupt. If the table is an ADT (Advantage Proprietary Table), run the ADT table repair utility (ADTFIX.EXE) against the offending ADT table. This utility is available for download from the Advantage Developer Zone Web site in the "Tools & Utilities" section, **http://DevZone.AdvantageDatabase.com**.

## 7124 Incorrect Record Count {#7124-incorrect-record-count}

***Problem:*** The table contains an incorrect record count in its header. The physical length of the table does not equal the table header length plus the field header length times the number of fields plus the record count times the record length.

***Solution 1:*** If the physical table ends at the logical end of a record, the record count in the header will be automatically updated by Advantage. However, any indexes built on the table will likely be logically or physically corrupt. All indexes on the table should then be rebuilt.

***Solution 2:*** If the physical table does not end at the logical end of a record, the table is physically corrupt. If the table is an ADT (Advantage Proprietary Table), run the ADT table repair utility (ADTFIX.EXE) against the offending ADT table. This utility is available for download from the Advantage Developer Zone Web site in the "Tools & Utilities" section, **http://DevZone.AdvantageDatabase.com**. Once the table has been fixed, all indexes on the table should then be rebuilt.

## 7126 Backup in-memory table read failed {#7126-backup-in-memory-table-read-failed}

***Problem***: An error occurred reading data from an internal table during a backup operation. Check the error log entries directly above the 7126 error in the ads_err log file for additional error codes.

***Solution***: This error should not occur. Contact your support representative and provide your ads_err.dbf and ads_err.adt log files.

## 7127 Backup in-memory table write failed {#7127-backup-in-memory-table-write-failed}

***Problem***: An error occurred writing data to an internal table during a backup operation. Check the error log entries directly above the 7127 error in the ads_err log file for additional error codes.

***Solution***: This error should not occur. Contact your support representative and provide your ads_err.dbf and ads_err.adt log files.

## 7128 Backup index file copy failed {#7128-backup-index-file-copy-failed}

***Problem***: An error occurred copying a structural index file during a backup or restore operation.

***Solution***: Check the error log entries directly above the 7128 error in the ads_err log for additional error codes and solutions.

## 7129 Savepoint Not Found {#7129-savepoint-not-found}

***Problem***: A valid savepoint name must be given to perform a partial transaction rollback.

***Solution***: Make sure that the savepoint name is correct

## 7130 Illegal Operation Inside of Trigger {#7130-illegal-operation-inside-of-trigger}

***Problem***: An illegal operation was performed inside of a trigger.

***Solution***: Do not perform transaction operations inside of triggers.

## 7131 Table is involved in another active backup command {#7131-table-is-involved-in-another-active-backup-command}

The table listed with this error code in the ads_err log file is currently being backed up or restored by another Advantage process, and can not be opened until the other process is finished.

## 7132 Subscription Information is Inconsistent {#7132-subscription-information-is-inconsistent}

***Problem***: An inconsistency was detected in the data in the replication queue.

***Solution***: This is generally an unexpected error. It can occur if you edit the replication queue manually while replication updates are being processed. Do not modify data in the replication queue. If this did not happen, please send a small re-creation to Advantage Technical Support.

## 7133 Triggers are not allowed on live views {#7133-triggers-are-not-allowed-on-live-views}

***Problem***:** A trigger was created on a live view. Triggers are only allowed on static views.

***Solution***:** Create the trigger on the view's table or re-write the view such that it produces a static cursor.

## 7134 Non-standard character used in table name or column name for replication {#7134-non-standard-character-used-in-table-name-or-column-name-for-replication}

***Problem***: Replication cannot be performed because the name of the table to be replicated or the name of one of the columns in the table to be replicated contains both the double quote (") character and closing bracket (]) character.

***Solution***: Avoid using non-standard characters in table names and column names. Restructure the table to remove non-standard characters in column names.

## 7135 No trigger defined for update type {#7135-no-trigger-defined-for-update-type}

***Problem***:** Triggers exist for the view, but not for the update type (INSERT, UPDATE, DELETE).

***Solution***:** In order to update a static view, at least one trigger must exist for that update type. Create a trigger for that update type or do not perform that update to the static view.

## 7136 Serial number and replication code mismatch {#7136-serial-number-and-replication-code-mismatch}

***Problem***: The serial number does not match the replication code that is stamped in the Advantage Database Server.

***Solution***: Verify that the replication code entered during installation is correct.

## 7137 Unexpected number of records modified during a replication update {#7137-unexpected-number-of-records-modified-during-a-replication-update}

***Problem***: A replication update resulted in an unexpected number of records updated at the target table. With each update at the source table, there should be one corresponding update at the target.

***Solution 1:*** Verify the identification columns for the table (in the publication definition) uniquely identify the record. If the specified identification columns do not uniquely identify the target record, multiple record updates could occur.

***Solution 2***: Verify the record to update at the target does exist. The More_Info field in the ads_err.adt error log should have information that helps identify the record in question. You may want to check the "Log Data for Failed Replication Updates" in the Advanced tab of the subscription properties dialog in Advantage Data Architect. If this option is chosen, the non-memo data fields of the record will be stored in the error log with the SQL statement that failed.

***Solution 3***: If the record does not exist at the target and, therefore, cannot be updated successfully, then you can choose the "Ignore Replication Failures" option in the Advanced tab of the subscription properties dialog in Advantage Data Architect. This will cause Advantage to log the 7137 error for the failed update but continue processing the replication queue. Alternatively, you can delete the failed entry from the replication queue. If you are deleting the entry and the failed entry is part of a transaction (TxnID is non-NULL in the replication queue), then you should delete all entries in the transaction.

## 7138 Record Not Locked {#7138-record-not-locked}

***Problem***: The client sent an unlock request for a record that the server no longer had locked.

***Solution***: In most situations this is an acceptable error, and is only noted as a warning. If, however, this error is encountered along with other unexpected behavior, contact your Advantage technical support provider.

Acceptable Situations:

| 1. | A failed referential integrity update that was deleting records. |
| --- | --- |

| 2. | An AFTER DELETE or INSTEAD OF DELETE trigger returns an error. |
| --- | --- |

## 7139 Invalid Packet Data Size {#7139-invalid-packet-data-size}

***Problem***: The server received a data packet that was not the expected size.

***Solution***: This is normally just an informational error. The error is common on servers that are exposed to the internet, where applications often scan open ports and attempt to send data to them.

## 7140 Connection is already a debugger or debuggee {#7140-connection-is-already-a-debugger-or-debuggee}

**Problem:** When using SQL DEBUG command, a connection cannot be made a debugger or debuggee because it is already a debugger or debuggee.

**Solution:** Ensure that the connection is not a debugger or debuggee.

## 7141 The name is not a valid temporary table name {#7141-the-name-is-not-a-valid-temporary-table-name}

**Problem:** The name given when trying to create a temporary table is not valid.

**Solution:** Make sure that there are no colon or semi-colons in the name.

## 7142 The maximum number of debuggees was exceeded {#7142-the-maximum-number-of-debuggees-was-exceeded}

**Problem:** When using the SQL DEBUG command, a connection cannot be made a debuggee because the server has reached the limit of number of concurrent debuggee connections.

**Solution:** When debugging an SQL script on the Advantage Database server, the maximum number of concurrent debuggees is the number of configured worker threads minus one. Increase the number of configured worker threads and restart the server to debug additional connections.

## 7143 Cannot make a connection a debuggee {#7143-cannot-make-a-connection-a-debuggee}

**Problem:** When using the SQL DEBUG command, a connection cannot be made a debuggee connection because it is processing a client request.

**Solution:** A connection can only be made a debuggee when it is in an idle state. Wait till the client is idle to retry the command or repeat the command until successful.

## 7144 Collation Repository Not Found {#7144-collation-repository-not-found}

***Problem***: Advantage was not able to find the collation repository that stores the dynamic collations.

***Solution***: The collation repository is an ADT table named adscollate.adt with an associated memo file named adscollate.adm. It should reside in the same directory as the Advantage Database Server binary image (e.g., ads.exe, libadsd.so, etc.). When using Advantage Local Server, adscollate.adt must be found in the path (normally it would be in the same directory as the adslocal.cfg file).

## 7145 Collation Load Failed {#7145-collation-load-failed}

***Problem***: Advantage was not able to open and use the collation repository that stores the dynamic collations.

***Solution***: An error occurred when trying to read the collation repository, which is an ADT table named adscollate.adt with an associated memo file named adscollate.adm. Check the error log (ads_err.adt or ads_err.dbf) for details.

## 7146 Collation Name Not Unique {#7146-collation-name-not-unique}

***Problem***: When loading a dynamic collation, multiple entries in the repository were found that match the name.

***Solution***: The error log (ads_err.adt or ads_err.dbf) entry for this error will show the name that was found to be non-unique. It may be necessary to replace the adscollate.adt and adscollate.adm files with valid copies.

## 7147 Collation Name Not Found {#7147-collation-name-not-found}

***Problem***: An attempt to load a dynamic collation failed because the given collation name was not found.

***Solution***: Verify that the correct collation name was specified in the application. The error log (ads_err.adt or ads_err.dbf) entry for this error will show the name that was being searched for.

## 7148 Collation Not Recognized {#7148-collation-not-recognized}

***Problem***: An attempt to load a dynamic collation failed because the version of the collation was not recognized.

***Solution***: Verify that the correct collation was specified. If the version is newer than what Advantage recognizes and the collation repository is valid, then it is necessary to use a newer version of Advantage.

## 7149 Invalid Packet {#7149-invalid-packet}

The communication layer received an unknown packet type from the Advantage client driver.

Check the Advantage error log to see if the invalid packets are all coming from the same client. If so, check the network card and network stack on that client.

For other situations, please send all ads_err error log files to Advantage Technical Support.

## 7150 Collation Is Corrupt {#7150-collation-is-corrupt}

***Problem***: An attempt to load a dynamic collation failed because the information in the collation repository did not contain the expected data.

***Solution***: When Advantage loads a dynamic collation from the repository (adscollate.adt and adscollate.adm), it verifies that the information is consistent. If it finds a problem with the collation information, it will log this error. To resolve this error, you will need to replace adscollate.adt and adscollate.adm with valid copies of the files.

## 7151 Invalid Table Type {#7151-invalid-table-type}

***Problem***: A Visual FoxPro DBF table was opened with either the ADS_CDX or ADS_NTX table type. This error occurs if the table contains field types (e.g., currency, datetime, etc.) that are not supported by the ADS_NTX and ADS_CDX table types.

***Solution***: Use the ADS_VFP table type when opening Visual FoxPro tables.

## 7153 Key Cannot Be Null {#7153-key-cannot-be-null}

***Problem***: A field value was modified such that it resulted in a NULL key value, but the index does not allow NULL values. This can happen with candidate indexes created on Visual FoxPro tables.

***Solution***: Change the data so that it does not result in a NULL key value or cancel the update.

## 7154 Index Automatically Rebuilt {#7154-index-automatically-rebuilt}

A 7154 error indicates an index file was not closed properly the last time it was opened. The server detected this state and automatically re-indexed the file.

This can happen if you use a file system command to copy an index file while Advantage has the file open. Advantage may have portions of the file cached, and if this cache has not been flushed to disk you can not make copies of the file until Advantage closes it. Any copies you make will need to be re-indexed before they are opened again by Advantage. If this situation arises, Advantage will detect it and automatically re-index and log the 7154 error.

## error 7156 Auto Re-Indexing is Active {#7156-auto-re-indexing-is-active}

***Problem***: The server cannot open the index file because it is being rebuilt.

***Solution:*** This error should not be returned by the Advantage Database Server. Please contact Advantage Technical Services if you encounter this error.

## 7157 Maximum number of active Unicode collators for a connection have been exceeded. {#7157-maximum-number-of-active}

Each connection in Advantage server is allowed to use 128 distinct Unicode collation locales. For example, if two index files with ‘en_US’ collation locale and three index files with ‘de_DE’ collation locale are opened on a connection, then the connection is using two distinct Unicode collation locale. The opened Unicode collators are cached on the connection until the connection is closed. If the connection already has 128 Unicode collators active, then it will not be able to use index files built with Unicode locale that is not the same as one of the already opened collators.

## error 7158 The server cannot determine the default ANSI/OEM Unicode collation locale {#7158-the-server-cannot-d}

The likely cause for this error is that an older version (pre 10.0 release) of the adscollate.adt is loaded by the servers. When Advantage database server is loaded, it will try to determine the Unicode collation locales correspond to the server’s default ANSI/OEM character sets. This is done using look up in the adscollate.adt. If the look up failed to find the corresponding Unicode collation locales, this error will be returned when the server try to sort or compare Unicode characters for tables opened with the default ANSI/OEM collation.

## error 7159 Cannot determine the code page for the default ANSI/OEM character set {#7159-cannot-determine-th}

The likely cause for this error is that an older version (pre 10.0 release) of the adscollate.adt is loaded by the server. When Advantage database server is loaded, it will try to determine the code pages of the server’s default ANSI/OEM character sets. This is done using look up in the adscollate.adt. If the look up failed to find the corresponding code pages for the character sets, this error will be returned when a conversion between Unicode and code page characters is needed on a table opened with the default ANSI/OEM character type.

## 7160 Unable to Load SSL {#7160-unable-to-load-ssl}

***Problem:*** Advantage Database Server was not able to load the OpenSSL libraries. In order to use AES encryption or TLS communications, you must have the FIPS Encryption Security Option available.

***Solution:*** If the libraries are available, verify that they are in a path location that the server can access.

## 7161 Unable to Verify Signature {#7161-unable-to-verify-si}

***Problem:*** Advantage Database Server was not able to verify the digital signature on one of the OpenSSL libraries.

***Solution:*** Verify that the libraries the Advantage Database Server has access to are the same ones from the FIPS Encryption Security Option.

## 7162 Unable to Load SSL Entrypoint {#7162-unable-to-load-ssl}

***Problem:*** Advantage Database Server was not able to load one of the entrypoints from the OpenSSL libraries. This may mean that the wrong version of the library was loaded.

***Solution:*** In order to use AES encryption or TLS communications, you must have the FIPS Encryption Security Option available. If the libraries are available, verify that they are in a path location that the server can access.

## 7163 SSL Library Error {#7163-ssl-library-error}

***Problem:*** A general unknown error occurred in the OpenSSL library.

***Solution:*** The error log may contain more detailed information with additional error numbers. Refer to the [OpenSSL error information](openssl-errors.md).

***Problem:*** The server failed to load the TLS certificate (TLS_KEY_FILE) and logged 7163 errors on startup.

***Solution:*** Verify that the path and name for the certificate file is correct. The full path must be included. If Advantage is running as a service in Windows, for example, the default directory may not be the folder containing the certificate.

## 7164 Unrecognized Cipher {#7164-unrecognized-cipher}

***Problem:*** One of the given TLS ciphers is not supported. The supported values are AES128-SHA, AES256-SHA, and RC4-MD5.

***Solution:*** Verify that the TLS_CIPHERS configuration parameter is correct.

## 7165 FIPS Mode Failed {#7165-fips-mode-failed}

***Problem:*** Advantage Database Server was not able to enable FIPS mode when starting up.

***Solution:*** If FIPS mode is not desired, verify that the FIPS configuration parameter is not specified with a value of 1. If FIPS mode is desired, check the error log for more detailed information on the exact nature of the error.

The OpenSSL libraries are required in order to use FIPS mode. If there was an error loading the libraries, the error log should have a [7160](#7160-unable-to-load-ssl), [7161](#7161-unable-to-verify-si), [7162](#7162-unable-to-load-ssl) error that may indicate why they could not be loaded.

It is also possible for the internal FIPS mode verification performed at startup to fail. If this happened, the error log should contain additional information.

## 7166 FIPS Not Allowed {#7166-fips-not-allowed}

***Problem:*** An attempt by a client in FIPS mode was made to connect to Advantage Database Server that was not in FIPS mode.

***Solution:*** The client FIPS setting must match that of the server.

## 7167 FIPS Required {#7167-fips-required}

***Problem:*** An attempt by a client not in FIPS mode was made to connect to Advantage Database Server that was in FIPS mode.

***Solution:*** The client FIPS setting must match that of the server.

## 7168 Table does not Support Strong Encryption {#7168-table-does-not-supp}

***Problem:*** An attempt was made to enable encryption on a table using AES encryption, but the table format does not support it.

***Solution:*** Only ADT and VFP table types support AES encryption; verify that the table type is correct. In addition, the table may need to be updated with additional information to support the encryption type. The system procedure sp_EncryptTable can be used to convert the table format.

## 7169 FIPS Mode Violation {#7169-fips-mode-violation}

***Problem:*** The current request could not be completed because Advantage is running in FIPS mode and the request required use of cryptography that is not approved for FIPS usage.

***Solution:*** If you are trying to open a dictionary or a table that is not using AES encryption while the server is in FIPS mode, the operation cannot be completed. The system procedure sp_SetDDEncryptionType can be used to change a dictionary to use AES encryption. Tables can be converted to AES encryption with the system procedure sp_EncryptTable. In order to perform the conversion, it is necessary to use clients and servers that are not running in FIPS mode.

## error_7171_ANSI_UNICODE_INCONSISTENT {#7171-ansi-unicode-incons}

***Problem:*** When using wild card in FTS filter expression, i.e. searching in multiple fields, the words to be searched must be the same for all ANSI and Unicode fields. 7171 error is returned when the number of words when parsed using Unicode collation is different from the number of words when parsed in ANSI collation. For example, the expression "Contains( *, 'КНДР')" where КНДР is encoded in Unicode and is parsed as one word in Unicode. However, in ANSI collation, the same string literal may not be able to translate directly and cannot be parsed into an valid word. If the table contains both ANSI and Unicode fields, the 7171 error will returned.

***Solution:*** Avoid searching both ANSI and Unicode fields for Unicode words that cannot be translated into ANSI encoding.

## 7172 Invalid TLS Certificate {#7172-invalid-tls-certifi}

***Problem:*** The request could not be completed because the server does not have a valid Transport Layer Security (TLS) certificate.

***Solution:*** Verify that the TLS_KEY_FILE configuration parameter refers to a valid certificate.

## 7173 Too Many Fields {#7173-too-many-fields}

***Problem:*** The requested operation could not be completed because the table has too many Memo and/or BLOB fields.

***Solution:*** The maximum number of memo fields that can be supported in certain operations is 500. It may be necessary to restructure the table to have fewer memo/BLOB fields in order to use the functionality.

## 7175 Online Pack Already Active {#7175-online-pack-already}

***Problem:*** An online pack operation was already active on a table when another online pack operation was requested on the same table.

***Solution1:*** Allow the previous online pack operation to finish before attempting to pack the same table again.

***Solution2:*** Cancel the active online pack operation before attempting to pack the same table again. Consider specifying a timeout value in the sp_PackTableOnline call if the operation is taking too long.

## 7176 Online Pack Timeout {#7176-online-pack-timeout}

***Problem:*** An online pack operation failed to complete before the timeout expired.

***Solution:*** Increase the timeout value or address the roadblocks preventing the pack from completing (close or reposition any open handles to the table, process pending replication updates for the table, etc).

## 7177 Online Pack Extra Indexes {#7177-online-pack-extra-i}

***Problem:*** Extra indexes belonging to the pack table were found open but not specified in the sp_PackTableOnline call.

***Solution:*** Include all indexes that belong to the table in the sp_PackTableOnline call.

## 7178 Online Reindex Already Active {#7178-online-reindex-alre}

***Problem:*** An online reindex operation was already active on a table when another online reindex operation was requested on the same table.

***Solution1:*** Allow the previous online reindex operation to finish before attempting to reindex the same table again.

***Solution2:*** Cancel the active online reindex operation before attempting to reindex the same table again. Consider specifying a timeout value in the sp_ReindexOnline call if the operation is taking too long.

## 7179 Permission Denied {#7179-permission-denied}

***Problem:*** A call to AdsMgKillUser or sp_mgKillUser failed with this error

***Solution:*** As of v11, membership in the DB:Admin group is required to use this functionality.

## 7180 Maximum Number of Advantage Web Platform Users Exceeded {#7180-stateless-connectio}

***Problem:*** The maximum configured number of Advantage Web Platform (stateless) users has been exceeded.

***Solution:*** Each concurrently active Advantage Web Platform user counts as an Advantage user. The WEB_PLATFORM_USERS configuration parameter can be used to specify the maximum number of web platform users.

## 7181 Maximum Number of Connected (Stateful) Users Exceeded {#7181-stateful-connection}

***Problem:*** The maximum configured number of connected (stateful) users has been exceeded.

***Solution:*** The Advantage user count can be allocated between stateful connections (e.g., those consumed by a Delphi application) and stateless connections (e.g., those used by the Advantage Web Platform) . The WEB_PLATFORM_USERS configuration parameter can be used to specify the maximum number of web platform users. Reducing that value will allow for more concurrent stateful connections.

## 7182 Online Operation Index Collation Mismatch {#7182-online-operation-in}

***Problem:*** The index collation specified on the connection is different than the collation that was used when an index was opened.

***Solution:*** Set the correct collation on the connection before attempting an online operation (pack, reindex, alter). Conversely, make sure any other users of the table or index is using the same collation that the online operation uses.

## 7183 Online Alter Already Active {#7183-online-alter-alread}

***Problem:*** An online alter operation was already active on a table when another online alter operation was requested on the same table.

***Solution1:*** Allow the previous online alter operation to finish before attempting to alter the same table again.

***Solution2:*** Cancel the active online alter operation before attempting to alter the same table again.

## 7184 Online Alter Replication Failure {#7184-online-alter-replic}

***Problem:*** An online alter operation cannot complete because there are replication update pending for the table being altered and replication is not enabled.

***Solution:*** Process or remove the pending replication updates before starting the online alter operation.

## 7185 Online Alter Extra Indexes {#7185-online-alter-extra}

***Problem:*** Extra indexes belonging to the alter table were found open but not specified in the ALTER call.

***Solution1:*** Add the extra non-auto open indexes to a data dictionary to ensure they get opened during the ALTER call.

***Solution2:*** Close all other instances of the table being altered so no extra indexes are found. Only do this if you are certain the changes during the alter do not require rebuilding the extra indexes.

## 7200 Advantage SQL Error {#7200-advantage-sql-error}

***Problem:*** The problem might be caused by an SQL statement error or some other limitation in the way Advantage processes SQL statements.

***Solution:*** Use AdsGetLastError to retrieve a detailed description of the error. The error description contains a "NativeError" code that you can look up. An example error string might be as follows:

Error 7200: AQE Error: State = HY000; NativeError = 5012; [Extended Systems][Advantage SQL][ASA] Error 5012.

In this case, you would look up error [5012](5xxx-errors.md#5012-ae-invalid-fielddef) to get more detailed information. The native error codes can, in general, be Advantage Client Engine errors (5000+), Advantage Database Server errors (7000+), or an SQL-specific error. Note that the SQL-specific error code values may change in a future release.

If you get a native error code that is not documented, contact Technical Support.

## 7201 The parameter number given exceeds the number of parameters in the SQL statement {#7201-the-parameter-number-given-exceeds-the-number-of-parameters-in-the-sql-statement}

***Problem***: Advantage Database Server received an SQL statement parameter with a number larger than the number of parameters in the statement.

***Solution***: Verify that the correct number of parameters is specified for the SQL statement.

## 7202 Data that resulted from the SQL statement is too long to be returned in a cursor {#7202-data-that-resulted-from-the-sql-statement-is-too-long-to-be-returned-in-a-cursor}

***Problem***: The SQL statement produces a result that exceeds the limit of the Advantage Database Server.

***Solution***: Consult your *Advantage Database Server Guide* for information about the existing limitations on Advantage supported tables.

## 7203 Data that resulted from the SQL statement has an unknown length {#7203-data-that-resulted-from-the-sql-statement-has-an-unknown-length}

***Problem***: The SQL statement produces result with an unknown length.

***Solution***: Verify that the SQL statement is correct.

## 7204 Too many columns exist in the SQL SELECT statement {#7204-too-many-columns-exist-in-the-sql-select-statement}

***Problem***: The number of columns in the cursor produced by the SQL statement exceeds the limitation of the Advantage Database Server.

***Solution***: Verify that the SQL statement is correct. The number of columns supported by Advantage Database Server is the same as the number of fields supported in a table.

## 7205 Cannot establish a connection to the Advantage SQL engine {#7205-cannot-establish-a-connection-to-the-advantage-sql-engine}

***Problem***: The Advantage Database Server failed to establish the requested connection to the Advantage SQL engine.

***Solution***: Verify that the connection path is correct.

## 7206 Cannot convert data from SQL format to Advantage format {#7206-cannot-convert-data-from-sql-format-to-advantage-format}

***Problem***: The Advantage Database Server failed to convert data from SQL format to Advantage format.

***Solution***: Verify that the SQL statement is correct. Consult the Advantage SQL documentation for the supported SQL data format.

## 7207 Unexpected error from the Advantage Server Agent {#7207-unexpected-error-from-the-advantage-server-agent}

***Problem***: The Advantage Database Server has received an unexpected error from the Advantage Server Agent module.

***Solution***: Check the Advantage Database Server error log, ADS_ERR.ADT or ADS_ERR.DBF, for details.

## 7208 One or more columns in the SQL SELECT statement contain a data type not supported by Advantage {#7208-one-or-more-columns-in-the-sql-select-statement-contain-a-data-type-not-supported-by-advantage}

***Problem***: The cursor produced by the SQL statement contains column types that are not supported by the Advantage Database Server.

***Solution***: Verify that the SQL statement is correct. Consult the Advantage SQL documentation for the supported SQL data format.

## 7209 SQL query aborted by user {#7209-sql-query-aborted-by-user}

***Problem***: The SQL query was aborted by the user.

***Solution***:** If using ADO and executing a query that can take quite a while to complete, set the Command.CommandTimeout property to a value greater than its default of 30 seconds. If using ADO.Net and executing a query that can take quite a while to complete, set the OleDbCommand.CommandTimeout property to a value greater than its default of 30 seconds.

## 7211 Advantage cannot sort the SQL result set based on the ORDER BY clause because of internal limitation {#7211-advantage-cannot-sort-the-sql-result-set-based-on-the-order-by-clause-because-of-internal-limitation}

***Problem:*** Advantage cannot sort the SQL result set based on the ORDER BY clause because of an internal limitation.

***Solution***: None.

## 7213 Server detected possible client communication failure {#7213-server-detected-pos}

***Problem:*** The server detected that the client may have had a communication failure and failed to send a server request.

***Solution:*** The server was able to continue processing the new request without problem; the error is logged for informational purposes.

## 7215 ROWID Invalidated During Pack {#7215-rowid-invalidated-d}

***Problem:*** A query used a ROWID value for a table that has been packed online.

***Solution:*** ROWID values for packed tables may be invalid and shouldn't be used. ROWID values should be recalculated after a table has been packed online.

## 7600 Advantage Replication Error {#7600-advantage-replication-error}

7600 is the error class for replication errors. In general, the 7600 error class is equivalent to the 7000 error class; it simply has a unique value to signify that the error occurred in response to a replication operation. It provides the ability to filter on the error class in order to easily identify replication errors in the error log. Look up the specific error code for details. In addition, if the error is logged to the ads_err.adt log file, the More_Info field may have additional information.

*[PO]: Purchase Order  
*[AZA]: local folder
*[(PO]: Purchase Order  
*[RQ]: Requisition  
*[(RQ]: Requisition  
*[RfQ]: Request for Quotation  
*[(RfQ]: Request for Quotation  
*[SO]: Service Order  
*[(SO]: Service Order  
*[SQ]: Service Requisition  
*[(SQ]: Service Requisition  
*[SRfQ]: Service Request for Quotation  
*[OoB]: Open on Board  
*[(OoB]: Open on Board 
*[ART]: Average Running Time (operation hours per day) 
*[MC]: Master Contract
*[ADS]: Advantage Database Server (database engine used in previous versions of the ZeeBORN software)
*[.replic]: file extension for replication files (aka data transfer files)