Seeing the error: "Connection timeout. Job canceled by scheduler." in the Mailboxes randomly. Anyone else seeing this error?
This may be caused by particularly large user mailboxes. I would recommend increasing the Polling Timeout value for this assigned application. It sounds like it's taking longer than the default value to collect all information for the respective user mailboxes.
Polling Timeout on application edit page affects regular polling of basic info (databases, files, performance counters, etc.) which is being collected every 300 seconds by default. While data for "Server mailboxes" component are collected by separate job that is executed once per 24 hours and has also separate setting for job timeout (720 minutes by default). It can be changed globally (not per application) in config file "SolarWinds\Orion\APM\SolarWinds.APM.BlackBox.Exchg.Collector.dll.config" if needed:
Restart of Orion services is needed in order to apply change of this parameter.
had to double the polling freq and timeout for it to work
Could you enable debug logging (on application edit page) and provide us with several logs so we could check which polling steps are taking that long time?
logging is enabled, where are the logs?
C:\ProgramData\Solarwinds\Logs\APM\ApplicationLogs
Did you ever find a solution to this? I'm running into a similar issue along with "Session limit exceeded for WinRM via PowerShell-Windows URL" error on Appsinight for Exchange.
The error is stating that you have exhausted the number of WinRM sessions allowed to that server. By default only 5 are allowed on each monitored host, but this limit can be increased easily by following the steps outlined in the KB article available at the link below.
i have set the sessions to 30 and still get the error: Session limit (30) exceeded for WinRM via PowerShell-Windows URL
Did you run both of the following two commands as written below on the Exchange server and wait 24 hours to see if it resolved the issue? User mailbox data is collected only once a day, so it will not update immediately.
winrm set winrm/config/winrs @{MaxConcurrentUsers="30 of concurrent users"}
winrm set winrm/config/winrs @{MaxShellsPerUser="30 of shells per user"}
yes, updated shells and sessions over a week ago and have the error as posted previously.
SAM 6.1.1 was recently released and available for download through your customer portal. I recommend upgrading and re-running the Configure Server action that's available when you edit the application for those that are already setup. If that does not resolve the issue, please open a case with support. It sounds as though permissions are the most likely cause but without diagnostics it's difficult to say for certain.
The upgrade is planned for tomorrow morning. I'll report back, fingers and eyes crossed.
upgraded to 6.1.1 and ran the wizard - session limit (30) exceeded for WinRM via PowerShell-Windows URL
What (if anything) do you have running PowerShell against that host? I recommend you try increasing the value to "50" and open a case with support. AppInsight for Exchange should work within Windows default out-of-the-box session limit. However, we have found that those environments that were leveraging PowerShell heavily prior to enabling AppInsight for Exchange have needed to increase these limits.
ticket opened - i'll post the final results
I have increased it up to 100 and ran into the same issue. I have a case open but I don't have a solution yet. I believe that in my case the server mailboxes component is timing out (job cancelled by scheduler) which causes multiple wsmprovhost processes to spawn. Once those reach the limit then the session limit error happens. My workaround has been to kill the processes when they get close to the limit.
Any news on this? As I'm testing the AppInsight for Exchange and we are seeing a similar error message.
Have you upgraded to SAM 6.1.1? Also, have you tried the solution suggested by Petr Vilem above?
I am also having the exact same issue. I have attempted the same solution as whack_a_thwack and as he stated " I believe that in my case the server mailboxes component is timing out (job cancelled by scheduler) which causes multiple wsmprovhost processes to spawn. Once those reach the limit then the session limit error happens. My workaround has been to kill the processes when they get close to the limit."
thanks for the tip, this resolve part of my issues. We have several databases some of them are huge, which will make sense to increase the timeout polling.
