Skip to content

ERR-7101D ( 462877) Protocol header error.#

Overview#

This document explains the cause of and solution for the ERR-7101D ( 462877) Protocol header error. message recorded in the Altibase server trace log.

Version#

All versions

Symptom#

The following error message is recorded in $ALTIBASE_HOME/trc/altibase_boot.log.

ERR-7101d(errno=0) Protocol header error.(TCP 127.0.0.1:13036)
Protocol processing failed. Close connection...

Cause#

This error occurs when a client version that is incompatible with the Altibase server attempts to connect to the server.

The server cannot process the protocol header sent by the client, so it closes the connection and records the error message in the trace log.

This error is only a record of a failed connection attempt from an incompatible client and does not affect Altibase server operation.

Solution#

If the error occurs repeatedly, identify the client attempting to connect to the Altibase server and use a client version that is compatible with the server.

Server and client version compatibility is determined as follows.

  • For clients earlier than Altibase 5.3.3, the server and client must have the same CM Protocol Version.
  • For Altibase 5.3.3 or later clients, the client can connect to a server of the same or a later version.
  • A client cannot connect to a server if the client version is later than the server version.
  • When comparing versions, use the first three version numbers, such as 6.3.1 or 7.1.0. Patch versions after the first three numbers are not considered.

The following table shows representative connection cases.

Server Version Client Version Connection Description
6.3.1 5.3.3 Available The client connects to a later server version.
6.1.1 6.3.1 Not available The client version is later than the server version.
6.3.1 4.3.9 Not available The server and client have different CM Protocol Version values.

Reference#

Use the following methods to check the server and client versions.

Checking the Server Version#

Run the altibase -v command on the server.

$ altibase -v
version 7.3.0.2.2 X86_64_LINUX_redhat_Enterprise_release6.0-64bit-7.3.0.2.2-release-GCC4.6.3 (x86_64-unknown-linux-gnu) Jul  6 2026 11:24:16, binary db version 7.3.0, meta version 9.4.1, cm protocol version 7.1.8, replication protocol version 7.4.9

The output shows the Altibase product version and CM Protocol Version.

Checking the APRE(SESC) Client Version#

For versions earlier than Altibase 5.3.3, run the sesc -v command.

$ sesc -v
 SES C/C++ Precompiler 3 Ver 4.3.9.234 XEON_LINUX_redhat_Enterprise_ES4-64bit-4.3.9.234-release-GCC3.4.6 (xeon-redhat-linux-gnu) Mar 10 2020 19:11:25

For Altibase 5.3.3 or later, run the apre -v command.

$ apre -v
Altibase Precompiler2(APRE) Ver.1 7.3.0.2.2 X86_64_LINUX_redhat_Enterprise_release6.0-64bit-7.3.0.2.2-release-GCC4.6.3 (x86_64-unknown-linux-gnu) Jul  6 2026 11:24:16

Checking the JDBC Driver Version#

Run the following command to check the JDBC driver version.

$ java -jar $ALTIBASE_HOME/lib/Altibase.jar
Altibase 7.3.0.2.2 with CMP 7.1.8 for JDBC 4.2 compiled with JDK 8

Checking the ODBC Driver Version on Windows#

Check the properties of altiodbc.dll in the lib directory of the Altibase client installation directory.

Example:

C:\Program Files (x86)\Altibase\ALTIBASE-HDB-Client-6.5.1.10.3\lib\altiodbc.dll

In the altiodbc.dll properties, check Details > Product version.