Use the Control Room diagnostics
utility to gather the Control Room logs, event viewer logs
and system information for a specified duration and troubleshoot any Control Room related issues.
About this task
Because the diagnostic utility is designed for On-Premises Windows environment only, ensure that the Control Room is installed on the machine. To gather
the required information, you must execute the utility independently on each node of
the Control Room cluster.
Procedure
-
Open the Windows Command Prompt with
elevated privileges (Run as administrator).
-
Navigate to the Control Room installation
path.
Default installation path for
Control Room
is:
C:\Program Files\Automation Anywhere\Automation360
-
Run the Control Room diagnostic utility using
the following command:
"C:\Program Files\Automation Anywhere\Automation360\jdk11\bin\java" -jar crdiagnosticutility.jar [OPTIONS]
Note: The Java Development Kit (JDK) is bundled with
the
Control Room and the default location
is:
"C:\Program Files\Automation Anywhere\Automation360\jdk11\bin\java"
-
The following table describes the option for performing the diagnostic
check:
| Option |
Description |
| -collectLogs |
By capturing multiple logs for the Control Room, you reduce the
turnaround time for collecting information on issues. The
logs are collected as a zip file on the machine where the
utility is being run. The logs are saved
in the configured log directory of Control Room. For example, the default
log directory is C:\ProgramData\AutomationAnywhere\Logs\.
The compressed file will be created in C:\ProgramData\AutomationAnywhere\Logs\CR_logs_<datetimestamp>.zip. Review the following considerations on
using the Control Room
diagnostic utility:
- To capture Windows logs for security events, run
the utility with administrative or elevated
privileges. An alert is displayed if you run the
utility without elevated privileges.
- To save the storage space, delete the zip file
after debugging.
|