Jump to content

Ricky

Hornbill Product Specialists
  • Content Count

    193
  • Joined

  • Last visited

  • Days Won

    1

Ricky last won the day on April 14

Ricky had the most liked content!

Community Reputation

16 Good

About Ricky

  • Rank
    Senior Member

Recent Profile Visitors

800 profile views
  1. Hi @AndyHillthe development team is currently looking into providing a feature to resume a suspended process. We will post an update as soon as we have further details. Regards, Ricky
  2. Hi @AndyGilly, Apologies for the delay in responding. I am still waiting for an update on this issue. I know that we have been able to identify the root cause of the problem and that the fix will be within the SIS. A release is due soon; however, I am still waiting for confirmation of the timeframe as I believe dependencies are holding back the release. I hope to get more information and hopefully an ETA later this week, and I will update you accordingly. Regards, Ricky
  3. @Mark HarveyThank you for your post, this type of action would be better suited using the Hornbill APIs to create the requests. The API calls can be scheduled in bulk using our Hornbill API Scheduler tool. The following link will provide further details of how the tool is used and where to get access to it: https://wiki.hornbill.com/index.php?title=API_Scheduler Regards, Ricky
  4. @AndyGillyI can see that the Manage Executed Processes feature does not allow resuming a process after failure. I have asked the Dev team to look into the issue and if it is possible to implement the feature. The interface used for both BPM and Runbooks; however, Resuming a process is not supported for Runbooks. I will get back to you as soon as I get a reply. Ricky
  5. Hi @AndyGilly, there a feature to view all Runbook process and is accessible via the following button: Ricky
  6. Hi @AndyGilly, I will chat with the dev team and get an update on any progress. Ricky
  7. @AndyGillyThanks for the update, the only thing i can see that may cause this the process not to set it, may be to do with IT Automation node setting the Policy not waiting for a response before the next node is executed. The execution policy can only be modified by ITOM via an IT Automation, so would not have been modified unless specifically called, and therefore may have been changed by some other mechanism such as a Group Policy setting. Ricky
  8. @AndyGilly Ignore the above comment as it is mis-leading, i should of written it as follows: There looks to be no issue with the execution, the only issue maybe where you are entering the Get-ExecutionPolicy to check the change. The package is built to use the native version of PowerShell and thus the change should be seen in the native console. This can be identified in the logs by the entry: 2021-04-07 13:50:50Z Target platform: win3264 2021-04-07 13:50:50Z Using the native variant of PowerShell 2021-04-07 13:50:50Z Using executable C:\Windows\system32/WindowsPowerShell\v1.0
  9. @AndyGilly There looks to be no issue with the execution, the only issue maybe where you are entering the Get-ExecutionPolicy to check the change. The package is built to use the 32 bit (x86) version of PowerShell and thus the change would not be seen in the 64bit console. This can be identified in the logs by the entry "2021-04-07 13:50:50Z Target platform: win3264". I am unable to get it to fail at my end and the output you have provided in the logs looks as if all was working as expected. When you set the Policy which version of PowerShell console are you setting it in PowerShel
  10. @AndyGilly We have updated the ECM package to provide enhanced error messaging (https://community.hornbill.com/topic/20615-new-update-hornbill-itom-content-pack-32/) this should help with any issues going forward. With regards to the Execution policy can you supply the the full debug log and Monitor for the Set-Execution Policy operation? Would also be useful to get the output of following command on the target device Thanks Ricky
  11. @AndyGilly Thanks for the update, I will take a look and see what I can come up with, and get back to you. Thanks Ricky
  12. @AndyGillyCan you also confirm that you are able to manually change to the the drive on the target device using: Set-Location <dirve-name>: This will confirm the package is being executed on the correct device, and I will also get back to the dev team who are currently investigating the error message with your update. Thanks Ricky
  13. @AndyGillyCan you check if the SiteId is correct as it is case sensitive? Regards Ricky
  14. Issue found within the ITOM Job Processing CLIXML parsing, used to produce filtered Console output, causing return parameters to be ignored. A workaround is available, which can be implemented by turning off the parser within Hornbill Administration Settings:
  15. Hi @AndyGilly, we have now released a Direct email feature that can be utilised within a Hornbill Business Process including ITOM Runbooks: Release Announcement: This feature is accessible via the Hornbill Automation node: Regards, Ricky
×
×
  • Create New...