Appendix B       iDAR Error Guide


The error numbers and text are logged by iPlanet Directory Access Router (iDAR) if some exception condition occurs. Only those errors that warrant an explanation are listed in this appendix.

The appendix has the following sections:

• Unnumbered Errors

• Numbered Errors

Unnumbered Errors

---

These errors are unnumbered and will happen only if an error occurs before iDAR could initialize itself.

Registry settings are not present

Installation problem or the Registry entries deleted by the Administrator.

Could not open log file %s

On Windows NT this means %IDAR_ROOT%\logs\fwd.log is not accessible where IDAR_ROOT is the variable in the registry.

On UNIX platforms, iDAR was not started with -s option and ${IDAR_ROOT}/logs/fwd.log is not accessible.

RegisterServiceCtrlHandler call failed
StartServiceCtrlDispatcher call failed

Only on Windows NT. Administrator did not reboot after installation. Or, bad installation. Or, Administrator tried to run iDAR from the command line without the -I flag.

Syslog is not available on Windows NT platform

Administrator tried to configure syslog (in ids-proxy-sch-LogProperty) on Windows NT.

Numbered Errors

---

These errors are generated by iDAR; each is distinct.

100203 Missing second quote in RDN AVA
100301 Too many AVAs in RDN (%d)
100302 Problem decoding RDN component
100303 Extra quote in RDN
100304 Problem decoding RDN component

Badly formed RDN component.

110201 Could not open %s

Could not open the initial tailoring file.

110202 Line %d too long/missing newline

Each line in the initial tailoring file must be terminated with a new line, or the line is more than 1024 characters long.

110203 Missing colon in line %d

Each option/value pair in the initial tailoring file must be separated by a colon.

110204 Unrecognized keyword in line %d (%s)
110205 Problem parsing line %d (%s)

Bad option name in initial tailoring file.

110207 Unknown configuration_url type %s

The protocol selector must be either ldap or file for configuration_url in the initial tailoring file.

110303 Problem parsing (%s)

One of the attribute values in the ids-proxy-sch-GlobalConfiguration entry was bad.

110401 Unknown property object %s referenced from global entry
110402 Unknown property object %s referenced from global entry

The property being referenced is incorrectly specified. This could mean either the property entry is incorrectly specified or it is not being included correctly. Run iDAR in debug mode and make sure all the properties are added. Make sure the spelling of the property name is correct at the point of inclusion.

110403 Unknown property type %s referenced from %s

110404 Unknown property type %s referenced from %s

Only allowed property from ids-proxy-sch-GlobalConfiguration object class is ids-proxy-sch-LogProperty.

130108 ids-proxy-con-ava has attribute name specified twice in %s
in %s

An attribute name was specified twice.

150201 SetServiceStatus call failed

Windows NT service manager configuration problem.

150304 Failed to Reread Configuration... Aborted

iDAR tried to reread its config files and failed.

150403 iDAR process %d has exited, attempting restart in 10 seconds

The monitor has detected that iDAR has exited abnormally and will attempt to restart it.

170802 Could not decode sasl cred

iDAR could not decode the credentials received from the client as part of a SASL bind.

170910 Operation received while SASL bind in progress

No operations are allowed when a SASL bind is in progress. The client sent a request other than "bind" while SASL bind was in progress.

170911 Duplicate message id received: %d

The client sent two simultaneous requests with the same message id.

170912 Operation received between SSL negotiation

No operations are allowed when the START TLS is in progress. The client initiated START TLS but send other operations before completing it.

171012 Could not establish SSL for referral server

SSL could not be established with a LDAP server to which iDAR was referred.

171027 OnBindSuccess rule failed... closing connection

An error occurred while evaluating OnBindSuccess rule. Note: This error message does not mean OnBindSuccess rule evaluated to FALSE.

190201 Wrong number of elements in NOT filter

Bad filter.

190402 First tag was not a SEQUENCE: source(%s, %d)
190403 First element was not a MessageID: source(%s, %d)

A incorrectly formatted PDU was received from the client or the server.

210302 ber_flush failed: Destination(%s, %d)
210303 ber_flush failed: Destination(%s, %d)

iDAR failed to send data to the server or the client because either the connection was reset or other network problems exist.

240101 Failed to tailor entry %s for attribute %s a bad attribute was found in a Group entry.

240102 Either (or both) LoadBalanceProperty or ids-proxy-con-server are present in %s

One of the above is allowed.

240201 A Property failed check from group %s

One of the properties included in this group was inconsistent with the Group.

240701 Could not find property %s referenced from %s

There can be several reasons for this. You must reference a property by its name, i.e., the value of the attribute ids-proxy-con-Name in the property entry you are referencing. Check to see if the spelling is correct. The next thing to check is if the referred property is one level under the value of ids-proxy-sch-PropertyBase attribute in the ids-proxy-sch-LDAPProxy object entry. Then make sure if the referred property belongs to ids-proxy-sch-belongs-to the correct server instance and is enabled (ids-proxy-sch-enable).

240703 Wrong property type for ids-proxy-con-server in %s

The property type can only be ids-proxy-sch-LDAPServer.

280205 Could not find property %s referenced from %s

See 240701.

280302 Check failed of one of the server properties

One of the properties included in this property was inconsistent with the Property.

300301 Connection from %s has IP options present
300302 Could not clear IP options from %s
300402 Failed for %s,can't verify hostname

iDAR could not resolve a hostname.

300403 Host name/name mismatch %s
300404 Host name/address mismatch %s

A reverse lookup of the host yielded a different host name for the client.

301101 Failed

iDAR failed to send data to a client/server.

330207 Failed
330211 Failed

Call to listen for failed.

340101 Failed to open connection, #times tried %d

Could not open connection to configuration LDAP server.

340901 No file name specified

No configuration file name was found in startup configuration file.

340902 No Server Entry DN Specified

The DN for the server's entry (object class ids-proxy-sch-LDAPProxy) was missing from the startup configuration file.

340912 No proper type for Server Entry %s

The server entry must have an objectclass attribute with value ids-proxy-sch-LDAPProxy.

380101 Failed
380103 Failed

A thread could not be created.

380201 Failed
380202 Failed

A mutex lock could not be acquired.

510103 No group %s as referenced in %s found

See explanation of 240701. Similar logic applies to Groups.

520112 Contradiction between ids-proxy-con-use-version

The LDAP protocol version that iDAR is configured to use with a backend LDAP server must be supported by that backend server.