IMPAX 6.5.1 Application Server Knowledge Base > Configuring and administering Active Directory authentication (ADAM) > Administering ADAM and AD LDS > Configuring granular logging for critical ADAM events
By default, all ADAM logging is disabled, making it difficult to detect replication failures, ADAM process failures, and other events that can cause the Application Server to stop functioning. However, you can configure diagnostic logging for such events by modifying the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ADAM_AgfaHealthcare\Diagnostics
ADAM logging levels
Use the following table as a guide to setting the appropriate logging levels for each of the entries in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ADAM_AgfaHealthcare\Diagnostics subkey.
| Logging Level | Description |
|---|---|
| 0 (None): | Only critical events and error events are logged at this level. This is the default setting for all entries. This entry should be modified only if a problem occurs that you want to investigate. |
| 1 (Minimal) | At this setting, high-level events are recorded in the event log. Events can include one message for each major task that is performed by the service. Use this setting to start an investigation when you do not know the location of the problem. |
| 2 (Basic) | |
| 3 (Extensive) | This level records more detailed information than the lower logging levels, including the steps that are performed to complete a task. Use this setting when you have narrowed the problem down to a service or a group of categories. |
| 4 (Verbose) | |
| 5 (Internal) | When this level is specified, all events are logged and a complete service log is recorded. Use this setting when you have traced the problem to a particular category or a small set of categories. |
By default, all subkeys are set to 0 (No logging).
See also
Enabling granular event logging for AD LDS events
Topic number: 115241 Applies to: IMPAX 6.5.1 Application Server Knowledge Base |