Advantage 7xxx Error Codes

7000    General Advantage server Error Code. Refer to the associated OS Error

        Code for more information.

7001    No memory available

        Problem:  There is not enough available free RAM on the network server.

        Solution:  Adjust your Advantage configuration file (AXS.CFG) options

        so that less memory is required or add RAM to the server.

7002    Configuration error

        Problem:  Invalid command line parameter.

        Solution:  Consult your Advantage server guide for configuration

        parameters, then restart/reload the Advantage server with valid command

        line parameters.

7003    User table full

        Problem:  The maximum number of users are already connected to the

        Advantage server.

        Solution:  Wait until a current user logs out or upgrades to a version

        of the Advantage Database Server that allows more users.

7004    Workarea table full

        Problem:  The maximum number of configured workareas are already in

        use.

        Solution:  Restart/reload the Advantage server with a larger value for

        number of workareas.

7005    .dbf table full

Problem:  The maximum number of configured .dbf files are already in use.

Solution:  Restart/reload the Advantage server with a larger value for number

of .dbf files.

7006    Index table full

Problem:  The maximum number of configured index files are already in use.

Solution:  Restart/reload the Advantage server with a larger value for number

of index files.

7007    Lock table full

Problem:  The maximum number of configured locks are already in use.

Solution:  Restart/reload the Advantage server with a larger value for number

of locks.

7008        Advantage server file open failure

Problem:  The specified database file, memo file or index file was unable to be

opened.

Solution:  Make sure the file exists and that the user has sufficient access

rights to open the file.

7009    Problem with Advantage server file write

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

Solution:  Check the network volume for available disk space.

7010    Problem with Advantage server file read

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

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

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

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

Problem: The user does not have sufficient access rights to open the specified

file.

Solution:  Make sure the user has sufficient access rights to open the file.

7014    Invalid database file

Problem:  The first byte in the specified .dbf file does not indicate a valid

.dbf file.

Solution:  Make sure the file is a valid .dbf file.

7015    Corrupt .ntx

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

Solution:  Rebuild the index.

7016    Corrupt .dbf

Problem:  The specified .dbf file contains corrupted data in the file or field

headers.

Solution:  Make sure the specified file is a valid .dbf file.

7017    Corrupt .idx

Problem:  The current .cdx or .idx index file contains corrupt or invalid data.

Solution:  Rebuild the index.

7018    Empty page

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

Solution:  Rebuild the index.

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.

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

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. This error is not logged in the error log but is visible by the

Advantage Management Utility.

Solution:  The user must re-connect.

7021    Maximum tags exceeded

Problem:  Attempted to open a .cdx file which contains more than 50 tags.

Solution:  Use a .cdx file with 50 tags or less.

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.

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.

7023    Incompatible Index File Type

Problem:  Attempted to open an index file type that is not supported by the

Advantage Database Server. The index must be an .ntx, .idx or .cdx file type.

Solution:  Reindex the file using the Advantage Database Server.

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 path too long

Problem:  The path to the file being opened was too long to create a semaphore

file.

Solution:  Shorten the path.

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

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

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

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 equation for calculating the minimum Index Sort Buffer Size is

located in the Index Sort Buffer Size description in the Advantage

Configuration chapter in the Advantage server guide.

7030    Missing Advantage configuration file, AXS.CFG, (applicable to Advantage

NLM only)

Problem:  This error is applicable to the Advantage NLM only. The Advantage

configuration file was not found when the Advantage NLM was loaded. The

configuration file must be located in the same directory as the Advantage NLM.

Solution:  Put AXS.CFG in the same directory as AXS.NLM. If AXS.CFG cannot be

found, re-install it from the Advantage installation disk.

7031    Could not open Advantage configuration file, AXS.CFG, (for Advantage

NLM) or Could not open Advantage Configuration Registry Key, (for Advantage

Service)

Problem Advantage NLM: The Advantage configuration file could not be opened

when the Advantage NLM was loaded.

Problem Advantage Service: The Advantage Configuration Registry Key could not

be opened when the Advantage Service was started.

Solution Advantage NLM: Make sure nobody is viewing or editing the Advantage

configuration file when the Advantage NLM is being loaded.

Solution Advantage Service: 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.

7032    Error in Advantage configuration parameter/value/data

Problem Advantage NLM:  An invalid Advantage configuration parameter or

parameter value was detected in the Advantage configuration file (AXS.CFG) when

the Advantage NLM was loaded.

Problem Advantage Service:  An invalid Advantage configuration value or value

data was detected in the Advantage Configuration Registry Key when the

Advantage Service was started.

Solution Advantage NLM:  Correct the configuration file parameter or parameter

value in question and then load the Advantage NLM. The configuration file line

number containing the error is displayed on the file server system console

screen when the Advantage NLM was attempted to be loaded.

Solution Advantage Service:  To correct the configuration value data, use the

Advantage Configuration Utility. To correct or remove invalid configuration

values, use the Registry Editor. The Advantage Configuration Registry Key is

located in the Registry at:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Advantage\Configuration

7033    Connection Table Full

Problem:  The maximum number of connections are already connected to the

Advantage server.

Solution:  Restart/reload the Advantage server with a larger value for number

of connections or wait until a current connection logs out.

Also see (HW115)

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

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

Problem:  A failed transaction recovery was not successful.

Solution:  Make sure the .dbf 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 AXS_ERR.DBF file

for more specific errors related to this failure.

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

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 .dbf has records. This can occur if a PACK or

ZAP is performed on the .dbf when the index file(s) was closed.

Solution:  Reposition to a valid record number. Reindex the index(es) that

contain more keys than the .dbf has records.

7039    File already open

Problem:  The user attempted to open a database file or an index file for

EXCLUSIVE use when another user already had the file open in SHARED mode.

Solution:  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.

7040    Server file creation error

Problem:  An error occurred when attempting to create a database file or an

index file.

Solution:  Make sure 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 RIGHTS CHECKING is ON).

7041    Server file not found

Problem:  The database file 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

Problem:  The byte being used for the TPS semaphore byte (either the "deleted"

byte or the AXS_TPS field, if one exists) 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 TPS semaphore byte.

Solution:  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

exclusively via a non-Advantage RDD/RDE. Then loop through all records in the

dbf 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 dbf exclusively (doesn't

matter which RDD/RDE used). Then loop through all records in the dbf and clear

all contents in the AXS_TPS field by replacing the field with a single space

"".

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

Problem:  The serial number in the hardware key (International servers) or

stamped in the ADS.EXE/AXS.NLM (North American servers) does not match the

validation code that is stamped in the ADS.EXE/AXS.NLM.

Solution:  Verify the hardware key is attached correctly (International

servers) or reinstall the Advantage Database Server.

7046    Evaluation period expired

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

Solution:  Contact Extended Systems or your local Advantage distributor and

purchase a full copy of Advantage Database Server.

7047    Invalid bits set in the deleted byte

Problem:  The "deleted" byte, which is the first byte in a .dbf 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 .dbf

exclusively via a non-Advantage RDD/RDE. Then loop through all records in the

.dbf re-marking all records for deletion that are currently marked for deletion

and recalling all records that are not currently marked for deletion.

The information in this document is subject to change without notice. This

document refers to numerous products by their trade names. The Advantage

Database Server is a product of Extended Systems. Advantage Database Server is

a trademark of Extended Systems Incorporated. All other designations are

trademarks or registered trademarks of their respective companies.