Each message written by the driver begins with a message identifier. The text of the message follows the message identifier. A diagnostic code, meaningful to the NetIQ product support team, follows the message text.
Example message:
OBJ010I Trawl complete. aas1625
In this example, the message identifier is OBJ010I. The message text is Trawl complete. The diagnostic code is aas1625.
The last character of the message identifier represents one of the following possible severity codes:
Table D-1 Message Severity Codes
|
D |
Debugging |
|
I |
Informational |
|
W |
Warning |
|
E |
Error |
Each message identifier begins with a code of 3-5 characters associated with the driver component that generated the message. Message explanations in this reference are grouped according to these codes so you can find them quickly.
Messages beginning with AGT are issued by the Core Driver for Authentication Services.
Messages beginning with AUDA are issued by Audit Services for Authentication Services.
Messages beginning with AUDG are issued by Audit Services for general components.
Messages beginning with AUDR are issued by Audit Services to report actions taken during Receiver script processing.
Messages beginning with AXML are issued by the Core Driver during interactions with the Identity Manager engine.
Messages beginning with CFG are issued by Platform Configuration file processing.
Messages beginning with CFGA are issued during installation when migrating values from the asamcore.conf file to Driver object configuration parameters.
Messages beginning with CFGP are issued by platform configuration file processing.
Messages beginning with CRT are issued by Certificate Services.
Messages beginning with DIR are issued by the Core Driver during LDAP directory access.
Messages beginning with DOM are issued by driver components as they communicate among themselves.
Messages beginning with DRVCOM are issued by the include/exclude system.
Messages beginning with EJS are issued by Event Journal Services.
Messages beginning with HES are issued by driver components as they use HTTP to communicate.
Messages beginning with LWS are issued by the Core Driver as it functions as an HTTP server.
Messages beginning with NET are issued by driver components during verification of SSL certificates.
Messages beginning with OAP are issued by driver components when communicating among themselves.
Messages beginning with OBJ are issued by Object Services.
Messages beginning with PLS are issued by Platform Services.
Messages beginning with PRCV are issued by Platform Receivers.
Messages beginning with RDXML are issued by the embedded Remote Loader.
Messages beginning with W3LM are issued by Web Services.