question

ShawnProskin-0664 avatar image
0 Votes"
ShawnProskin-0664 asked AndreasBaumgarten answered

Monitor activities not working after Orchestrator upgrade.

I recently upgraded our Orchestrator environment to 2016 Update Rollup 8 (7.3.327.0). Since the upgrade, all of our "Monitor" activities are having issues. Around 5 PM daily, they stop properly monitoring. They do not receive any errors and they appear to be running and waiting but they do not trigger when needed. These include Monitor File and SharePoint Monitor List Items. Simply pressing stop then start fixes the issue.

Has anyone encountered a similar behavior?

Thanks in advance,
Shawn

msc-orchestrator
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

AndreasBaumgarten avatar image
0 Votes"
AndreasBaumgarten answered ShawnProskin-0664 edited

How many Orchestrator Runbook servers do you have in your environment?
Could you please check all "tabs" of the Runbook (Log, Log History, Audit History, Events) for additional details.
Anything in the EventLogs that might be helpful?

Regards
Andreas Baumgarten

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi Andreas,

We have 3 Runbook servers. In the Orchestrator Events tab, I see a series of warning messages every day at 5:17 PM. Screenshot below. I've also provided screenshot of the drill down into each individual message. Appears some type of network issue happens each day at that time. Not sure why the rollup update would have caused this to begin acting differently. Any thoughts?

29725-orchestrator-warnings.png


MonitorFile: System.ComponentModel.Win32Exception
29734-orchestrator-warning-1.png


MonitorFile: File monitor is waiting
29675-orchestrator-warning-2.png


0 Votes 0 ·
AndreasBaumgarten avatar image
0 Votes"
AndreasBaumgarten answered ShawnProskin-0664 commented

You are monitoring a "remote folder", a share on a different VM?
Network connection is working without any problem between the SCORCH runbook servers and the remote VM (ping, remote access in the share)?
It's always at the same time the issue is showing up?

Regards
Andreas Baumgarten

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Yes, it's always the same time of day that it's showing up. The monitored locations are always either a DFS share or a SharePoint List. Not a specific VM.

0 Votes 0 ·
XinGuo-MSFT avatar image
1 Vote"
XinGuo-MSFT answered

Is the target computer always online at that time?

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

AndreasBaumgarten avatar image
0 Votes"
AndreasBaumgarten answered

Is there anything that is happening every day at this time?

  • Maintenance stuff?

  • Restart of servers, services?

  • DNS is available all the time?

  • Network connection is available all the time?

It's possible to create runbooks for testing?
Monitor File -> Target = "a local folder" on the 3 SCORCH VMs.
Monitor File -> Target = "a share on a VM in the same vNet/subnet" of the SCORCH VMs
This way some possible reasons can be eliminated.

Regards
Andreas


5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.