ESF Manager generates various log messages regarding errors, warnings, and successful completion of infrequent activities (such as loading and initializing an ESM Module). These messages are sent to an enviroment-specific logging facility, such as the CAS Console Log and the MFDS Journal. (See saf-env.c for more information on ESF Manager environments.)
Each ESF log message has:
- A number. Each of the different messages is assigned an integer number in the range 0-8999; messages 9000-9999 are reserved for customer use. Message numbers are more or less grouped by ESF Manager component:
- A level: informational, warning, error, or critical (fatal error), indicated by the letters "I", "W", "E", and "C".
- Message text. ESF Manager message text is retrieved from a message catalog for internationalization purposes; if a catalog for the current language is not available, a default English message is used.
- For some messages, substitution parameters are replaced with event- specific details.
Currently no messages in this class have been defined.
- 103W Admin "type" request failed: "value"
- An ESF Admin request of the given type failed, returning error code value.
- 104W Update ("type") request failed: "value"
- An ESF Update request of the given type failed, returning error code value.
- 105W ESM Module number ("name") returned error code value ("description") from Update (type)
- The ESM Module name (at position number in the stack, if multiple modules are configured) returned error code value from an Update operation for a cached update. The type is either "single update" or "refresh all", indicating whether the ESM Module was asked to refresh its private data associated with one update, or clear all of its privately cached security information. See External Administrative Update Notification for more information.
- 110E ESM Module number ("name") returned error code value ("description") from Verify
- The ESM Module name (at position number in the stack, if multiple modules are configured) returned error code value from a Verify (authenticate user) operation. This constitutes a Fail result for the Verify request.
- 111E ESM Module number ("name") returned error code value ("description") from Auth
- The ESM Module name (at position number in the stack, if multiple modules are configured) returned error code value from an Auth (authorize resource access) operation.
- 112E ESM Module number ("name") returned error code value ("description") from XAuth
- The ESM Module name (at position number in the stack, if multiple modules are configured) returned error code value from an Xauth (authorize resource access) operation.
- 113E ESM Module number ("name") returned error code value ("description") from Admin
- The ESM Module name (at position number in the stack, if multiple modules are configured) returned error code value from an Admin (administrative action) operation.
- 114E ESM Module number ("name") returned error code value ("description") from Update
- The ESM Module name (at position number in the stack, if multiple modules are configured) returned error code value from an Update (update notification) operation.
- 200I Loaded ESM Module "name"
- The binary file name has been loaded as an ESM Module and initialized.
- 201C Unable to load ESM Module "name": reason
- The ESM Module in the binary file name could not be loaded; reason is a numeric reason code.
- 202C ESM Module "name" returned invalid procedure table
- The ESM module name returned an invalid result when its initial entry point was called.
- 203C ESM Module "name" initialization failed
- The ESM Module name returned an error from its initialization procedure.
- 204W ESM Module index returned error code value from Exit
- The ESM Module (indicated by its position in the ESM Module list, index) returned a non-zero value from its Exit procedure.
- 301W Unable to open log file "name": ("value") description
- ESF was unable to open the log file "name". The value is the error code and description is a short description. (The file is specified by the
MF_SAFLOG environment variable. This function only applies to standalone utilities that use ESF, and not to main ES components.)
- 320C CAS support function "name" is not available
- The required CAS support function name is not available to ESF Manager, possibly due to a version mismatch between modules or a resource constraint. This is a fatal error.
- 321E Unable to allocate ACEE (error code)
- ESF Manager was unable to allocate an ACEE structure, which is required for user verification. code is the error returned by the environment's ACEE allocation function.
- 322E Unable to allocate named shared memory (error code)
- ESF Manager was unable to allocate a named shared memory area, either for its own use or to satisfy a request from an ESM Module. code is the error returned by the environment's shared-memory allocation function.
Currently no messages in this class have been defined.
Currently no messages in this class have been defined.
- 601C Auditing subsystem startup failed: ("value") description
- ESF was unable to connect to the auditing subsystem. This is a critical failure (if auditing is enabled). value is the return code from auditing startup and description is a short description of the problem.
- 602C Auditing: cobaudit_event failed: ("value") description
- The auditing subsystem failed to audit a security event. This is a critical failure (if auditing is enabled). value is the return code from auditing startup and description is a short description of the problem.
See the documentation for your ESM Module for information on its log messages. (Documentation for the MLDAP ESM Module can be found here.)
These messages will not normally be logged by released products. They may appear in Early-Adopter releases. If you receive a message in this range, contact Micro Focus Technical Support for more information.