Share via

MS Orchestrator runbook failure with error message: Error communicating with OpExec service on ...

AnneW 86 Reputation points
2024-12-02T22:08:41.97+00:00

We are using MS orchestrator to automate jobs. There are a bunch of runbooks and scheduled to run nightly. recently we found one job failed nightly starting last Monday. But the job is to run a .bat file on an oracle server that also runs a powershell that triggers a sqlplus to run oracle script. We can see from powershell log it logged into the Oracle server and executed the sql code, and disconnected from the server successfully. But the step of the the runbook somehow shows the step failed instead of succeeded. This is a child runbook the master runbook calls, then the whole master job failed, The error is Error communicating with OpExec service on server, the job has been running fine without problem, but it failed since last week, could not find what is wrong. Any ideas? thanks

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.

0 comments

4 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. AnneW 86 Reputation points
    2024-12-03T19:27:33.03+00:00

    C:\ExtractScripts\Scripts>exit /b 0     Obtaining the remote execution status... Exception Error communicating with OpExec service on myServer: Disconnecting from myServer... Disconnected.

    This shows our script runs error, but opExec service returns failure.

    Was this answer helpful?

    0 comments
  2. AnneW 86 Reputation points
    2024-12-03T19:26:03.47+00:00

    and we know the job succeed see log :
    C:\ExtractScripts\Scripts>exit /b 0     Obtaining the remote execution status... Exception Error communicating with OpExec service on myServer: Disconnecting from Server... Disconnected

    Was this answer helpful?

    0 comments
  3. AnneW 86 Reputation points
    2024-12-03T18:50:26.7733333+00:00

    Correct, we did ask and there is no change in Oracle server and Orchestrator server we are aware of.

    And we see from job run log, it completed and disconnect oracle database then report Error communicating with OpExec service on myServer.

    I changed the job to another time slot, it succeeded last night, but the other simple 1-minute runbook job also reported failure even it completed the job, but reported Error communicating with OpExec service on myServer.
    It looks like a false alarm, but why we got this error.

    I also see in event viewer oracle server log there are some error messages like below: this does appear more in last week also in the time slot job runs. what does this mean, we don't have interactive service, all the jobs are PowerShell or bat jobs.
    The Orchestrator Run Program Service service is marked as an interactive service.  However, the system is configured to not allow interactive services.  This service may not function properly.

    this error message shows at the same time when the job marked failure.

    Was this answer helpful?

    0 comments
  4. XinGuo-MSFT 22,271 Reputation points
    2024-12-03T09:08:11.3466667+00:00

    Hi,

    The key point is that we need to figure out why the child runbook shows that the step failed instead of succeeding.

    What changes have we made recently in Oracle server or Orchestrator server.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.