Search: log-message

/ logs/ ls -l 2.1.4 Step 4: Configure Tomcat service running 1. Get Java Installation folder sudo

. Change owner and group ownership to logs folder. sudo chown -R tomcat /opt/tomcat/logs sudo chgrp -R tomcat /opt/tomcat/logs 2.2. Install ActiveMQ 2.2.1. Step 1: Extract installation file 1.   Move

conf sudo chown -R tomcat webapps/ work/ temp/ logs/ ls -l [[image:image-20230728180918-5.png

="331" width="838"]] ~11. Change owner and group ownership to logs folder. sudo chown -R tomcat /opt/tomcat/logs sudo chgrp -R tomcat /opt/tomcat/logs == (% style="color:#000000" %)**2.2. Install ActiveMQ

installer version Logs Check the following log files. File name Target directory Descriptions msiexec.log C:\ProgramData\akaBot\Logs\ No error relates to Auto-logon BotService.log C:\ProgramData\akaBot\Logs\ No error relates to Auto-logon AutoLogonChecker.log C:\ProgramData\akaBot\Logs\ No error relates to Auto

\|Must be equal to akaBot installer version **Logs** Check the following log files. |=File name|=Target directory|=Descriptions |msiexec.log|C:\ProgramData\akaBot\Logs\|No error relates to Auto-logon |BotService.log|C:\ProgramData\akaBot\Logs\|No error relates to Auto-logon |AutoLogonChecker.log|C:\ProgramData

C:\Windows\System32\ Must be equal to akaBot installer version Logs Check the following log files. File name Target directory Descriptions msiexec.log C:\ProgramData\akaBot\Logs\ No error relate to Auto-logon BotService.log C:\ProgramData\akaBot\Logs\ No error relate to Auto-logon AutoLogonChecker.log C

to akaBot installer version **Logs** Check the following log files. |=File name|=Target directory|=Descriptions |msiexec.log|C:\ProgramData\akaBot\Logs\|No error relate to Auto-logon |BotService.log|C:\ProgramData\akaBot\Logs\|No error relate to Auto-logon |AutoLogonChecker.log|C:\ProgramData\akaBot\Logs

on. Machine Username The username used to log in to the Agent machine Type The type of Agent. This can be only

, S3: To view the Agent’s logs from the Agent Details page, click the Log tab next to the Task tab to switch the view. You can also Export Log for further investigation by clicking the Export Log option

**|The username used to log in to the Agent machine |**Type**|The type of Agent. This can be only Development

, [[image:image-20230425155109-29.png]] S3: To view the Agent’s logs from the Agent Details page, click the **Log

also Export Log for further investigation by clicking the **Export Log** option next to the **Filter

of all agent’s tasks at the bottom of the Details page, S3: To view the Agent’s logs from the Agent Details page, click the Log tab next to the Task tab to switch the view. You can also Export Log for further investigation by clicking the Export Log option next to the Filter button. You can export all Logs

: To view the Agent’s logs from the Agent Details page, click the Log tab next to the Task tab to switch the view. [[image:image-20230308181334-29.png]] You can also Export Log for further investigation by clicking the **Export Log** option next to the **Filter** button. You can export all Logs or specific

Workflow as below: No Column/Label Description 1 Action Available actions to manage the Log of said

a confirmation message for you to confirm.

]] |=No|=Column/Label|=Description |1|Action|((( Available actions to manage the Log of said Workflow. Includes

message for you to confirm. [[image:image-20221028101740-21.png]] ))) {{velocity

an organization unit: Agent group Agents Workflows Tasks Schedules Packages Repository Assets Queue Logs Report

* Packages Repository * Assets * Queue * Logs * Report ! Statistics are produced for each organizational

to the Organization Unit name on the Organization Unit page.Type your warning message here. {{/warning

/Add%20Log%20Fields/">Add Log Fields</a> <a href="/bin/view/Activities/%5B1%5D%20Core

/Get%20Exchange%20Email%20Messages/">Get Exchange Email Messages</a> <a href="/bin/view/Activities/Exchange/Activities/Move%20Message%20To%20Another%20Folder/">Move Message To Another Folder