Remote Collector is not forwarding logs
Debugging must be performed on the D-Srv.
Login to the D-Srv
Click Start > Programs > Administrative Tools > WinSSHD Control Panel
Click Setting > Edit/view setting
Expand Server, click Logging, check Log to textual log file box. Select logging level to ?Errors, Warnings, Info, Trace, Dump?
Click OK. Click Close.
Restart winsshd service.
A new folder called Logs will be created under e:\nic\version\node\winsshd.
Login to the RC and stop the Scheduler then check and kill any forwarder processes within task manager.
Then still on the RC, open cmd prompt and run pi_ls_forwarder -v from the envision \bin directory, let it run for a few minutes, stop it.
Then start the Scheduler service back up.
The log file will reside under e:\nic\version\node\winsshd\Logs folder.
Related Articles
How to enable DEBUG logging in RSA Identity Governance and Lifecycle Number of Views Enable RADIUS debug/verbose logs with all versions of RSA Authentication Manager 8.x Number of Views How to enable DEBUG logging to show SQL queries generated by RSA Identity Governance & Lifecycle Number of Views How to enable debug logs in RSA Web Threat Detection Number of Views How to enable SSL debug when using the WebSphere application server with RSA Identity Governance & Lifecycle Number of Views
Trending Articles
RSA Authentication Manager 8.9 Release Notes (January 2026) Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings. RSA Authentication Manager Upgrade Process How to delete old or pending certificate signing requests for RSA Authentication Manager console or virtual host replaceme…
