Error Code | Error Text | Error Analysis |
221 | CPIC_ERROR | Internal CPI-C error |
222 | CANT_GET_MEMORY | Memory bottle neck, because either the shared memory blocks or the main memory is too low. |
223 | NI_READ_FAILED | Network read error, network problems, or partner has terminated |
224 | NI_WRITE_FAILED | Network write error, network problems, or partner has terminated |
225 | INVALID_REQUEST | Unknown request type in APPC header |
228 | SHM_READ_FAILED | No longer used |
229 | SHM_WRITE_FAILED | Attempt to write to the index area of the gateway failed |
230 | CONN_EXCEEDED | Maximum number of connections in the gateway has been reached Increase value of parameter gw/max_conn |
233 | WRONG_COMM_TYPE | Unknown connection type Permitted types are only:
I for internal connections, partner is in R/3 E for external connections, external partner E for external connections, partner is registered C for external connections, partner is in R/2 |
234 | CONNECT_FAILED | Attempt to open connection to gateway failed. Check the host name and service. If these are correct, check whether the gateway is actually running and is listening to the correct port. Your own host name(s) and the ports the gateway listen to are in the first lines of the trace file (dev_rd). |
235 | COMM_TABLE_ERROR | Error in the administration structure that the gateway shares with the SAP System (communication table). |
236 | GW_CONNECT_FAILED | See CONNECT_FAILED |
237 | GW_DISCONNECTED | Connection to the gateway has been closed (CPIC-SS ), or the gateway should open a connection to a different gateway, and an earlier attempt had already failed. If the connection to another gateway fails, the next attempt is not until 60 seconds later. If connection requests arrive at this gateway during this time, they are rejected and assigned this error status. |
238 | WRITE_TO_GW_FAILED | Network write error, network problems, or the remote gateway has been closed. |
239 | READ_FROM_GW_FAILED | Network read error, network problems, or the remote gateway has been closed. |
240 | INVALID_LEN | Destination length is longer than an APPC request block; or the length of the data packet is shorter than the length of the APPC header. |
242 | GW_TIMEOUT | Connection setup to the remote gateway has been closed because timeout has been exceeded. The time limit can be set in parametergw/timeout. |
244 | SYSTEM_DISCONNECTED | The connection to the partner has already been closed, yet the system is still attempting to connect to the partner. |
245 | MEM_OVERFLOW | The overflow area can no longer store the data. If a partner sends data much quicker than the partner can receive it, the data is stored temporarily in the overflow area. The size of the area is set in the parameter gw/max_overflow_size. The memory is for local processes. The default is 1 MByte and you can increase this as appropriate. |
246 | WRONG_APPCHDR_VERSION | The protocol header exchanged between gateways and CPIC/RFC clients contains an invalid version number. |
247 | GW_APPC_SERVER_DOWN | The data could not be sent from the SAP System to the gateway. Check that the gateway is running. |
248 | TXCOM_TABLE_FAILED | Entry in table TXCOM was not found or there is a problem with the database table itself. Check that the symbolic destination exists (transaction SM54). |
249 | COMM_TABLE_OVERFLOW | The communication table is full. The size of the table or the number of entries is set in the parameter rdisp/max_comm_entries. The value should be at least as big as the value of parameter gw/max_conn. |
450 | C_NO_MEM | Request for memory unsuccessful. |
451 | C_NO_SIDE_INFO | Side info file could not be found. If the environment variable SIDE_INFO is not defined, the file sideinfo is searched for in the current directory. |
455 | C_SIGNAL | The signal SIGALRM could not be set. |
456 | C_TIMEOUT | Timeout reached when allocating an SNA connection. The timeout can be set in the environment variable CPIC_TIMEOUT. |
472 | C_NO_SIDE_INFO_ENTRY | Side info entry could not be found. |
473 | C_NO_CONV | Conversation ID could not be found. |
474 | C_MANUAL_CANCELD | The connection has been terminated manually (for example, by the system administrator). |
476 | C_NO_PARTNER | The connection partner could not be assigned. |
485 | C_GETHOSTNAME | The local host name could not be determined. |
486 | C_NO_SAP_CMACCP | SAP_CMACCP call is missing. This call must be the first call made in a CPIC program that is to be stated from a different program. |
487 | C_NO_PROGRAM_NAME_ARG | The local program name could not be found in the argument list. Check that all arguments have been passed to the program. |
488 | C_NO_HOST_ARG | The gateway host name could not be found in the argument list. Check that all arguments have been passed to the program. |
489 | C_NO_SERV_ARG | The gateway service could not be found in the argument list. Check that all arguments have been passed to the program. |
490 | C_NO_CONVID_ARG | The conversation ID could not be found in the argument list. Check that all arguments have been passed to the program. |
491 | C_ILLEGAL_PARAMETER | A CPIC call has been made incorrectly, look out for further error messages. |
497 | C_NIHOSTTOADDR | The resolution of the IP address from the host name has failed. |
498 | C_NIADDRTOHOST | The resolution of the host name from the IP address has failed. |
499 | C_THOST_FAILED | The conversion of the short host name to the long host name from table THOST has failed. |
635 | FORK_FAILED | Local program could not be started. Possible causes of the error are:
Program is not available. Program is not allowed to be executed. Program is not in the search path. |
636 | BAD_NI_HANDLE | An invalid handle has been passed to the network layer. |
637 | REXEC_FAILED | Remote program could not be started using rexec(). Possible causes of the error are:
User does not exist on the remote host. Password of user is incorrect. The gateway host is not entered in the .rhosts file. Program is not available. Program is not allowed to be executed. Program is not in the search path. |
638 | TP_START_FAILED | Remote program could not be started using remsh(). Possible causes of the error are:
ID does not exist on the remote host. The gateway host is not entered in the .rhosts file. Program is not available. Program is not allowed to be executed. Program is not in the search path. |
676 | GW_SECURITY_ERROR | Program is not allowed to be started. File secinfo defines who is allowed to start which programs. |
677 | GW_TIMEOUT_REG_PRGM | Timeout while waiting for a registered program to become free. The registered program was being used by a different partner the whole time. Try starting the registered program in parallel or by minimizing the time the program can be used for. |
678 | TP_REGISTERED | Transaction program is registered. |
679 | TP_NOTREGISTERED | Transaction program is not registered. |
720 | TP_REG_SECU_ERROR | Program is not allowed to be registered. File secinfo defines which programs on which hosts are allowed to be registered. |
721 | GW_SNC_DISABLED | A client wants to communicate using SNC, but SNC is deactivated in the gateway. Whether the gateway can communicate using SNC is defined in the parameter snc/enable. |
722 | GW_SNC_REQUIRED | A client want to communicate without SNC, but SNC is defined as obligatory for all connections. |
728 | CONV_ID_NOT_FOUND | Conversation ID could not be found. |
731 | GW_SHUTDOWN | Gateway is being shutdown. This return code is sent to all open connections. |
732 | GW_REM_PRGM_DISABLED | Remote programs are not allowed to be started. This is defined in parameter gw/rem_start. |
737 | GW_CONNECT_TIMEOUT | Timeout while setting up connection to a remote gateway. The gateway interrupts the action and continues it later, as soon as data can be written and read again on the network channel (socket). |
738 | GW_REQ_TO_DP_FAILED | The gateway could not put the request into the dispatcher queue. Probably the number of requests that can be waiting in the queue at any one time has been exceeded. |
760 | C_NO_SIDE_INFO_GW | No Side Information File exists for the gateway. |
765 | C_SNC_DISABLED | A client wants to communicate using SNC, but SNC is deactivated. |
766 | C_SNC_ERROR | General SNC error - more details in the error info. |
767 | C_SNC_MODE_ON | A client want to communicate without SNC, but SNC is defined as obligatory for these connections. |
768 | C_SNC_NOT_AVAILABLE | SNC is not available. |