Server component logs

Log levels

Depending on how detailed the information about the component operation must be, you can set different log levels. They define how important and detailed the information written to the log files is. This allows you to filter and analyze the logs more efficiently.

We recommend that you use the Trace log level as the most informative one.

Log levels

Trace	The most detailed level. Logs with the Trace level contain all the information about the component operation processes, including the details of API method calls.
Debug	At this log level, the records contain the details of the component operation, significant variables, and other data that may be useful for detecting and fixing errors.
Info	At this log level, informational messages notifying about the normal functioning of the component are written. They may include such events as starting or completing processes, editing a user profile, and others.
Warn	This log level is used to write warnings and notifications about potential errors and abnormal situations. The events are not critical but require attention. The component can continue working.
Error	The log level used to write errors that led to incorrect component operation or serious problems. Logs with the Error level indicate problems that require intervention and correction.
Fatal	The least detailed log level. If this level is set, only the most critical errors and problems that lead to the immediate termination of the component or other serious consequences are written. Logs with the Fatal level usually indicate serious failures that require immediate intervention and correction.

Collect Core Server logs

Enable logging

1. Use an administrator account to open the C:\inetpub\wwwroot\am\core\Config\nlog.config file.

2. In the logger tags, set the minlevel parameter to Trace and the enabled parameter to true.

   Example

     <rules>
       <logger name="*" writeTo="f1" minlevel="Trace" enabled="true" >
         <filters>
           <when condition="equals('${logger}','metricTime')" action="Ignore" />
           <when condition="equals('${logger}','metricInfo')" action="Ignore" />
         </filters>
       </logger>
       <logger name="metricTime" writeTo="metricTimeTarget" minlevel="Trace" enabled="true" />
       <logger name="metricInfo" writeTo="metricInfoTarget" minlevel="Trace" enabled="true" />
     </rules>

3. Save the file and restart the IIS server.

Collect logs

1. Delete the existing Core Server logs in the C:\inetpub\wwwroot\am\core\Logs folder.
2. Reproduce the problem.
3. Put together an archive with the logs and send it to Axidian Technical Support along with a detailed description of the user activity and the exact time when the problem was reproduced.

Collect Management Console logs

Enable logging

1. Use an administrator account to open the C:\inetpub\wwwroot\am\mc\Config\nlog.config file.

2. In the logger tag, set the minlevel parameter to Trace and the enabled parameter to true.

   Example

   <rules>
       <logger name="*" writeTo="f1" minlevel="Trace" enabled="true" />
   </rules>

3. Save the file and restart the IIS server.

Collect logs

1. Delete the existing Management Console logs in the C:\inetpub\wwwroot\am\mc\Logs folder.
2. Reproduce the problem.
3. Put together an archive with the logs and send it to Axidian Technical Support along with a detailed description of the user activity and the exact time when the problem was reproduced.

Collect Log Server logs

Enable logging

1. Use an administrator account to open the C:\inetpub\wwwroot\ls\nlog.config file.

2. In the logger tag, set the minlevel parameter to Trace. Create the enabled parameter and set it to true.

   Example

   <rules>
       <logger name="*" minlevel="Trace" writeTo="file" enabled="true" />
   </rules>

3. Save the file and restart the IIS server.

Collect logs

1. Delete the existing Log Server logs in the C:\inetpub\wwwroot\ls\Logs folder.
2. Reproduce the problem.
3. Put together an archive with the logs and send it to Axidian Technical Support along with a detailed description of the user activity and the exact time when the problem was reproduced.

Collect Key Server logs

Enable logging

1. Use an administrator account to open the C:\inetpub\wwwroot\axidiankey\Web.Config file.

2. In the logger tag, set the minlevel parameter to Trace and the enabled parameter to true.

   Example

   <rules>
      <logger name="*" minlevel="Trace" writeTo="fileLog" enabled="true" />
   </rules>

3. Save the file and restart the IIS server.

Collect logs

1. Delete the existing Axidian Key server logs in the C:\inetpub\wwwroot\axidiankey\logs folder.
2. Reproduce the problem.
3. Put together an archive with the logs and send it to Axidian Technical Support along with a detailed description of the user activity and the exact time when the problem was reproduced.

Collect User Console logs

Enable logging

1. Use an administrator account to open the C:\inetpub\wwwroot\am\uc\Config\nlog.config file.

2. In the logger tag, set the minlevel parameter to Trace and the enabled parameter to true.

   Example

   <rules>
      <logger name="*" writeTo="f1" minlevel="Trace" enabled="true" />
   </rules>

3. Save the file and restart the IIS server.

Collect logs

1. Delete the existing User Console logs in the C:\inetpub\wwwroot\am\uc\logs folder.
2. Reproduce the problem.
3. Put together an archive with the logs and send it to Axidian Technical Support along with a detailed description of the user activity and the exact time when the problem was reproduced.

Collect Identity Provider logs

Enable logging

1. Use an administrator account to open the following file:

   • for Axidian Access 8.1.5 and higher — C:\inetpub\wwwroot\am\idp\nlog.config
   • for Axidian Access 8.1.4 and lower — C:\inetpub\wwwroot\am\idp\Config\nlog.config

2. In the logger tag, set the minlevel parameter to Trace and the enabled parameter to true.

   Example

   <rules>
      <logger name="*" writeTo="f1" minlevel="Trace" enabled="true" />
   </rules>

3. Save the file and restart the IIS server.

Collect logs

1. Delete the existing Identity Provider logs in the C:\inetpub\wwwroot\am\idp\logs folder.
2. Reproduce the problem.
3. Put together an archive with the logs and send it to Axidian Technical Support along with a detailed description of the user activity and the exact time when the problem was reproduced.

Collect Mobile Device Provisioning logs

Enable logging

1. Open the C:\inetpub\wwwroot\am\mdp\nlog.config configuration file.

2. In the rules section, set the minlevel parameter to Trace and the enabled parameter to true.

   Example

   <rules>
      <logger name="*" writeTo="f1" minlevel="Trace" enabled="true" />
   </rules>

3. Save the changes.

Collect logs

1. Delete the existing Mobile Device Provisioning logs in the C:\inetpub\wwwroot\am\mdp\logs folder.
2. Reproduce the problem.
3. Put together an archive with the logs and send it to Axidian Technical Support along with a detailed description of the user activity and the exact time when the problem was reproduced.

Collect cache server logs

Information

The cache server logs are collected on the client machines with the Windows Logon or ESSO Agent components installed.

Enable logging

1. Use an administrator account to open the C:\Program Files (x86)\Common Files\Axidian-Id\AM\CacheServer\NLog.config file for 64-bit machines or C:\Program Files\Common Files\Axidian-Id\AM\CacheServer\NLog.config for 32-bit machines.

2. In the logger tags, set the enabled parameter to true.

   Example

   <rules>
        <logger name="*" minlevel="Trace" writeTo="f1" encoding="Unicode" enabled="true" >
         <filters>
            <when condition="equals('${logger}','metricTime')" action="Ignore" />
            <when condition="equals('${logger}','metricInfo')" action="Ignore" />
         </filters>
      </logger>
     <logger name="*" minlevel="Trace" writeTo="console" encoding="Unicode" enabled="true" />
     <logger name="metricTime" writeTo="metricTimeTarget" minlevel="Trace" enabled="true" />
     <logger name="metricInfo" writeTo="metricInfoTarget" minlevel="Trace" enabled="true" />
   </rules>

3. Save the changes in the file.

Collect logs

1. Delete the existing cache server logs in the C:\Windows\System32\LogFiles\Axidian-ID Cache folder.
2. Reproduce the problem.
3. Put together an archive with the logs and send it to Axidian Technical Support along with a detailed description of the user activity and the exact time when the problem was reproduced.

Collect configuration wizard logs

Enable logging

1. Use an administrator account to open the C:\Program Files\Axidian\Wizard\NLog.config file.

2. In the logger tag, set the minlevel parameter to Trace and the enabled parameter to true.

   Example

   <rules>
      <logger name="*" writeTo="file" minlevel="Trace" enabled="true" />
   </rules>

3. Save the file and restart the configuration wizard.

Collect logs

1. Delete the existing configuration wizard logs in the C:\Program Files\Axidian\Wizard\Logs folder.
2. Reproduce the problem.
3. Put together an archive with the logs and send it to Axidian Technical Support along with a detailed description of the user activity and the exact time when the problem was reproduced.

Collect Telegram Service logs

Enable logging

1. Use an administrator account to open the C:\Program Files (x86)\Axidian-Id\Axidian-Id Telegram Service\Nlog.config file.

2. In the logger tag, set the minlevel parameter to Trace and the enabled parameter to true.

   Example

   <rules>
      <logger name="*" writeTo="f1" minlevel="Trace" encoding="Unicode" enabled="true">
      </logger>
   </rules>

3. Save the changes in the file and restart the Telegram Service.

Collect logs

1. Delete the existing Telegram Service logs in the C:\Program Files (x86)\Axidian-Id\Axidian-Id Telegram Service\Logs folder.
2. Reproduce the problem.