Applications Systems

A timeout occurred during execution message appearing on the Application Details page for SAM

This article provides information about an error on the application or component details page which resulting to Unknown status

First published date

2/20/2020 4:06 PM

Last published date

7/17/2025 1:49 PM

Overview

This article suggests potential solutions to the error that is most often received on the Application Details page. The resolution will vary depending on the cause so investigation of the appropriate log files can provide more insight into which resolution will be the correct one.
"A timeout occurred during execution which resulted in the job being canceled."

Sample Image:
 

Product section

Server Application Monitor

Cause

If the Application is polled via Non-Agent

  • Orion Polling engine might have issues
  • Component might have permission or connectivity issues
  • SAM is over polled

If the application is polled via Agent

  • Possible the Job Engine in Agent is corrupted
  • Agent itself needs to re-install

Resolution

  • If the application is polling at increased rates or has a reduced timeout, reset these values to default. The default application polling rate is 300 seconds (5 minutes), and the default timeout is 300 seconds. Some more extensive application templates, such as AppInsight for Active Directory, are recommended to poll every 600 seconds.
  • Ensure that all SolarWinds Services are running and remain in the running status. If any services shut down unexpectedly, particularly the Orion Module Engine, it is advised to restart all SolarWinds Services. This can quickly be performed with the Orion Service Manager.
  • If the device is an Agent managed node, visit this article
  • A timeout occurred during execution which resulted in the job being cancelled error on SAM components assigned to agent servers due to installed Windows Update.
  • Also you may check the Agent's Job Engine logs and might find issues like below 
  • 2024-11-06 13:39:07,911 [STP SmartThreadPool Thread #783] ERROR SolarWinds.JobEngine.Engine.WorkerMonitor - (null)     Attempt to proces jobs on worker 30780f83-46bd-4076-8783-6f394d1d0f00 failed.
    Microsoft.Data.Sqlite.SqliteException (0x80004005): SQLite Error 13: 'database or disk is full'.

               Workaround - Repair the Job Engine files inside the Agent Server

                    Go to the Agent Server
                    1. Stop the Agent Service
                    2. Go to this path C:\ProgramData\SolarWinds\JobEngine.v2.agent\Data
                    3. Delete below files and restart the Agent service

Image_2024-11-08_09-58-46.png

                   Or you can Uninstall / Re-install the Agent

  • If the device is non-agent managed; 
    • Unmanage, the application, then manage the application once more.
    • Consider reinstalling job engine and collector services if there are many applications and nodes on the polling engine, not polling. 
    • Orion Polling Engine is Not Polling
  • Contact SolarWinds support for further investigation if these do not resolve the issue.