Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > AppInsight for Exchange - A timeout occurred during execution which resulted in the job being canceled

AppInsight for Exchange - A timeout occurred during execution which resulted in the job being canceled

Updated 10/25/2017

Overview

When attempting to poll AppInsight for Exchange the configuration and testing is successful but the following error appears after some time of trying to poll.

A timeout occurred during execution which resulted in the job being canceled.

 

In the Debug files, it's hanging on collecting the File and Transaction Log Directory information.


DateTime [Cx] DEBUG SolarWinds.APM.Probes.ProbeExecutors.ProbeHierarchyBatchExecutor - 
    Component probe starting: JobContext - ComponentId: 476469, 
    ComponentName: Database File And Transaction Logs Dir Info
DateTime [Cx] DEBUG SolarWinds.APM.Probes.ProbeExecutors.ProbeHierarchyBatchExecutor - 
    probeParameters:0 resultContext.Inputs:1
DateTime [Cx] DEBUG SolarWinds.APM.Probes.ProbeBase`1 - Remaining Time: 191.6086855 sec.
DateTime [Cx] DEBUG SolarWinds.APM.Probes.Script.PowerShellScriptHelper - Processing 
macros: 3 variables processed
DateTime - Job timeout detected

Environment

  • Server and Application Monitor v6.1+

 

Cause 

The cause of this issue is large directories which store the Mailbox log files and information. When attempting to browse to the directories in Windows Explorer it takes a long time to list all the files.

 

Resolution

If the directory lists its contents in a reasonable time increasing the timeout on AppInsight for Exchange will allow it to complete.

 

Also, on the Exchange side, ensure that Circular Logging is enabled if allowed by the customer's policies as this can cause large file buildups in Exchange.

 

A Workaround which we can try from an Application Point of view to negotiate larger Exchange enviorments is to tweak the WinRm Session Limits:

 

  1. Login to the Monitored Exchange Server
  2. Open the command prompt in Run As Administrator context.
  3. Type winrm get winrm/config/winrs to get your current configuration.

 

To increase the limit of any of these settings, it can also be done using the winrm command.

To change the number of concurrent users and shells per user, use the following commands:

winrm set winrm/config/winrs @{MaxConcurrentUsers="30"}
winrm set winrm/config/winrs @{MaxShellsPerUser="20"}
winrm set winrm/config/winrs @{MaxMemoryPerShellMB="2048"}

 

Note: This command must be executed on the system you are connecting to remotely using WinRM/WinRS. Once applied this setting is permanent until changed by an administrator.

 

 

 

Last modified

Tags

Classifications

Public
/*]]>*/