LDAP Directory Synchronizer
Online Documentation

HOME NEXT PREVIOUS

LDSU Errors

LDSU has two types of error messages, run-time and transaction. Run-time error messages appear to stdout (ldsu.log) during LDSU processing. Transaction error messages appear in the transaction log file (log_file parameter) and describe the status of an individual LDAP transaction.


LDSU Run-Time Error Messages

This section lists LDSU run-time error messages that may appear during LDSU processing. Run-time error messages are logged to stdout (which is captured in ldsu.log in an instance subdirectory) and, if FATAL, are written to the transaction log file (if defined). A FATAL status also causes LDSU to exit with a non-SUCCESS exit status by setting the ldsu_status variable.

The format of an LDSU error message is:

  %LDSU-<Severity>-<Code>, <Message>

    where:

      <Severity> = F (for FATAL) - causes LDSU to terminate or 
                   W (for WARNING) - causes LDSU to continue
      <Code>     = Error Code - See table below
      <Message>  = Error Message

The following table lists LDSU error messages with an Explanation and User Action for each message.

ATTRNOTFND, error finding ATTR 'name' in layout file for 'DN'

Explanation:
LDSU could not find an attribute returned by the LDAP server in the layout file.
User Action:
Since LDSU only asks for attributes that it knows about in the layout file to be returned, this should only happen when the LDAP server returns the attribute as another name. Most LDAP servers which allow an attribute to have multiple names, return the name the same as what it was asked for. However, other LDAP servers will return the "primary" name only even if a "secondary" name was asked for. In this case, change the layout file to use the "primary" name.

CONFIGOPEN, error opening configuration file: 'filename'

Explanation:
The configuration file could not be opened.
User Action:
Assure that 'filename' is a valid file specification for the config file and that the user has read access. LDSU requires a configuration file, named ldsu_config.dat by default. The default value can be overriden by passing the name via the do_* scripts or running the ldsu image directly and passing the name of the config file as the first argument in the ldsu command line. This error message should be supplemented by an operating system error message.

DATATRUNC, data truncated for 'DN' attribute 'field'

Explanation:
Data read from the LDAP directory for 'DN', attribute 'field' is too long to fit into the layout record.
User Action:
Increase the size of the field in the layout file record or shorten the value in the LDAP directory. Note that the length of the field in the layout file refers to the ascii representation of the value.

DELFAIL, failed to delete pre-sorted metafile: 'filename'

Explanation:
After a sort has completed, the old (pre-sorted) metafile could not be deleted.
User Action:
Check access to the file. This error message should be supplemented by an operating system error message.

DIREXIT, error exiting Directory Service

Explanation:
An error occurred while unbinding from the LDAP directory.
User Action:
This error message should be supplemented by an LDAP error message containing the reason. Consult LDAP Directory Server documentation.

DIRFETCH, error reading entry 'DN'

Explanation:
An error occurred fetching the next DN after an LDAP search call.
User Action:
Verify DN returned by LDAP server is valid.

DIRINIT, error initializing Directory Service

Explanation:
An error occurred opening or binding to the LDAP Directory server.
User Action:
Verify bind_* parameters in ldsu_config.dat. This error message should be supplemented by an LDAP error message containing the reason. Consult LDAP Directory Server documentation.

DIRREAD, error reading 'DN'

Explanation:
An error occurred during an LDAP Directory search call to read an existing record in the directory.
User Action:
Verify DN returned by LDAP server is valid. This error message should be supplemented by an LDAP error message containing the reason. Consult LDAP Directory Server documentation.

DIRREF, error reading 'REF-DN' reference record for 'DN' attribute 'ATTR'

Explanation:
An error occurred during an LDAP Directory search call to read a reference record in the directory.
User Action:
The REF-DN contained in the ATTR for DN could not be read. Verify that the ATTR value points to a valid DN. This error message should be supplemented by an LDAP error message containing the reason. Consult LDAP Directory Server documentation.

DIRSEARCH, error searching Directory Service

Explanation:
An error occurred during an LDAP Directory search call to extract records from the directory.
User Action:
Verify that LDAP server is running and that search_context, custom_filter are valid. Also verify that the LDAP server can return the number of records requested. This error message should be supplemented by an LDAP error message containing the reason. Consult LDAP Directory Server documentation.

DUPVALDIS, duplicate Value ('ATTR'='VAL') Discarded for 'DN'

Explanation:
A duplicate value in a multivalue field was removed and not entered in the LDAP directory.
User Action:
Check RDF and input file to ensure that only unique values are assigned to multiple values of the same attribute before being written to the LDAP directory.

EMPTYRDF, RDF file doesn't contain any valid records

Explanation:
An RDF file specified in the config file did not have any non-comment lines.
User Action:
Specify a valid RDF file.

EXTRALINE, 'NUM' extra line(s) in input file ignored

Explanation:
The number of records in the input file was not evenly divisible by the number of records per entry parameter (e.g. INPUT_LINES_PER_RECORD).
User Action:
Remove extra records or add records in the input file to make the number of records evenly divisible by INPUT_LINES_PER_RECORD.

FDFCREATE, error creating foreign directory file: 'FILENAME'

Explanation:
The output foreign directory file could not be created.
User Action:
Assure that 'FILENAME' is a valid file specification and that sufficient privileges and disk space exist to create the file. The filename is determined by a configuration file parameter.

FDFOPEN, error opening foreign directory file: 'FILENAME'

Explanation:
The input foreign directory file could not be read.
User Action:
Assure that 'FILENAME' is a valid file specification and that sufficient privileges exist to read the file.

FDFWRITE, error writing foreign directory file

Explanation:
Error while writing data to the output foreign directory file.
User Action:
Check for sufficient free disk space for the file.

INPTRUNC, data truncated for Field 'ATTR' in Record 'NUM'

Explanation:
In record number 'NUM' in the input file, the value for 'ATTR' was too long, as specified in the RDF file, to fit into the meta file record.
User Action:
Change the RDF and the input file to use less data for this field or increase the length of the field in the layout file.

INTERNAL_ERROR, 'MESSAGE'

Explanation:
A data inconsistency has resulting in an internal software error.
User Action:
Contact your Digital Software Support Contact as specified under the terms of your warranty.

INVLAYOUTREC, invalid schema file record: 'RECORD'

Explanation:
An invalid record in the layout file was found.
User Action:
Check the syntaxes rules for a layout record.

INVLDIF, invalid LDIF format at line 'NUM'. 'REASON'

Explanation:
An input LDIF File has a invalid or unexpected line at line 'NUM'. A further 'REASON' may be given to describe the error. (e.g. "One or more values required after changetype: add").
User Action:
Check the syntax rules for an LDIF input file.

INVRDFCOL, invalid RDF location column number: 'NUM'

Explanation:
An invalid starting column number (i.e. the middle number in N.N.N syntax) in the RDF was found.
User Action:
Verify the column number is a an integer from 1-4096 or a '*' if using EXPORT or CHANGES mode.

INVRDFCOND, invalid RDF conditional record syntax: 'RECORD'

Explanation:
An invalid RDF conditional (between ? and first :) in a record was found.
User Action:
Verify that the conditional part of the RDF record is terminated by a colon (':').

INVRDFFLD, invalid RDF location field number: 'NUM'

Explanation:
An invalid field or subfield number (i.e. the second or third number in N-N or N-N-N syntax) in the RDF was found.
User Action:
Verify the field number is a an integer from 1-4096 or a '*' if using EXPORT or CHANGES mode.

INVRDFFUNC, invalid RDF function: 'FUNCTION'

Explanation:
An unknown RDF function ($FUNCTION) was specified in the RDF file.
User Action:
Specify a valid RDF Function.

INVRDFKWD, invalid RDF keyword: 'ATTR'

Explanation:
An invalid RDF keyword ('ATTR') was found.
User Action:
Verify that the 'ATTR' is in the layout file.

INVRDFLDIF, RDF LDIF format not supported for 'KEYWORD'

Explanation:
The LDIF value for an RDF filename cannot be used for all RDF types.
User Action:
Specify a filespec for a file containing RDF statements instead of LDIF.

INVRDFLEN, invalid RDF location field length: 'NUM'

Explanation:
An invalid field length (i.e. the third number in N.N.N syntax) in the RDF was found.
User Action:
Verify the field length is a an integer from 1-4096 or a '#' if in EXPORT or CHANGES mode. Also verify that the field length plus the starting column number does not exceed 4096.

INVRDFLOC, invalid RDF location syntax in record: 'RECORD'

Explanation:
An invalid RDF location (N.N.N) syntax was found.
User Action:
Verify the location is 3 fields separated by 2 periods ('.'). Also, the fields must be integers with the exception that in the EXPORT and CHANGES mode, the second field can be a '*' and the third field can be a '#'.

INVRDFNUM, invalid RDF location record number: 'NUM'

Explanation:
An invalid RDF record number was found. (e.g. First number in N.N.N or N-N syntax).
User Action:
Verify that the record number is an integer from 1 to the INPUT_LINES_PER_RECORD parameter for this RDF.

INVRDFOPER, invalid RDF operator: 'STRING'

Explanation:
An invalid RDF operator was found.
User Action:
Specify a valid operator (e.g. ==, !=, etc.) in the RDF file.

INVRDFREC, invalid RDF record syntax: 'RECORD'

Explanation:
An invalid RDF record was found.
User Action:
Verify that the RDF record contains and action statement which is two field strings separated by an equal sign ('=').

INVRDFREF, invalid RDF reference keyword: 'DN-ATTR'->'ATTR'

Explanation:
An invalid RDF reference syntax was found.
User Action:
DN-ATTR or ATTR was not found in the Layout File. The error is also returned if this syntax is specified in IMPORT or TRANSACTION mode. It is only allowed in EXPORT or CHANGES mode.

INVRDFSTR, invalid RDF string: 'STRING'

Explanation:
An invalid RDF string was found.
User Action:
Verify that the RDF string is enclosed by double quote characters.

KEYWVALDUP, duplicate config kewyword: 'RECORD'

Explanation:
A configuration file keyword was repeated.
User Action:
Remove duplicate definitions of a keyword. A keyword may only appear once.

KEYWVALINV, invalid config record value: 'RECORD'

Explanation:
An invalid value for a configuration file keyword was found.
User Action:
Check config file (ldsu_config.dat) reference for configuration file keyword information.

KEYWVALREQ, value required for config keyword: 'RECORD'

Explanation:
A required configuration file keyword was not found or did not have a value.
User Action:
Supply a value for the required keyword.

LAYOUTOPEN, error opening schema data file: 'FILENAME'

Explanation:
The schema (layout) file could not be opened.
User Action:
Assure that 'FILENAME' is a valid file specification for the layout file and that the user has read access. The default value for the layout file (ldsu_layout.dat in the parent directory) can be changed by specifying a value for the layout_file parameter in the configuration file.

LICCHK, LDSU license has invalid checksum in: 'FILENAME'

Explanation:
For Windows NT, the LDSU license file has an invalid checksum.
User Action:
Obtain a valid license file from Digital.

LICDATE, LDSU license expires on 'DATE'

Explanation:
For Windows NT, Informational message that the LDSU license file will expire after 'DATE'
User Action:
Obtain a permanent valid license file from Digital if desired.

LICEXCEEDED, #Entries: 'NUM-FOUND' > 'MAX-NUM' - maximum # allowed

Explanation:
The LDSU license #entries quota has been exceeded.
User Action:
The LDSU license has a maximum number of entries restriction that has been exceeded. Obtain a unlimited valid license file from Digital if desired.

LICEXPIRED, LDSU license expired

Explanation:
For Windows NT, the LDSU license has expired.
User Action:
Obtain a permanent valid license file from Digital if desired.

LICINV, invalid License file format in: 'FILENAME'

Explanation:
For Windows NT, the LDSU license file has an invalid format.
User Action:
Obtain a valid license file from Digital.

LICOPEN, error opening license file: 'FILENAME'

Explanation:
For Windows NT, the LDSU license file could not be opened.
User Action:
For Windows NT, a valid license file must exist. This filename is \LDSU\LDSU_NT_LICENSE.DAT on the system drive or pointed to by the LDSU_NT_LICENSE environment variable. Obtain a valid license file from Digital if required.

LICREAD, error reading license file: 'FILENAME'

Explanation:
For Windows NT, the LDSU license file could not be read.
User Action:
Assure that LDSU has suffficient access to read the license file.

LICVERS, LDSU requires a 'VERSION' License

Explanation:
For Windows NT, the LDSU license file contains an old version.
User Action:
Obtain a valid license file from Digital for the current LDSU version.

LOGOPEN, error creating log file: 'FILENAME'

Explanation:
The log file could not be created.
User Action:
Assure that 'filename' is a valid file specification and that sufficient privileges and disk space exist to create the file. The filename is determined by the log_file configuration file parameter.

MAXADD, #add transactions: 'NUM', exceeds maximum: 'MAX'

Explanation:
LDSU determined that 'NUM' add transactions would need to be performed which exceeds the 'MAX' specified. LDSU then exited without performing any transactions.
User Action:
Perform integrity checks on input file or increase MAX_ADD_TRANSACTIONS.

MAXDELETE, #delete transactions: 'NUM', exceeds maximum: 'MAX'

Explanation:
LDSU determined that 'NUM' delete transactions would need to be performed which exceeds the 'MAX' specified. LDSU then exited without performing any transactions.
User Action:
Perform integrity checks on the input file or increase MAX_DEL_TRANSACTIONS.

MAXFAIL, maximum fail transactions reached at 'NUM' transactions

Explanation:
The program has stopped after reaching the specified number of failed Add, Modify, and Delete Transactions.
User Action:
This parameter is set by the 'max_fail_transactions' configuration file keyword in IMPORT or TRANSACTION mode.

MEMALLOC, error allocating memory: #Bytes='NUM', ID='CODE'

Explanation:
The program has stopped due to insufficient virtual memory.
User Action:
Increase any virtual memory limits for the LDSU process if possible. Reduce LDSU's virtual memory requirement by extracting less records at a time (by using smaller groups or using the big_search parameter). Also, only defining the minimum attributes in the LDSU layout file (with minimum lengths and #values) would help. This may also indicate an internal software error which should be reported to the Digital Software Support Contact.

METACREATE, error creating metafile: 'FILENAME'

Explanation:
The metafile 'FILENAME' could not be created.
User Action:
Assure that 'FILENAME' is a valid file specification and that sufficient privileges and disk space exist to create the file.

METAOPEN, error opening metafile: 'FILENAME'

Explanation:
The metafile 'FILENAME' could not be read.
User Action:
Assure that 'FILENAME' is a valid file specification and that sufficient privileges exist to read the file.

METAWRITE, error writing metafile

Explanation:
Error writing data to the metafile.
User Action:
Check for sufficient free disk space for the file.

NOSYNCHTYPE, first config keyword must be SYNCH_TYPE

Explanation:
The first non-comment line in the configuration file must assign a value to the SYNCH_TYPE keyword.
User Action:
Assure that the first non-comment line in the configuration file contains the SYNCH_TYPE keyword.

NOTOWNED, entry not owned by this instance

Explanation:
An attempt was made to modify or delete a record that did not have a matching group id and/or synch id as specified in the config file.
User Action:
Review the directory synchronization design.

PROCFAIL, error running command procedure: 'FILENAME'

Explanation:
The command procedure 'FILENAME' could not be run.
User Action:
Assure that 'FILENAME' is a valid file specification and that sufficient privileges exist to execute the file as a subprocess.

RDFOPEN, error opening RDF file: 'FILENAME'

Explanation:
The rdf file 'FILENAME' could not be opened.
User Action:
Assure that 'FILENAME' is a valid file specification and that sufficient privileges exist to read the file.

RDNNOTFND, error finding RDN 'NAME' in layout file after 'DN'

Explanation:
LDSU could not find an RDN returned by the LDAP server in the layout file. When extracting records from the LDAP Directory, LDSU dissects the DN into RDNs and stores in the record defined by the Layout File. The Layout File, therefore, must define an RDN field for all RDNs in DNs being extracted. This includes not having enough RDN values for a single RDN label defined.
User Action:
Add the RDN (or add another RDN value) to the LDSU Layout File or update the filters on the extract to not extract this record from the LDAP directory.

RENAMEFAIL, failed to rename sorted metafile 'FILENAME' to 'FILENAME

Explanation:
The sorted metafile could not be renamed to the pre-sorted metafile name.
User Action:
Assure that the 'FILENAMES' are valid file specifications and that sufficient privileges exist to rename the file.

SORTFAILED, sort failed of metafile: 'FILENAME', status = 'NUM'

Explanation:
An error sorting the metafile 'filename' occurred.
User Action:
Assure that 'FILENAME' and 'FILENAME'_SRT are valid file specifications and that sufficient privileges and disk space exist to sort the file.

VALNOTFND, error finding Value in ATTR 'ATTR' for 'DN'

Explanation:
LDSU issues this warning message when it cannot find a specific value for an attribute to remove from the LDAP directory. This can only occur when using an LDIF Changes Format Input file and an attribute value is specifed after a "delete: attribute" clause.
User Action:
Check the value was not previously removed or is the correct value.


LDSU Transaction Codes

This section lists LDSU Transaction Codes that appear in the transaction log file during an import to the LDAP directory.

Each transaction (Add, Modify, or Delete) that is performed against the LDAP directory is logged in the transaction log file (the name of which is determined by the (log_file parameter).

A transaction log file is also created during Changes Mode Export. In that case, the transaction log file is detailing which records changed in the directory that caused an Add, Modify, or Delete to be written to the Changes Mode Export Files. The status of these "transactions" will always be NORMAL and the Code will be SUCCESS.

The format of a Transaction Log Entry is:

  <C> <Status> <DN> - status=<Code>

    where:

      <C>      = A (for Add), M (for Modify) or D (for Delete)
      <Status> = NORMAL or FAILED
      <DN>     = DN (or list of key_fields if FAILED)
      <Code>   = Status Code (see below) or LDAP error

The transaction log is then followed by the list of LDAP attributes and values that were Added, Modified, or Deleted for this transaction. A modify transaction contains the before and after values for the attributes that changed.

NORMAL Status Codes

A NORMAL Status indicates the LDAP directory transaction succeeded. The Status Code can one of the following for a NORMAL Status:

SUCCESS
Transcation completed successfully
KEYFLDTRUNC
Transcation completed successfully, unique_field was truncated
KEYFLDMOD
Transcation completed successfully, unique_field was modified to be made unique

FAILED Status Codes

A FAILED Status indicates the LDAP directory transaction did NOT succeed. If the LDAP Add, Modify, or Delete failed as the result of an error returned by the LDAP directory server, the error returned by the server is displayed. If LDSU processing discovered the error before the LDAP Add, Modify, or Delete was initiated, one of the following FAILED Status Codes is displayed:

'attribute'-NOTUNIQ
The LDAP 'attribute' listed in the unique_fields parameter is not unique. (For unique field sets, the first field of the set is listed).
PRUNOTUNIQ
The gen_profs_alias_fields parameter could not create a unique field.
SNUNOTUNIQ
The gen_snads_alias_fields parameter could not create a unique field.
UNIQFAILED
An LDAP error occured while performing unique field processing. Check unique_search_context and other unique field parameters (unique_fields, gen_profs_alias_fields, gen_snads_alias_fields, make_unique_* ) for validity.
USERDEFNOTUNIQ
The make_unique parameter could not be made unique.
KEYNOTFOUND
A single record, using the DN (or key_fields and search_context), could not be found in the LDAP directory. Check values for validity. This error can also be generated if multiple records are returned for the key_fields values. If so, make sure the key_fields yields a unique record when searching the LDAP directory.



HOME NEXT PREVIOUS

Digital Copyright © Digital Equipment Corporation 1998