# Advantage 66xx Error Codes

*Advantage Error Guide*

**Note** If you receive an error in the 66XX range, contact Advantage Technical Support for more information.

## Contents

- [6602 Client comm layer timed out waiting for receive packet from the Advantage Database Server](#6602-client-comm-layer-timed-out-waiting-for-receive-packet-from-the-advantage-database-server)
- [6604 Timeout waiting for intermediate burst acknowledgement](#6604-timeout-waiting-for-intermediate-burst-acknowledgement)
- [6605 Client comm layer received more data from the Advantage Database Server than it was expecting](#6605-client-comm-layer-received-more-data-from-the-advantage-database-server-than-it-was-expecting)
- [6606 Amount of client protocol command information to send was greater than the maximum allowed](#6606-amount-of-client-protocol-command-information-to-send-was-greater-than-the-maximum-allowed)
- [6607 Protocol command information received by the client was not of the expected size](#6607-protocol-command-information-received-by-the-client-was-not-of-the-expected-size)
- [6609 Client comm layer received data of an unknown origin](#6609-client-comm-layer-received-data-of-an-unknown-origin)
- [6610 The Advantage Database Server did not respond to a database request in a timely manner](#6610-the-advantage-database-server-did-not-respond-to-a-database-request-in-a-timely-manner)
- [6611 Client communications layer timed out when attempting to send a packet](#6611-client-communications-layer-timed-out-when-attempting-to-send-a-packet)
- [6612 Client comm layer received a packet that was out of sequence and was beyond the acceptable range of sequence numbers](#6612-client-comm-layer-received-a-packet-that-was-out-of-sequence-and-was-beyond-the-acceptable-range-of-sequence-numbers)
- [6613 An IPX event was canceled](#6613-an-ipx-event-was-canceled)
- [6614 IPX/SPX not initialized on client](#6614-ipx-spx-not-initialized-on-client)
- [6615 Client comm layer is out of DOS memory](#6615-client-comm-layer-is-out-of-dos-memory)
- [6616 Client comm layer found no free ECBs available](#6616-client-comm-layer-found-no-free-ecbs-available)
- [6617 Client comm layer Winlock failed](#6617-client-comm-layer-winlock-failed)
- [6618 Maximum tasks reached or IPX DLLs not found](#6618-maximum-tasks-reached-or-netware-dlls-not-found)
- [6619 Client comm layer was already busy with one database operation when a second database operation was requested](#6619-client-comm-layer-was-already-busy-with-one-database-operation-when-a-second-database-operation-was-requested)
- [6620 Client comm layer did not have the needed Advantage Database Server destination address](#6620-client-comm-layer-did-not-have-the-needed-advantage-database-server-destination-address)
- [6621 Client comm layer attempted to use a send address that was already in use](#6621-client-comm-layer-attempted-to-use-a-send-address-that-was-already-in-use)
- [6622 The winsock connection must be reset in the client comm layer](#6622-the-winsock-connection-must-be-reset-in-the-client-comm-layer)
- [6623 A winsock virtual circuit was aborted](#6623-a-winsock-virtual-circuit-was-aborted)
- [6624 A winsock virtual circuit was reset remotely](#6624-a-winsock-virtual-circuit-was-reset-remotely)
- [6625 Client comm layer socket is not connected](#6625-client-comm-layer-socket-is-not-connected)
- [6626 Client comm layer socket already shut down](#6626-client-comm-layer-socket-already-shut-down)
- [6627 Client comm layer winsock system was not properly initialized](#6627-client-comm-layer-winsock-system-was-not-properly-initialized)
- [6628 Client comm layer did not send all data](#6628-client-comm-layer-did-not-send-all-data)
- [6629 Client comm layer received a packet from an incorrect source](#6629-client-comm-layer-received-a-packet-from-an-incorrect-source)
- [6630 An invalid function pointer was found in the client comm layer](#6630-an-invalid-function-pointer-was-found-in-the-client-comm-layer)
- [6631 An unexpected exception occurred in the client comm layer](#6631-an-unexpected-exception-occurred-in-the-client-comm-layer)
- [6632 Watch dog thread creation failed](#6632-watch-dog-thread-creation-failed)
- [6633 The Advantage Database Server did not respond to a database request in a timely manner](#6633-the-advantage-database-server-did-not-respond-to-a-database-request-in-a-timely-manner)
- [6634 The inter-process communications (IPC) object is no longer valid](#6634-the-inter-process-communications-ipc-object-is-no-longer-valid)
- [6669 Tag list is corrupt](#6669-tag-list-is-corrupt)

## 6602 Client comm layer timed out waiting for receive packet from the Advantage Database Server {#6602-client-comm-layer-timed-out-waiting-for-receive-packet-from-the-advantage-database-server}

## 6604 Timeout waiting for intermediate burst acknowledgement {#6604-timeout-waiting-for-intermediate-burst-acknowledgement}

Client comm layer timed out waiting for acknowledgment of intermediate burst of packets sent to the Advantage Database Server

## 6605 Client comm layer received more data from the Advantage Database Server than it was expecting {#6605-client-comm-layer-received-more-data-from-the-advantage-database-server-than-it-was-expecting}

## 6606 Amount of client protocol command information to send was greater than the maximum allowed {#6606-amount-of-client-protocol-command-information-to-send-was-greater-than-the-maximum-allowed}

## 6607 Protocol command information received by the client was not of the expected size {#6607-protocol-command-information-received-by-the-client-was-not-of-the-expected-size}

## 6609 Client comm layer received data of an unknown origin {#6609-client-comm-layer-received-data-of-an-unknown-origin}

## 6610 The Advantage Database Server did not respond to a database request in a timely manner {#6610-the-advantage-database-server-did-not-respond-to-a-database-request-in-a-timely-manner}

A communications problem has occurred. Search for 6610 in the Advantage Knowledge Base for possible solutions.

## 6611 Client communications layer timed out when attempting to send a packet {#6611-client-communications-layer-timed-out-when-attempting-to-send-a-packet}

When using IPX communication with a 16-bit application, this error indicates that the communications layer timed out while waiting for a free ECB to use to send data to the Advantage Database Server.

With 32-bit applications, this error indicates that the send on a socket timed out. It may mean that the connection was dropped due to a network failure.

## 6612 Client comm layer received a packet that was out of sequence and was beyond the acceptable range of sequence numbers {#6612-client-comm-layer-received-a-packet-that-was-out-of-sequence-and-was-beyond-the-acceptable-range-of-sequence-numbers}

## 6613 An IPX event was canceled {#6613-an-ipx-event-was-canceled}

## 6614 IPX/SPX not initialized on client {#6614-ipx-spx-not-initialized-on-client}

## 6615 Client comm layer is out of DOS memory {#6615-client-comm-layer-is-out-of-dos-memory}

## 6616 Client comm layer found no free ECBs available {#6616-client-comm-layer-found-no-free-ecbs-available}

## 6617 Client comm layer Winlock failed {#6617-client-comm-layer-winlock-failed}

## 6618 Maximum tasks reached or IPX DLLs not found {#6618-maximum-tasks-reached-or-netware-dlls-not-found}

Either the maximum number of tasks available to use the client comm layer has been reached or the NWCALLS.DLL and/or NWIPXSPX.DLL were not found.

## 6619 Client comm layer was already busy with one database operation when a second database operation was requested {#6619-client-comm-layer-was-already-busy-with-one-database-operation-when-a-second-database-operation-was-requested}

Advantage clients support functionality to call a "progress" function during index creation and reindexing. If this progress function makes a call to the Advantage Database Server, such as to AdsGetRecordCount() or LastRec(), a 6619 error will occur. A call cannot be made to the Advantage server at this time because the communication layer is busy with the creation of the index. Only one call can be using the communication layer at a time. Only use functions that do not require a call to the Advantage Database Server in the index creation progress function. If the number of records in the table is needed by the index creation progress function, retrieve that information before the index creation operation and store the results in a variable for use in the index creation progress function.

**Note** It is possible to get a 6619 error when executing database operations in an Advantage Extended Procedure (AEP). If using Advantage Local Server the client application and the AEP must use the same "ShowDeleted" setting. If both the client and AEP are written in the same language this is usually not a problem. If the settings are mismatched you may receive a 6619 (comm layer was busy) error.

## 6620 Client comm layer did not have the needed Advantage Database Server destination address {#6620-client-comm-layer-did-not-have-the-needed-advantage-database-server-destination-address}

## 6621 Client comm layer attempted to use a send address that was already in use {#6621-client-comm-layer-attempted-to-use-a-send-address-that-was-already-in-use}

## 6622 The winsock connection must be reset in the client comm layer {#6622-the-winsock-connection-must-be-reset-in-the-client-comm-layer}

## 6623 A winsock virtual circuit was aborted {#6623-a-winsock-virtual-circuit-was-aborted}

## 6624 A winsock virtual circuit was reset remotely {#6624-a-winsock-virtual-circuit-was-reset-remotely}

A remote socket connection was closed by the server. This error will usually be raised by client applications if the server is shut down when clients are still connected.

## 6625 Client comm layer socket is not connected {#6625-client-comm-layer-socket-is-not-connected}

## 6626 Client comm layer socket already shut down {#6626-client-comm-layer-socket-already-shut-down}

## 6627 Client comm layer winsock system was not properly initialized {#6627-client-comm-layer-winsock-system-was-not-properly-initialized}

## 6628 Client comm layer did not send all data {#6628-client-comm-layer-did-not-send-all-data}

## 6629 Client comm layer received a packet from an incorrect source {#6629-client-comm-layer-received-a-packet-from-an-incorrect-source}

## 6630 An invalid function pointer was found in the client comm layer {#6630-an-invalid-function-pointer-was-found-in-the-client-comm-layer}

## 6631 An unexpected exception occurred in the client comm layer {#6631-an-unexpected-exception-occurred-in-the-client-comm-layer}

## 6632 Watch dog thread creation failed {#6632-watch-dog-thread-creation-failed}

The thread used to send keep-alive packets from the client to the server failed during creation.

## 6633 The Advantage Database Server did not respond to a database request in a timely manner {#6633-the-advantage-database-server-did-not-respond-to-a-database-request-in-a-timely-manner}

***Problem***: This error will occur if the server does not respond to the client while using inter-process communications when the client and server processes are on the same physical workstation.

***Solution***: Verify that Advantage Database Server is still running. If it is running, then check the MAX_TIMEOUTS value in the ads.ini file. If that value is very small and the server is extremely busy, it is possible that the server might not be able to respond in the timeout period. Increase the value (or remove it from the ads.ini file so that the default value will be used).

## 6634 The inter-process communications (IPC) object is no longer valid {#6634-the-inter-process-communications-ipc-object-is-no-longer-valid}

***Problem***: This error indicates that the connection to the server has been lost while using inter-process communications. The communications channel has been given to another client.

***Solution***: Close the connection and open a new one. It is expected that this error would only occur if the server was stopped and restarted while the client was still running.

## 6669 Tag list is corrupt {#6669-tag-list-is-corrupt}

*[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)