How to enable verbose logging for an RSA Authentication Agent 7.x for Windows through the registry
Originally Published: 2016-08-04
Last Modified: 2022-06-20
Article Number
Applies To
RSA Product/Service Type: Authentication Agent for Windows
RSA Version/Condition: 7.3.1[40] or later, though 7.2 and 7.1 should also work
Platform: Windows
O/S Version: Microsoft Windows Server 2012 R2, Windows Server 2008 R2, Windows 7, Windows 8, all supported versions of Windows
Issue
Tasks
Resolution
As shown in the agent interface:
In the registry, set the DWORD value to 1 to turn on logging to that specific file. You may want to enable logging for all, but typically Customer Support looks at the SIDAuthenticator log file for logon and challenge information, and the DAService log for offline authentication requests and downloads.
The registry setting for HKEY_LOCAL_MACHINE\SOFTWARE\RSA\SDTI\ACECLIENT is a remnant from the older agents, which only logged to a single file called trace.log in Agent version 7.0, and was originally called ACECLIENT.log in older versions of the agent. It is not necessary to enable logging for the trace.log file because with newer agents, there is not much useful or unique information in it. If the root cause of the issue is not identified after enabling verbose logging for the suggested values, run a test with the DWORD value set to 1.
Notes
