Kaseya Software Management - Gathering Logs.

 

Question: When using Software Management to patch agents, perhaps a patch wasn’t able to install after trying twice. How can we get the TaskRunner/Endpoint logs for that Agent?

Resolution:

  1. Login to the VSA
  2. Navigate to "Agent > Agents > Agent Logs"
  3. Click on the machine that is having the issue
  4. On the "Diagnostic Logs > Endpoints", you will see 3 entries for Software Management. Click on the "Software Management Logs > Deployment"

  1. Click "List Logs" (this dialog can take a minute or two to load)
  2. Find the log files that are around the time of the error (there can be multiple)
  3. Click the icon under the "Get" column for that log. This will open the log (this dialog can take a minute or two to load)
  4. Copy all the text (CTRL - A) to a notepad file to save it.
  5. Do this with all the important log files.
  6. You can also get these logs manually in the location below.

 

  • Task runner logs: "C:\ProgramData\Kaseya\Log\Endpoint\Instance_serverGUID\Tasks"
  • In Windows, the Software Management logs are located in:“C:\ProgramData\Kaseya\Data\task\lumension\” folder.
  • The Endpoint logs are located in: “C:\ProgramData\Kaseya\Log\Endpoint\Instance_serverGUID\KaseyaEndpoint"

 

● On a Mac, the endpoint logs are located in "/Library/Logs/com.kaseya/Endpoint". The SM task logs are located in a folder in the Endpoint folder.

 
 
 
  1. Look in these files for the word "errorCode". The log that has this will give us more information on the error.
    1. "errorCode 20" is usually an environmental issue. The patch cannot be installed because there is something specific wrong with the patch. Google the patch and see if other people are having issues installing it.
    2. For now, report all other error codes to Jira.
  2. If you are forwarding this ticket on, you will want to get the endpoint log as it might be helpful for investigation.
    1. In the Diagnostic "Logs > Endpoints" grid, select "Kaseya Endpoint Log"
    2. Click the "Lists Logs" link
    3. Choose the log that is closest to the time of the error, without going over.
      Click the icon under the “Get” column for that log. This will open the log (this dialog can take a minute or two to load)
    4. Copy all the text (CTRL - A) to a notepad file to save it.
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Contact us