none
SCORCH Runbook running infinately without any logs? RRS feed

  • Question

  • Runbook triggered via an API call through Orchestrator and the runbook appears to be running with run symbol on the Runbook name , but no log is recorded and runbook is not running in real and looks like running infinately? Could you please help with this issue at the earliest as this is impacting production.

    I have done some testing and found that the issue is with "Initialize Data activity". 

    • Runbook is showing the logs and it is running fine without Initialize Data activity.
    • When Initialize Data activity is added and Parameters are passed the Runbook is not running but it is showing as running which is never ending. Please find the below screenshot. blank_log.PNG


    Regards, Naveen krishna Meruva

    Wednesday, October 16, 2019 6:22 AM

Answers

  • Hi,

    because of the log "Message: A trigger returned a resultset and the server option 'disallow results from triggers' is true.</Param>"

    Check the SQL Server Instance from Orchestrator DB:

    select value 
    FROM sys.configurations 
    WHERE name = 'disallow results from triggers'

    The Result must be 0.

    If not execute:

    exec sp_configure 'disallow results from triggers',0 
    RECONFIGURE

    Regards,

    Stefan


    More and news about System Center at stillcool.de and sc-orchestartor.eu .

    Thursday, October 17, 2019 2:43 PM
    Answerer

All replies

  • Hi,

    are any special characters for XML in the data like "<", ">", or "&" ?

    If yes, try it without special characters for XML.

    Regards,

    Stefan 


    More and news about System Center at stillcool.de and sc-orchestartor.eu .

    Wednesday, October 16, 2019 12:00 PM
    Answerer
  • Hi Stefan Horz,

    Thank you for the reply.

    Please find my investigation details below:

    I have checked it and we don't have any special characters in the XML.

    I have triggered the Runbook from Orchestrator by passing simple values like "Hello" and "World" as the input parameters but no luck. 

    I have tested the same runbook removing the initialize data activity and started it from Orchestrator which ran successfully.

    your support is highly appreciated. Please let me know if i need to check on other aspects.

    Thank you,

    Naveen Krishna Meruva 



    Regards, Naveen krishna Meruva

    Wednesday, October 16, 2019 12:07 PM
  • Hi,

    The initial Request that i started facing the issue was working fine initially for 2 months after which this issue came into picture and the problem raised. 

    Note: There were no changes taken place at either points.

    Thank you,

    Naveen Krishna Meruva.


    Regards, Naveen krishna Meruva

    Wednesday, October 16, 2019 12:20 PM
  • Hi,

    is anything in tab Events for this time?

    Or is something special in the logs then? (Default location: C:\ProgramData\Microsoft System Center 2012\Orchestrator\RunbookService.exe\Logs)

    Regards,

    Stefan


    More and news about System Center at stillcool.de and sc-orchestartor.eu .

    Wednesday, October 16, 2019 2:12 PM
    Answerer
  • Hi,

    me again :-)

    Do you get the Warning "The Runbook contains multiple starting Activities" when Check in ?

    Regards,

    Stefan


    More and news about System Center at stillcool.de and sc-orchestartor.eu .

    Wednesday, October 16, 2019 8:51 PM
    Answerer
  • Hi Stefan,

    Thanks for the reply :-)

    There is no warning like that. 

    Appreciate your support.

    Thank you,

    Naveen Krishna Meruva.


    Regards, Naveen krishna Meruva

    Thursday, October 17, 2019 7:29 AM
  • Hi Naveen Krishna Meruva,

    you#re welcome!

    Is anything in tab Events for this time?

    Or is something special in the logs then? (Default location: C:\ProgramData\Microsoft System Center 2012\Orchestrator\RunbookService.exe\Logs)

    Regards,

    Stefan


    More and news about System Center at stillcool.de and sc-orchestartor.eu .

    Thursday, October 17, 2019 9:16 AM
    Answerer
  • hi Stefan,

    Thanks again for supporting me.

    I have checked the events tab and don't see any information.

    Please find the below log that i see in the logs from the above path specified by you,  which seems to be having an issue with the parameters.. Could you please have a look and help me resolve this issue.

    2019-10-17 11:31:27 [6108] 1 Exception caught in long __stdcall WorkflowContextComAdapter::OnPolicyInstanceCreated(unsigned long,wchar_t *)
    WorkflowContextComAdapter.cpp(499):
    <Exception>
    <Type>Opalis::Exception</Type>
    <Location>
    void __cdecl StorageCallExecutor::throwChained(const class Opalis::Exception &)
    StorageCallExecutor.cpp(42)
    </Location>
    <MsgCode>SCE: ActionServerStorage call failed</MsgCode>
    <Prev><Exception>
    <Type>Opalis::Exception</Type>
    <Location>
    void __thiscall ActionServerStorageDB::createPolicyInstance(const class std::basic_string<wchar_t,struct std::char_traits<wchar_t>,class std::allocator<wchar_t> > &,const class std::basic_string<wchar_t,struct std::char_traits<wchar_t>,class std::allocator<wchar_t> > &,const __int64 &,const unsigned long)
    ActionServerStorageDB.cpp(262)
    </Location>
    <MsgCode>createPolicyInstance failed</MsgCode>
    <Params>
    <Param>{X4XXXXXX-XXFC-XXXX-XX6D-XXXXX96DE3XX}</Param>
    <Param>{BXFXXXXX-9CXX-XXXX-B9XX-XXEABXXXXXXX}</Param>
    </Params>
    <Prev><Exception>
    <Type>Opalis::Exception</Type>
    <Location>
    void __thiscall CODBDataStore::createPolicyInstance(const class std::basic_string<wchar_t,struct std::char_traits<wchar_t>,class std::allocator<wchar_t> > &,const class std::basic_string<wchar_t,struct std::char_traits<wchar_t>,class std::allocator<wchar_t> > &,const class std::basic_string<wchar_t,struct std::char_traits<wchar_t>,class std::allocator<wchar_t> > &,__int64,unsigned long)
    ODBDataStore.cpp(8136)
    </Location>
    <MsgCode>_com_error</MsgCode>
    <Params>
    <Param>IDispatch error #3092</Param>
    <Param>Error 524, Level 16, State 1, Procedure InsertRunbookInstanceInputParameters, Line 32, Message: A trigger returned a resultset and the server option 'disallow results from triggers' is true.</Param>
    <Param>-2147217900</Param>
    </Params>
    </Exception></Prev>
    </Exception></Prev>
    </Exception>



    Regards, Naveen krishna Meruva

    Thursday, October 17, 2019 11:15 AM
  • Hi,

    Are you passing any ”special characters” in the Initialize Data activity?

    Similar issue described here:

    https://systemcenternoise.wordpress.com/2016/04/05/orchestrator-runbook-running-but-not/

    Best regards,
    Leon



    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, October 17, 2019 11:48 AM
  • Hi Leon,

    Thank you for the link.

    We do not have any special characters in our parameter values. Even then we are seeing this issue. 

    I have tried passing simple strings such as "Hello" and "World" to the parameters but no luck .. 

    Even the new Runbooks are facing the same issue. Without initialize data it works perfect ... if i add initialize data is fails ... 

    Thank you,

    Naveen Krishna Meruva.


    Regards, Naveen krishna Meruva

    Thursday, October 17, 2019 12:16 PM
  • Does this issue occur with all runbooks?

    Are you facing this issue when just normally starting a runbook, for example from the Web Console? 

    Are you able to run any runbook from the Runbook Designer (this won't work when using Initialize Data as you cannot insert any parameters).


    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, October 17, 2019 12:19 PM
  • Hi Leon,

    Yes, It is happening if i am trying to start a runbook from Orchestrator console as well.

    I am able to Run the runbooks from Runbook designer that does not have initialize Data in them as we cannot pass parameters for initialize Data at this phase.

    Thank you,

    Naveen Krishna Meruva 


    Regards, Naveen krishna Meruva

    Thursday, October 17, 2019 12:58 PM
  • I would start by making sure that the Orchestrator database isn't full.

    How many runbooks do you have in your environment and how many runbook servers?

    If the Orchestrator database seems OK, have you tried simply restarting the Orchestrator services?

    The following tool is good to have some idea what is currently running in your Orchestrator environment:
    Orchestrator Health Checker


    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, October 17, 2019 1:04 PM
  • Hi Leon,

    Thank you for your support.

    I have checked the Database and it is not full and it is set to increase dynamically to accommodate Orchestrator data.

    We have only 4 Runbooks which are linked to one Master Runbook which triggers all the other. We have only one Runbook server.

    I have restarted the Orchestrator Services and have restarted the Runbook server as well.

    Thank you,

    Naveen Krishna Meruva. 


    Regards, Naveen krishna Meruva

    Thursday, October 17, 2019 1:12 PM
  • To get a better idea, could you show a screenshot of your runbooks?

    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, October 17, 2019 1:16 PM
  • Please find the below master runbook that triggers the child runbooks.

    Regards, Naveen krishna Meruva

    Thursday, October 17, 2019 2:20 PM
  • Hi,

    because of the log "Message: A trigger returned a resultset and the server option 'disallow results from triggers' is true.</Param>"

    Check the SQL Server Instance from Orchestrator DB:

    select value 
    FROM sys.configurations 
    WHERE name = 'disallow results from triggers'

    The Result must be 0.

    If not execute:

    exec sp_configure 'disallow results from triggers',0 
    RECONFIGURE

    Regards,

    Stefan


    More and news about System Center at stillcool.de and sc-orchestartor.eu .

    Thursday, October 17, 2019 2:42 PM
    Answerer
  • Hi,

    because of the log "Message: A trigger returned a resultset and the server option 'disallow results from triggers' is true.</Param>"

    Check the SQL Server Instance from Orchestrator DB:

    select value 
    FROM sys.configurations 
    WHERE name = 'disallow results from triggers'

    The Result must be 0.

    If not execute:

    exec sp_configure 'disallow results from triggers',0 
    RECONFIGURE

    Regards,

    Stefan


    More and news about System Center at stillcool.de and sc-orchestartor.eu .

    Thursday, October 17, 2019 2:43 PM
    Answerer
  • Hi Stefan,

    Thank you for your inputs.

    I will validate these steps and update you on the result.

    Thank you,

    Naveen Krishna Meruva


    Regards, Naveen krishna Meruva

    Friday, October 18, 2019 6:23 AM
  • Hi Stefan,

    Thanks for your support.

    The steps provided by you resolved the issue and I can see the Logs now.

    Thank you,

    Naveen krishna Meruva.


    Regards, Naveen krishna Meruva


    Monday, October 21, 2019 6:36 AM
  • Hi Leon,

    Thank you for your support.

    The issue is resolved now.

    Thank you,

    Naveen Krishna Meruva.


    Regards, Naveen krishna Meruva

    Monday, October 21, 2019 6:37 AM