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 System Management Hub or in the log file of the Administration Service. The Broker Agents of System Management Hub can replace messages of class 0302 with their own messages or dialogs.
03020000 | 03020001 | 03020002 | 03020003 | 03020004 | 03020005 | 03020006 | 03020007 | 03020008 | 03020009 | 03020010 | 03020011 | 03020012 | 03020013 | 03020014 | 03020015 | 03020016 | 03020017 | 03020018 | 03020019 | 03020020 | 03020021 | 03020022 | 03020023 | 03020025 | 03020028 | 03020029 | 03020031 | 03020032 | 03020033 | 03020034 | 03020035 | 03020036 | 03020037 | 03020038 | 03020045 | 03020046 | 03020047 | 03020048 | 03020049 | 03020050 | 03020051 | 03020052 | 03020053 | 03020054 | 03020055 | 03020056 | 03020057 | 03020058 | 03020059 | 03020060 | 03020061 | 03020062 | 03020063 | 03020064 | 03020065 | 03020066 | 03020067 | 03020068 | 03020069 | 03020070 | 03020071 | 03020072 | 03020073 | 03020083 | 03020084 | 03020085 | 03020086 | 03020087 | 03020088 | 03020089 | 03020090 | 03020091 | 03020092 | 03020093 | 03020094 | 03020095 | 03020097 | 03020098 | 03020100 | 03020102 | 03020104 | 03020105 | 03020106| 03020000 | Admin 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. |
| 03020002 | Rule name missing |
| Explanation |
The name of an authorization rule was not specified. |
| Action |
Check and correct the correspoding field in SMH or the RPC program. |
| 03020003 | Service or topic name missing |
| Explanation |
The name of a service service or topic was not specified or is invalid. |
| Action |
Check and correct the corresponding input field in SMH. |
| 03020004 | Class name wrong or missing |
| Explanation |
The name of a class was not specified or is invalid. |
| Action |
Check and correct the corresponding input field in SMH. |
| 03020005 | Server name wrong or missing |
| Explanation |
The name of a server was not specified or is invalid. |
| Action |
Check and correct the corresponding input field in SMH. |
| 03020006 | Service name wrong or missing |
| Explanation |
The name of a service was not specified or is invalid. |
| Action |
Check and correct the corresponding input field in SMH. |
| 03020007 | Topic name wrong or missing |
| Explanation |
The name of a topic was not specified or is invalid. |
| Action |
Check and correct the corresponding input field in SMH. |
| 03020008 | User name wrong or missing |
| Explanation |
The name of a user was not specified or is invalid. |
| Action |
Check and correct the corresponding input field in SMH. |
| 03020009 | Set name wrong or missing |
| Explanation |
The name of a set was not specified or is invalid. |
| Action |
Check and correct the corresponding input field in SMH. |
| 03020010 | Logical broker name wrong or missing |
| Explanation |
The name of a logical broker was not specified or is invalid. |
| Action |
Check and correct the corresponding input field in SMH. |
| 03020011 | Real broker ID list wrong or missing |
| Explanation |
The name of a real broker ID list was not specified or is invalid. |
| Action |
Check and correct the corresponding input field in SMH. |
| 03020012 | Logical service name wrong or missing |
| Explanation |
The name of a logical service was not specified or is invalid. |
| Action |
Check and correct the corresponding input field in SMH. |
| 03020013 | Class/server/service name wrong or missing |
| Explanation |
The name of a class/server/service was not specified or is invalid. |
| Action |
Check and correct the corresponding input field in SMH. |
| 03020014 | Logical broker list wrong or missing |
| Explanation |
The logical broker list was not specified or is invalid. |
| Action |
Check and correct the corresponding input field in SMH. |
| 03020015 | Broker name wrong or missing |
| Explanation |
The name of the broker was not specified or is invalid. |
| Action |
Check and correct the corresponding input field in SMH. |
| 03020016 | TCP port duplicate or wrong value |
| Explanation |
The name of the TCP port is duplicate or is invalid. |
| Action |
Check and correct the corresponding input field in SMH. |
| 03020017 | SSL port duplicate or wrong value |
| Explanation |
The name of the SSL port is duplicate or is invalid. |
| Action |
Check and correct the corresponding input field in SMH. |
| 03020018 | Transport wrong or missing |
| Explanation |
The transport was not specified or is missing. |
| Action |
Check and correct the corresponding input field in SMH. |
| 03020019 | Create key failed |
| Explanation |
A new key could not be added to the Administration Service data file. |
| Action |
Check the file config/xds.ini and any directory services that were used. If you are using LDAP, it is possible that the LDAP server is no longer accessible. |
| 03020020 | Celete key failed |
| Explanation |
A key could not be removed from the Administration Service data file. |
| Action |
Check config/xds.ini and any directory services that were used. If you are using LDAP, it is possible that the LDAP server is no longer accessible.. |
| 03020021 | Get value failed |
| Explanation |
The value of a key could not be determined from the Administration Service data file. |
| Action |
Check config/xds.ini and any directory services that were used. If you are using LDAP, it is possible that the LDAP server is no longer accessible.. |
| 03020022 | Set value failed |
| Explanation |
Write access to Administration Service data was not successful. |
| Action |
Check config/xds.ini and any directory services that were used. If you are using LDAP, it is possible that the LDAP server is no longer accessible.. |
| 03020023 | Could not create Broker |
| Explanation |
The broker could not be created. The Administration Service tried to create a directory in the EntireX directory 'config/etb/' and to store the attribute file in this directory. |
| Action |
Check the permission of config/etb or any directory created. |
| 03020025 | Could not open attribute file ETBnnn.ATR |
| Explanation |
The attribute file config/etb/etbnn.atr could not be opened. |
| Action |
Check the permissions for file config/etb/ETBnnn.ATR. |
| 03020028 | Administration Service internal error |
| Explanation |
The Administration Service has detected an internal error. |
| Action |
Contact Software AG support. |
| 03020029 | Not yet implemented |
| Explanation |
The function that was called has not yet been implemented. |
| Action |
None. |
| 03020031 | Out of memory |
| Explanation |
A storage request of the Administration Service failed. |
| Action |
Check whether sufficient system resources are available. |
| 03020032 | Value buffer too small |
| Explanation |
The Administration Service has detected an internal error. |
| Action |
Contact Software AG support. |
| 03020033 | Key already exists |
| Explanation |
The key already exists in the data file. An attempt was made to re-create a broker that already exists. |
| Action |
None; SMH issues a suitable message. |
| 03020034 | Duplicate value |
| Explanation |
The Administration Service has detected an internal error. |
| Action |
None; the problem was solved by internal programming. |
| 03020035 | Could not start process |
| Explanation |
A process could not be started. |
| Action |
Check the log files of the process to be started. The EntireX directory config/etb/ contains the working directory of all local brokers. For example, if an attempt was made to start broker ETB001, all log files for ETB001 are in directory ETB001. The file with suffix ".etbsrv" provides information on the failed process. |
| 03020036 | Could not start process as user |
| Explanation |
A process could not be started. |
| Action |
Check the log files of the process to be started. The EntireX directory config/etb/ contains the working directory of all local brokers. For example, if an attempt was made to start broker ETB001, all log files for ETB001 are in directory ETB001. The file with suffix ".etbsrv" provides information on the failed process. |
| 03020037 | Broker is already started |
| Explanation |
A process could not be started because it was already active. |
| Action |
None. |
| 03020038 | Could not find service in data file |
| Explanation |
The broker or service was not found in the data file or LDAP. |
| Action |
None; error processing is handled by SMH. |
| 03020045 | Administrator session timed out |
| Explanation |
The administrator session has expired. |
| Action |
Repeat the failed operation with valid credentials. |
| 03020046 | Invalid command |
| Explanation |
Invalid RPC command. |
| Action |
Broker SMH agent error, contact Software AG support. |
| 03020047 | Broker already exists |
| Explanation |
The Broker already exists. |
| Action |
Change the name of the broker in SMH. |
| 03020048 | Duplicate ports not allowed |
| Explanation |
Duplicate port numbers are not allowed. |
| Action |
Change the port number in SMH. |
| 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 SMH; 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. |
| 03020051 | CIS Command service request failed |
| Explanation |
A broker CIS command 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 | Internal error invalid control block |
| Explanation |
Internal error; an invalid control block was detected. |
| Action |
Contact Software AG support. |
| 03020053 | Invalid credentials |
| Explanation |
Invalid credentials were used to access the Administration Service. This message can be given after a change of password. |
| Action |
Log off SMH and log on again. |
| 03020054 | Broker is already stopped |
| Explanation |
An attempt was made to stop a broker that has not started. |
| Action |
None. |
| 03020055 | Internal error invalid values |
| Explanation |
Internal error. A broker with invalid data was found. |
| Action |
Contact Software AG support. |
| 03020056 | SSL parameters too long for para string |
| Explanation |
The length of the SSL parameters exceeds the maximum permitted. |
| Action |
Correct the SSL parameters in SMH. |
| 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/ETBSRV/ 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/ETBSRV/ contains details of the failed write or copy attempt. |
| 03020060 | Forbidden character in file name |
| Explanation |
The Administration Service checks the broker name for illegal characters. Broker ID, directory and file names are generated automatically from the broker name. This error message is issued if the broker name contains invalid special characters. |
| Action |
Correct the broker name in SMH. |
| 03020061 | Could not open file |
| Explanation |
A file could not be opened. |
| Action |
The Administration Service log in the EntireX directory config/etb/ETBSRV/ contains details on the failed access attempt. |
| 03020062 | Remote Broker already exists |
| Explanation |
An attempt was made to add an existing broker instance. |
| Action |
Correct the broker name or the remote broker ID in SMH. |
| 03020063 | File not found |
| Explanation |
A file could not be found, or invalid permissions. |
| Action |
The Administration Service log in the EntireX directory config/etb/ETBSRV/ contains details on the failed access attempt. |
| 03020064 | Download error |
| Explanation |
Reserved for future use. |
| Action |
None. |
| 03020065 | Upload error |
| Explanation |
Reserved for future use. |
| Action |
None. |
| 03020066 | Could not read file |
| Explanation |
The read access to a file failed. |
| Action |
The Administration Service log in the EntireX directory config/etb/ETBSRV/ 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/ETBSRV/ contains details on the failed access attempt. |
| 03020068 | Invalid attribute file |
| Explanation |
The contents of the attribute file is invalid. This error can occur when an attribute file is being migrated. |
| Action |
Add the broker manually, using SMH. |
| 03020069 | Could not write attribute file |
| Explanation |
The write access to an attribute file failed. |
| Action |
In the Administration Service log in the EntireX directory config/etb/ETBSRV/ contains details on the failed access attempt. |
| 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/ETBSRV/ contains details on the failed access attempt. |
| 03020072 | Could not open attribute file for ETBSRV |
| Explanation |
The Administration Service could not open its own attribute file. The error can only occur during installation. |
| Action |
The Administration Service log in the EntireX directory config/etb/ETBSRV/ 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. |
| 03020083 | Data file: parameter error |
| Explanation |
Internal Error. |
| Action |
Contact Software AG support. |
| 03020084 | Data file: out of memory |
| Explanation |
There is not enough memory available to read in the data file. |
| Action |
Check whether sufficient system resources are available. |
| 03020085 | Data file: file I/O error |
| Explanation |
A read/write operation on the data file failed. |
| Action |
Determine the cause of the error and correct it. File config/xds.ini contains detailed information on the data file. Possible source of error:
|
| 03020086 | Data file: internal error |
| Explanation |
An internal error was detected. |
| Action |
Contact Software AG support. |
| 03020087 | Data file: invalid parameter string |
| Explanation |
Internal Error. |
| Action |
Contact Software AG support. |
| 03020088 | Data file: invalid directory service |
| Explanation |
A parameter |
| Action |
Check all parameters |
| 03020089 | Data file: LDAP initialization failed |
| Explanation |
A connection to the LDAP server could not be established. |
| Action |
Check the hostname and port number in file config/xds.ini. |
| 03020090 | Data file: LDAP server bind failed |
| Explanation |
A connection to the LDAP server could not be established. |
| Action |
Check the LDAP parameters, including password in file config/xds.ini. |
| 03020091 | Data file: duplicate key |
| Explanation |
An attempt was made to add an existing key. |
| Action |
None. |
| 03020092 | Data file: invalid key name |
| Explanation |
An attempt was made to use an invalid key name. |
| Action |
None. |
| 03020093 | Data file: generic LDAP error |
| Explanation |
An error occurred when trying to access LDAP. |
| Action |
Check the network connection to the LDAP server and the LDAP installation. |
| 03020094 | Data file: duplicate values |
| Explanation |
Duplicate or multiple values were detected. |
| Action |
None. |
| 03020095 | Data file: corrupt date file |
| Explanation |
The data file is corrupt. The internal structure was damaged. |
| Action |
Determine the data file using config/xds.ini and replace the data file with a backup. If no backup exists, delete the file and add authorization rules again. The data of the Administration Service will be automatically re-generated when the data file is deleted. |
| 03020097 | Data file: no data |
| Explanation |
No data exists in the data file or LDAP. |
| Action |
None. |
| 03020098 | Data file: no such key |
| Explanation |
The key that was searched for does not exist in the data file or LDAP. |
| Action |
None. |
| 03020100 | Data file: xds.ini file not found |
| Explanation |
The file config/xds.ini was not found. |
| Action |
Add a new file config/xds.ini. |
| 03020102 | Data file: invalid parameter |
| Explanation |
Internal Error. |
| Action |
Contact Software AG support. |
| 03020104 | Data file: insufficient memory |
| Explanation |
Not enough memory available to read the data file. |
| Action |
Check whether sufficient system resources are available. |
| 03020105 | Data file: internal error |
| Explanation |
Internal Error. |
| Action |
Contact Software AG support. |
| 03020106 | Data file: duplicate values |
| Explanation |
Duplicate or multiple values were detected. |
| Action |
None. |
