The messages have the format:
0302nnnn
| where | 0302 | is the message class, and |
| nnnn | is the message number in the range 0000 - 9999 |
Messages of class 0302 are caused by the Administration Service or related components. The messages can appear in the log file of the Administration Service.
Messages of class 0302 can result, for example, from the programs Defaultbroker, etbsrv, etbadm
or in programs generated with Command and Information Services IDLs.
03020000 | 03020001 | 03020004 | 03020012 | 03020013 | 03020014 | 03020015 | 03020016 | 03020017 | 03020019 | 03020023 | 03020026 | 03020029 | 03020030 | 03020031 | 03020035 | 03020036 | 03020038 | 03020044 | 03020045 | 03020046 | 03020049 | 03020050 | 03020052 | 03020053 | 03020057 | 03020058 | 03020059 | 03020061 | 03020063 | 03020064 | 03020066 | 03020067 | 03020068 | 03020070 | 03020071 | 03020073 | 03020074 | 03020075 | 03020076 | 03020077 | 03020078 | 03020079| 03020000 | Administration Service successfully executed |
| Explanation |
The Administration Service action has completed successfully. |
| Action |
None. |
| 03020001 | Invalid arguments |
| Explanation |
The Administration Service has detected invalid or missing arguments. |
| Action |
Contact Software AG support. |
| 03020004 | Startup Administration Broker worker thread requested |
| Explanation |
The Administration Service has requested the start of a worker thread that it requires. |
| Action |
None. This message is for information purposes only. |
| 03020012 | Command lost during forwarding |
| Explanation |
A command was lost during an exchange between the Administration Broker processes |
| Action |
Contact Software AG support. |
| 03020013 | Broker does not exist |
| Explanation |
The configuration data of the requested broker is missing. |
| Action |
None. This message is for information purposes only. |
| 03020014 | Broker already exists |
| Explanation |
The configuration data of the requested broker does already exist. |
| Action |
None. This message is for information purposes only. |
| 03020015 | Broker name wrong or missing |
| Explanation |
The name of the broker is missing or contains illegal chararacter(s). |
| Action |
Repeat the last action with a valid broker name. |
| 03020016 | TCP port duplicate or wrong value |
| Explanation |
The name of the TCP port is duplicate or is invalid. |
| Action |
Check and correct the arguments of the program call. |
| 03020017 | SSL port duplicate or wrong value |
| Explanation |
The name of the SSL port is duplicate or is invalid. |
| Action |
Check and correct the arguments of the program call. |
| 03020019 | Missing port number |
| Explanation |
The port number is missing or is invalid. |
| Action |
Repeat the last action with a valid port number. |
| 03020023 | Could not create a broker process |
| Explanation |
The start of a broker failed. |
| Action |
For detailed information see log file EntireX/config/etb/ETBADM/ETBSRV.LOG. |
| 03020026 | Broker not registered |
| Explanation |
The Administration Service has discovered an unregistered broker. |
| Action |
None. This message is for information purposes only. |
| 03020029 | Not yet implemented |
| Explanation |
The function that was called has not yet been implemented. |
| Action |
Contact Software AG support. |
| 03020030 | Data area too small |
| Explanation |
The data buffer for exchanging data between Administration Broker processes |
| Action |
Contact Software AG support. |
| 03020031 | Out of memory |
| Explanation |
A storage request of the Administration Service failed. |
| Action |
Check whether sufficient system resources are available. |
| 03020035 | Could not start process |
| Explanation |
A process could not be started. The Administration Service tried to start up a process: For process type "Broker" in directory config/etb and for process type "Service" in directory config/service. These directories contain attribute file, configuration file and log file. |
| Action |
Check the log files of the process to be started. The EntireX directory config/etb contains the working directory of all local brokers. The EntireX directory config/service contains the working directory of all local known services. For example, if an attempt was made to start broker ETB001, all log files for ETB001 are in directory ETB001. For more information see log files
|
| 03020036 | Could not start process as user |
| Explanation |
A process could not be started as user. The Administration Service tried to startup a process: For process type "Broker" in directory config/etb and for process type "Service" in directory config/service. These directories contain attribute file, configuration file and log file. |
| Action |
Check the log files of the process to be started. The EntireX directory config/etb contains the working directory of all local brokers. The EntireX directory config/service contains the working directory of all local known services. For example, if an attempt was made to start broker ETB001, all log files for ETB001 are in directory ETB001. For more information see log files
|
| 03020038 | Could not stop broker process |
| Explanation |
The broker process could not be stopped. |
| Action |
For more information see log files
|
| 03020044 | Administration Service not running |
| Explanation |
The Administration Service process is not started. |
| Action |
Under UNIX, start the Administration Service. Under Windows, start Administration Service from Window Service. Repeat the failed operation. |
| 03020045 | Administration Service 'etbadm' not registered |
| Explanation |
The Broker Service process etbadm could not be successfully registered with the Administration Service. |
| Action |
For more information see log files
|
| 03020046 | Invalid command |
| Explanation |
An invalid command was detected. |
| Action |
None. This message is for information purposes only. |
| 03020049 | BROKER-ID wrong or missing |
| Explanation |
No broker ID or an invalid ID was passed to the Administration Service. |
| Action |
Reenter the Broker ID in the used application; do not use special characters. |
| 03020050 | CIS Information service request failed |
| Explanation |
A broker CIS information request failed. |
| Action |
If the target broker has started, check its log file. For detailed information, it may be necessary to increase the trace level. |
| 03020052 | Control block does not exist |
| Explanation |
The broker or service control block for a specified broker or service does not exist. An invalid broker or service ID was used. This error can occur when two commands are processed in parallel, whereby one of the commands is a delete broker or delete service command. |
| Action |
Check the log files of the process to be started. The EntireX directory config/etb contains the working directory of all local brokers. The EntireX directory config/service contains the working directory of all local known services. For example, if an attempt was made to start broker ETB001, all log files for ETB001 are in directory ETB001. For more information see log files.
|
| 03020053 | Invalid credentials |
| Explanation |
Invalid credentials were used to access the Administration Service or a specific broker. This message can be given after a change of password. |
| Action |
Log on required in the used application. |
| 03020057 | Copy text file failed |
| Explanation |
A text file (e.g. attribute file or SSL certificates) could not be copied by the Administration Service. |
| Action |
The Administration Service log in the EntireX directory config/etb/ETBADM contains details of the failed copy attempt. |
| 03020058 | SSL certificate or key file not found |
| Explanation |
The SSL certificates could not be found in the EntireX directory config/etb. |
| Action |
Create your own SSL certificates and make available in the EntireX directory config/etb. |
| 03020059 | Could not write attribute file |
| Explanation |
The attribute file could not be created by the Administration Service. |
| Action |
The Administration Service log in the EntireX directory config/etb/ETBADM contains details of the failed write or copy attempt. |
| 03020061 | Could not open file |
| Explanation |
A file could not be opened. |
| Action |
The Administration Service log in the EntireX directory config/etb/ETBADM contains details on the failed access attempt. |
| 03020063 | Missing attribute file |
| Explanation |
No suitable attribute file could be found when creating the thread context. |
| Action |
None. This message is for information purposes only. |
| 03020064 | Missing broker API version |
| Explanation |
The broker API version could not be detected. |
| Action |
None. This message is for information purposes only. |
| 03020066 | Could not read file |
| Explanation |
The read access to a file failed. |
| Action |
The Administration Service log in the EntireX directory config/etb/ETBADM contains details on the failed access attempt. |
| 03020067 | Could not write file |
| Explanation |
The write access to a file failed. |
| Action |
The Administration Service log in the EntireX directory config/etb/ETBADM contains details on the failed access attempt. |
| 03020068 | Invalid attribute file |
| Explanation |
The contents of the attribute file are invalid. This error can occur when a broker attribute file is being migrated, or when
a broker or service is to be added with command |
| Action |
Correct the attribute file. |
| 03020070 | Internal error |
| Explanation |
General internal error of the Administration Service. |
| Action |
Contact Software AG support. |
| 03020071 | Could not open attribute file |
| Explanation |
The attribute file of a newly created broker could not be opened for writing. |
| Action |
The Administration Service log in the EntireX directory config/etb/ETBADM contains details on the failed access attempt. |
| 03020073 | Request timeout occurred |
| Explanation |
A request to start, stop or restart a broker could not be performed within a defined period. This error can occur if a broker process is stopped immediately due to an error in the broker attribute file. |
| Action |
Check the broker log file. |
| 03020074 | Access denied by Security Facility |
| Explanation |
The Administration Service security has returned an error. The user is not authorized to use the command-line utility of the Administration Service. |
| Action |
A security violation has occurred. This message and the related user ID are written to the Administration Service log. |
| 03020075 | Instance "EntireX Broker brokerId" is not reachable or not running |
| Explanation |
EntireX Broker is not available or stopped. |
| Action |
Try to start the EntireX Broker. |
| 03020076 | Instance "EntireX RPC Server for serverType serverId" is not reachable or not running |
| Explanation |
EntireX RPC Server is not available or stopped. |
| Action |
Try to start The EntireX RPC Server. |
| 03020077 | Administration port number of instance "EntireX RPC Server for serverType serverId" is invalid |
| Explanation |
Administration port number of the EntireX RPC Server is empty or invalid. |
| Action |
Open the Command Central server configuration of the RPC Server and insert a valid administration port number. |
| 03020078 | TCP port number of the Administration Service is invalid. Check the variable entirex.etbadm.tcp.port in the configuration file config/entirex.config |
| Explanation |
TCP port number of the Administration Service is empty or invalid. |
| Action |
Open the configuration file config/entirex.config in the Entirex directory and insert a valid TCP port number ( |
| 03020079 | Administration port number <port number> is invalid. Administration port number is in use for instance <InstanceId> |
| Explanation |
Administration port number is in use for another RPC server instance. |
| Action |
Enter a valid administration port number that is not in use by another RPC server instance. |