Monitor activities not working after Orchestrator upgrade.

Shawn Proskin 1 Reputation point
2020-10-01T12:18:41.25+00:00

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

System Center Orchestrator
System Center Orchestrator
A family of System Center products that provide an automation platform for orchestrating and integrating both Microsoft and non-Microsoft IT tools.
215 questions
0 comments No comments
{count} votes

4 answers

Sort by: Most helpful
  1. XinGuo-MSFT 14,621 Reputation points
    2020-10-02T07:41:39.053+00:00

    Is the target computer always online at that time?

    1 person found this answer helpful.
    0 comments No comments

  2. Andreas Baumgarten 97,566 Reputation points MVP
    2020-10-01T16:59:46.877+00:00

    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


  3. Andreas Baumgarten 97,566 Reputation points MVP
    2020-10-01T21:36:26.25+00:00

    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


  4. Andreas Baumgarten 97,566 Reputation points MVP
    2020-10-02T17:29:20.803+00:00

    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

    0 comments No comments