Task Log
The Task Log records task execution results. For each task, you can:
-
Confirm the operation result per device or setting item
-
Check the progress of a currently executing task
-
Suspend or resume a task in the log
A new log entry is added to the log each time you start a new task and SLNX updates the log while the task is being executed. When the task is completed, the log is updated with the final result.
Tasks are executed based on the location time of the Delegation Server. Even if you created a task to be applied to all devices, the task will be executed based on the time setting of each Delegation Server if multiple servers are located in different time zones.
There are two types of Task log: Configuration and Other. You can filter by the Log type, and the columns change respective to the type.
Configuration Task Log
- Select [System] → [Logs] → [Task Log].
- Switch the Log type to [Configuration].
You will find the following columns in the Task Log list.
Item
Description
Details Start Date
Date and time when the task started.
End Date
Date and time when the task ended.
This column is blank if the task is still on-going or pending.
Task Name
Name of the registered task.
Status Colored icon representing the job status Empty – job in progress
Green – All templates finished for all devices and all Succeeded.
Orange – Some devices were canceled or abandoned or templates Failed, Cancelled or Skipped
Red – All devices were cancelled or abandoned or Finished and all Templates Failed or Skipped
If a Standard device preference template has a “Does Not Match” for one of the attributes this will result in a failure and will display a Red or Orange Status.
# Devices
Number of devices expected for this task to run on.
This value is calculated when Run Now is clicked or when the first activity shows up for a scheduled task
Device States
Devices will be in one of these states.
Finished: Number of devices which have finished this task. The value includes both Delegation Server and DM Agent managed devices
Cancelled:Number of devices which had their task cancelled.(either from the Cancel Job button or a DM Restart) The value includes both Delegation Server and DM Agent managed devices.
Due to timing issues a device may be marked as cancelled and later reclassified if data is reported for the running this job. All devices controlled by Delegation Server may be marked as cancelled if a job is cancelled via the UI or a Delegation Server restart if the task was not finished on the particular Delegation Server.
Abandoned: Number of DM Agent devices which did not receive the task notification and did not and will not run the job. Due to timing issues, a device may be marked as abandoned and later reclassified if data is reported for running this job. The job status will be set 30 minutes after the latest time allowed for the task to run.
Started: Number of devices that have started this job but not finished. This value identifies how many devices a DS is currently processing plus the number of devices with DM Agent installed that have started processing this task. If a DM Agent controlled device, it will go into a “Started” state even if there are no threads available at this time to execute the template.
Queued: Number of devices queued for this job but not started. This value identifies how many devices a Delegation Server will process plus the number of devices with DM Agent installed that have been sent a notification to run.
Pending: Number of devices that have this task pending. The reason for pending could be caused due to a controlling Delegation Server in a later timezone (tasks run in the Delegation Server's timezone) or the controlling Delegation Server is offline and has not received the notification to run a task. DM Agent devices may also be in Pending as the notification to run scheduled tasks is controlled by the Delegation Server they are configured to communicate with and schedule could be in a future timezone.
#Templates Number of templates expected to be run Calculated based on the number of templates in task multiplied by the number of devices. Success
Number of templates that have completed successfully.
Failed
Number of templates that have failed to run.
If a Standard device preference template has a “Does Not Match” for one of the attributes this will result in a failure.
Skipped
Number of templates that were skipped.
A typical cause is incompatibility with the device.
Cancelled
Number of templates that are marked as cancelled
The cause is either a Delegation Server Restart or cancellation by the user.
-
Click a specific log to view the details at the bottom of the screen. The list will be Grouped by Device Task State and Delegation Server. If the device is controlled by a DM Agent they will be displayed with the Delegation Server shown as “SLNX DM Agent”.
You can use the filtering function if you cannot find in the list the task log you want to open.
-
Click [Filters] to display the input/select area where you can type in your search texts.
-
Enter your search key or use other filter options.
-
Click [Filter] on the right side of the input/select area, or press the Enter key.
To see the details of the task, select the task name then click [Go to Task] on the option bar.
-
-
The information available in the Result Details depends on the type of log selected.
For Configuration logs, the name of the template involved in the task is listed.
-
Click [Export CSV] to export the current log to CSV format. The log name will begin with the current date and, and will include the date and the term 'TaskLogDetail' in the filename. You can rename the log as needed.
Other Task Log
To view Task Logs categorized as Other, follow the steps below:
- Select [System] → [Logs] → [Task Log].
- Switch the Log type to [Other].
You will find the following columns in the Task Log list.
Item
Description
Start Date Displays the date and time when the task started. End Date
Displays the date and time when the task ended.
This is empty if the task is still on-going or pending.
Task Name
Displays the name of the registered task.
Category
Displays the Polling category.
Example: Counter, Other, Supplies, etc.
Event
Displays the task event details.
Progress
Displays the progress of the task.
Result
Displays the final result of the task.
Cause
Displays information such as the reason that a task failed.
Error Code
Displays an error code. For details about resolving errors, refer to .
Owner
Displays the user who registered the task.
Delegation Server
Displays the Delegation Server name.
-
Click a specific log to view the details at the bottom of the screen.
Use the filtering function if you cannot find in the list the task log you want to open. Instructions are provided above.
If you want to see the details of the task, select the task name then click (Go to Task) on the option bar. The Task will open in a new tab in the Management Console.
-
The information available in the Result Details depends on the type of log selected.
For Polling tasks, the Cause and Error Code is listed if the Result is Failed.
-
Click [Export CSV] to export the current log to CSV format. The log name will begin with the current date and, and will include the term 'TaskLog' in the filename. You can rename the log as needed.
Task Log Updates
When a task is executed with “Run Immediate” all devices associated with the task will have entries created to be displayed in the Job Detail grid. The default status for all tasks will be “Pending”.
For scheduled tasks, the initial entries for all devices will appear once a DS or DM Agent reports information on the given task. The state transition of status will be the following.
Devices Managed by a Delegation Server
Pending->Queued: when the Delegation Server controlling the device starts running the task
Queued->Started: when the Delegation Server reports activity on the job for the given task
Started->Finished: when the Delegation Server reports an end for all devices on the Delegation Server
Started->Cancelled: when the Delegation Server reports job cancelled on the Delegation Server
Pending->Abandoned: when the Delegation Server starts any scheduled jobs that would have run while down will be marked as Abandoned. There may be some entries in the Core database if you have multiple DS Servers and the task ran on a different DS. If job was a 'Run Immediate', the task will go abandoned after 1 day.
Devices Managed by DM Agent
Pending->Queued -- when Notification is queued to be sent to DM Agent
Queued->Started -- when DM Agent reports activity for the given task
Started->Finished – when the Delegation Server reports data for all templates in the task
Pending->Abandoned
Queued->Abandoned – 30 minutes after the task was to run based on the latest time zone of the Delegation Server supporting DM Agents. For instance, if a task is scheduled for 6 PM and servers existed in EST and PST time zone, the task is not abandoned until 9:30 PST.
Additional Notes on Logs
-
Item Name, Value, Value Retrieved from Device, Result, Cause, Error Code, and other information in the columns are included in the details displayed for each device. For some templates, the following columns are also displayed:
-
The Address Book template task includes the "Entry Type", "Login Name", "Entry Name", and "Mode" columns. The "Mode" column displays information about the operation such as "Add"/"Delete"/"Update" applied to the device.
-
The Address Book template and Embedded Applications template tasks include the "Mode" column, which displays information related to the operations applied to the device. The Applications task displays the "Installation" and "Uninstallation" information, and the Address Book task displays the "Add", "Delete", and "Update" information.
-
The SDK/J Platform template and Embedded Applications template tasks include columns for the template version (the software version defined in the template) and device version (the software version obtained from the device).
-
-
When an SDK/J platform update task is executed and the SDK/J platform of the target device does not support updating by RICOH Software Server, the task log displays an error indicating "Unsupported device".
-
For a firmware update task, right-clicking the task log displays the [Firmware information] tab and the detailed information about the firmware update can be confirmed.
-
If you restart SLNX or an unexpected shutdown occurs while a task is running or suspended, the task will be in the "Suspended" state after the system restarts. An entry such as "Cancelled because of system suspension." is recorded in the log.
-
In cases where an Embedded Application is installed/uninstalled as part of a task, the result "Does not match" or "Match" may incorrectly appear in the Task log.
-
For Remote Erase Memory tasks, click on the task to drill-down and view details. Note that if a Remote Erase Memory task was initiated that included targets that are managed by the Device Manager and by the DM-Agent, two tasks will be displayed. All devices managed by a DM-Agent will indicate "skipped", with a cause of "Unsupported device". Within the drill-down view, you can select a device to view details including the HDD serial numbers, erase method, repeat times, and the result. You can also run a Device Memory Erase Status report to view comprehensive details. Refer to Device Reports for details.