Version 9.5 SP1
 —  Error Messages and Codes  —

Message Class 0250 - EntireX ACI - Location Transparency Return Codes

The messages have the format:

0250nnnn

where 0250 is the message class, and
nnnn is the message number in the range 0000 - 9999

Overview of Messages

02500007 | 02500020 | 02500022 | 02500023 | 02500025 | 02500026 | 02500027 | 02500028 | 02500029 | 02500030 | 02500060 | 02500201 | 02500202 | 02500203 | 02500204 | 02500205 | 02500206 | 02500207 | 02500208 | 02501000 | 02501001 | 02501002 | 02501003

02500007 LocTrans: ECS conversion error
Explanation

(C components) The conversion of the directory data to UTF-8 failed.

Action

Check the conversion settings (parameter translatekey) and the conversion objects.


02500020 LocTrans: LDAP server connection failure
Explanation

(C components) The connection to the LDAP server failed.

Action

Check name and port of the LDAP server in file xds.ini. Check network connection to the LDAP server.


02500022 LocTrans: LDAP security error
Explanation

(C components) The LDAP server needs security settings.

Action

Check authentication for the LDAP server and authorization for the data on the LDAP server.


02500023 LocTrans: Invalid context parameter
Explanation

(C components) A keyword in the settings of the directory service is wrong.

Action

Check settings in file xds.ini.


02500025 LocTrans: Repository not found
Explanation

(C components) The requested repository or directory is not accessible.

Action

Check name and location of repository (flat file). Check host and port of LDAP directory.


02500026 LocTrans: Invalid directory service
Explanation

(C components) The requested directory service is not valid or not reachable.

Action

Check settings in file xds.ini and check reachability of directory.


02500027 LocTrans: baseDN required for LDAP
Explanation

(C components) The baseDN describes the location of the data in the directory. This baseDN must be present and not NULL.

Action

Check setting of baseDN in file xds.ini.


02500028 LocTrans: authPass required for LDAP
Explanation

(C components) For authenticated access authPass and authDN are needed in file xds.ini.

Action

Check setting of authDN and authPass in file xds.ini.


02500029 LocTrans: LDAP initialization failed
Explanation

(C components) The connection to the LDAP server failed to initialize.

Action

Check settings in file xds.ini and check reachability of directory.


02500030 LocTrans: LDAP server bind failed
Explanation

(C components) The LDAP server is not running or not reachable.

Action

Check if LDAP server is running and configuration (file xds.ini) is correct.


02500060 LocTrans: Logical Name not in directory
Explanation

(C components) The name of the logical service or the logical Broker ID is not found in the directory.

Action

Check with System Management Hub if the name is present in the directory.


02500201 LocTrans: No Broker ID found for <logical name>
Explanation

(Java components) For the <logical name>, no real Broker ID is configured.

Action

Use System Management Hub to configure a real Broker of the logical Broker ID <logical name>.


02500202 LocTrans: No running Broker found for <logical name>
Explanation

(Java components) For the <logical name>, real Brokers are configured, but none of these replies to KERNELVERSION call.

Action

Check if Brokers are up and running.


02500203 LocTrans: Could not resolve logical Broker for <logical name>
Explanation

(Java components) The <logical name> is not found in the directory.

Action

Use the System Management Hub to add this logical Broker ID or change directory.


02500204 LocTrans: Real service not unique for <logical name>
Explanation

(Java components) The logical service for <logical name> exists in the directory, but the configuration is corrupt.

Action

Use System Management Hub to delete this logical service and add it correctly.


02500205 LocTrans: No real service found for <logical name>
Explanation

(Java components) The logical service for <logical name> exists in the directory, but the real service is not configured.

Action

Use the System Management Hub to add the real service to this logical service.


02500206 LocTrans: No logical Broker found for <logical name>
Explanation

(Java components) The logical service for <logical name> exists in the directory, but the logical Broker ID is not configured.

Action

Use the System Management Hub to add the logical Broker ID to this logical service.


02500207 LocTrans: Description of logical service corrupt (<value>) for <logical name>
Explanation

(Java components) The logical service for <logical name> exists in the directory, but the configuration is corrupt.

Action

Use the System Management Hub to delete this logical service and add it correctly.


02500208 LocTrans: Error in configuration: <detailed description>
Explanation

(Java components) The directory is not reachable or there is some other error in the configuration.

Action

Check the configuration and verify that the directory service is running.


02501000 LocTrans: No logical service specified
Explanation

(C components) The specified logical service could not be found.

Action

Check the settings for file xds.ini. Verify entries with the System Management Hub Agent "Location Transparency".


02501001 LocTrans: No active Broker found
Explanation

(C components) No active Broker could be located while querying all of the specified Broker IDs for the given logical service.

Action

Check the settings for file xds.ini. Verify entries with the System Management Hub Agent "Location Transparency".


02501002 LocTrans: EXXLocTrans.dll file not found
Explanation

(C components) The Location Transparency library was not found.

Action

Restore the copy of EXXLocTrans.dll that was installed when EntireX was installed on the machine. If location transparency has never been used, the stubs may need to be reinstalled on the machine.


02501003 LocTrans: xds.ini file not found
Explanation

(C components) The file xds.ini was not found.

Action

Restore the previously used copy of xds.ini on the machine. If location transparency has never been used, the stubs may need to be reinstalled on the machine.


Top of page