CONNE_ILLEGAL_TRANSPORT_HEADER is an ABAP runtime error which you may come across when using or developing within an SAP system. See below for the standard details explaining what it means and how you can avoid or fix this runtime error.
Short Dump Classification: A - ABAP Programming Error
You can view further information about a runtme error by using transaction code ST22 which will show you this and all runtime erros that have happen in your SAP system.
Also check out the Comments section below to view or add related contributions and example screen shots.
Please see search hints for more details about the possible cause of this runtime error and how it could be avoided.
Please see send to sap for more details about the possible cause of this runtime error and how it could be avoided.
The IMPORT data set cannot be interpreted.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
Please see conne illegal header for more details about the possible cause of this runtime error and how it could be avoided.
The full transport header (initial part of CLUSTD):
<runtime parameter>
If the table in question is VBDATA (IMPORT FROM LOGFILE), the key now
follows (VBKEY). If not, the key is in the section 'Selected Variables'
below.
<runtime parameter>
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
CONNE_ILLEGAL_TRANSPORT_HEADER - conne illegal transport header CONNE_EXPORT_ILLEGAL_TYPE - conne export illegal type CONNE_DESCRIPTION_FLAG_INVALID - conne description flag invalid CONNE_CONTAINER_TOO_SHORT - conne container too short CONNE_COMPRESS_FLAG_INVALID - conne compress flag invalid COMPUTE_UNSUPPORTED_DECF_FUNC - compute unsupported decf func