Ricky

Hi Andy, apologies as I have only just been notified about this post. The first place to look will be the SIS log file EspSisService.log located in the folder: C:\ProgramData\Hornbill\Site Integration Server\log The following is an extract showing a job being processed by the SIS, if you can post yours we should be able to work out where the issue is. 2021-01-26 12:18:17Z [INFO]:[GENERAL]:[4452] Executing package job: 2073 2021-01-26 12:18:17Z [INFO]:[GENERAL]:[4452] Executer filename: C:\Program Files\Hornbill\Site Integration Server\exec\win\x64\EspSisExec.exe 2021-01-26 12:18:17Z [INFO]:[GENERAL]:[4452] Package filename: C:\ProgramData\Hornbill\Site Integration Server\packages\37fe560b5772fe22073a78dca8dec234bcb34ae2.pkg 2021-01-26 12:18:17Z [INFO]:[GENERAL]:[4452] Target: W2K12R2-DC01 2021-01-26 12:18:17Z [INFO]:[GENERAL]:[4452] Protocol: 1 2021-01-26 12:18:17Z [INFO]:[GENERAL]:[4452] Package: BooleanPSParam 2021-01-26 12:18:17Z [INFO]:[GENERAL]:[4452] Operation: Demo Powershell 2021-01-26 12:18:17Z [INFO]:[GENERAL]:[4452] Callback context: zEmgs7Gp31vYr23mB4kYjIXvYis_uEMG51ke4_KbXAx8MWKJORKBIh9faqQ8-6QZ9gAStYQpeveDemPQAVNc43aDJVxmZ54Q3iFyyx_-eGg2B4kYd8aN9UwdIKxCyLmUgroE4Dl2qS--Mas8fiwjNWiK216nZ0Vgml1syioI0qY6kC-xBeP5KqDD_TwJxCsdG7E0x44ij97ltLQZ_Vtqwgyf96c_i2hAUP4h64oTVEv4OXGj93-4FM1NmABnwazyMeL4w6NVtbBCFe0J8QE7RIHjohf7gECEZ3yD5gD9qKRRaZxMpWtwyFkDFPQZOqUiLfuHWMQHe0xwdYrgwIsDR4GmPbwHjK0dbzSXt2arP-veAnD5QzNvEwHT808S15PHP6jSULvdGywGePC8bchuk26RyiyMQCU11dw8WWd2Q91ZMwO3MHF5eZmiCiPFSA5fV_eynbE3zVS4xW8neMjBpcj6UrO8hhHlnx6UdIoLO4_8qAFG 2021-01-26 12:18:17Z [INFO]:[GENERAL]:[4452] Timeout: 60 2021-01-26 12:18:17Z [INFO]:[GENERAL]:[4452] Encoded parameters: okpfR9fnZEwMovC0_-G_42TYE2Mo5b75u0qQUTTgsa6mx5GSj7HFkit8--pAYT5phA0eaL4rLSF7-3SCmrveB88s8xKb5-G-lMfX7ymR-ygH50E5HY2v9bygyA-LIlOxyAIid43gRBk-81GLXCuCY3qyIoiMXfHCWuJvP9n2zmHnVA-8IlLvO53I_FJsykBKJYlM7_1Rt944Py3RmwFfMax8YWgw4zF6TrTG2QVh3e85AaAGyoww-yjxDmbPSxzjmavAr2c3WESNzZLNUx6fmPmq4XDXjrtIEtoKNcabyWciQmT31mAwcFcBPp_4Y4JgfpYpryE9no91PZmgUnzPK54kJ93yt3BOB_vH9E3N8yYy2PweSzZSuUQSGuAxJYq-3WDcH7ScVPX5QmLosR58ylpohabfrd_qNIyndMeTDPreq2PdUwU-JDYDeDniRiYwSiAOeE__Iwz6Bqzd_vSwPaNMhVKWaDv4U7OfaZ8uXOj9XJD6ggd- 2021-01-26 12:18:17Z [INFO]:[GENERAL]:[4452] Encoded credentials: RMFrQFMVdXvfl5MRvBNLUrH8QwNHF3CeioK1TGCfUO-TsWEwS2TMFuHY3OOAs3M7Mgq8vdFJC19IEKGpWoIEkcw2JDIsnFwU9TT61iUm-Ro 2021-01-26 12:18:17Z [INFO]:[GENERAL]:[4452] Impersonating Administrator@hornbill.qa against W2K12R2-DC01. 2021-01-26 12:18:18Z [INFO]:[GENERAL]:[4452] Running command line: "C:\Windows\TEMP\Hornbill\SIS Package Processor\4edc654c-3770-480c-b0fe-9a9780aec6e6\EspSisExec.exe" -target "W2K12R2-DC01" -mode package -packageFilename "C:\Windows\TEMP\Hornbill\SIS Package Processor\4edc654c-3770-480c-b0fe-9a9780aec6e6\37fe560b5772fe22073a78dca8dec234bcb34ae2.pkg" -xmlResultFilename "C:\Windows\TEMP\Hornbill\SIS Package Processor\4edc654c-3770-480c-b0fe-9a9780aec6e6\Result.xml" -operation "Demo Powershell" -callbackContext "zEmgs7Gp31vYr23mB4kYjIXvYis_uEMG51ke4_KbXAx8MWKJORKBIh9faqQ8-6QZ9gAStYQpeveDemPQAVNc43aDJVxmZ54Q3iFyyx_-eGg2B4kYd8aN9UwdIKxCyLmUgroE4Dl2qS--Mas8fiwjNWiK216nZ0Vgml1syioI0qY6kC-xBeP5KqDD_TwJxCsdG7E0x44ij97ltLQZ_Vtqwgyf96c_i2hAUP4h64oTVEv4OXGj93-4FM1NmABnwazyMeL4w6NVtbBCFe0J8QE7RIHjohf7gECEZ3yD5gD9qKRRaZxMpWtwyFkDFPQZOqUiLfuHWMQHe0xwdYrgwIsDR4GmPbwHjK0dbzSXt2arP-veAnD5QzNvEwHT808S15PHP6jSULvdGywGePC8bchuk26RyiyMQCU11dw8WWd2Q91ZMwO3MHF5eZmiCiPFSA5fV_eynbE3zVS4xW8neMjBpcj6UrO8hhHlnx6UdIoLO4_8qAFG" -timeout 60 -encodedParameters "okpfR9fnZEwMovC0_-G_42TYE2Mo5b75u0qQUTTgsa6mx5GSj7HFkit8--pAYT5phA0eaL4rLSF7-3SCmrveB88s8xKb5-G-lMfX7ymR-ygH50E5HY2v9bygyA-LIlOxyAIid43gRBk-81GLXCuCY3qyIoiMXfHCWuJvP9n2zmHnVA-8IlLvO53I_FJsykBKJYlM7_1Rt944Py3RmwFfMax8YWgw4zF6TrTG2QVh3e85AaAGyoww-yjxDmbPSxzjmavAr2c3WESNzZLNUx6fmPmq4XDXjrtIEtoKNcabyWciQmT31mAwcFcBPp_4Y4JgfpYpryE9no91PZmgUnzPK54kJ93yt3BOB_vH9E3N8yYy2PweSzZSuUQSGuAxJYq-3WDcH7ScVPX5QmLosR58ylpohabfrd_qNIyndMeTDPreq2PdUwU-JDYDeDniRiYwSiAOeE__Iwz6Bqzd_vSwPaNMhVKWaDv4U7OfaZ8uXOj9XJD6ggd-" -encodedCredentials "RMFrQFMVdXvfl5MRvBNLUrH8QwNHF3CeioK1TGCfUO-TsWEwS2TMFuHY3OOAs3M7Mgq8vdFJC19IEKGpWoIEkcw2JDIsnFwU9TT61iUm-Ro" -logLinePrefix "P" 2021-01-26 12:18:23Z [INFO]:[GENERAL]:[4452] XML Result document: <?xml version="1.0" encoding="utf-8"?> | <result> | <process> | <success>Yes</success> | <exit_code>0</exit_code> | <result>Success</result> | </process> | <processing> | <output> | #&lt; CLIXML | {{SISJobOutputParameterStart:ParamA}}test{{SISJobOutputParameterEnd}} | {{SISJobOutputParameterStart:ParamB}}10{{SISJobOutputParameterEnd}} | {{SISJobOutputParameterStart:ParamC}}True{{SISJobOutputParameterEnd}} | &lt;Objs Version=&quot;1.1.0.1&quot; xmlns=&quot;http://schemas.microsoft.com/powershell/2004/04&quot;&gt;&lt;Obj S=&quot;progress&quot; RefId=&quot;0&quot;&gt;&lt;TN RefId=&quot;0&quot;&gt;&lt;T&gt;System.Management.Automation.PSCustomObject&lt;/T&gt;&lt;T&gt;System.Object&lt;/T&gt;&lt;/TN&gt;&lt;MS&gt;&lt;I64 N=&quot;SourceId&quot;&gt;1&lt;/I64&gt;&lt;PR N=&quot;Record&quot;&gt;&lt;AV&gt;Preparing modules for first use.&lt;/AV&gt;&lt;AI&gt;0&lt;/AI&gt;&lt;Nil /&gt;&lt;PI&gt;-1&lt;/PI&gt;&lt;PC&gt;-1&lt;/PC&gt;&lt;T&gt;Completed&lt;/T&gt;&lt;SR&gt;-1&lt;/SR&gt;&lt;SD&gt; &lt;/SD&gt;&lt;/PR&gt;&lt;/MS&gt;&lt;/Obj&gt;&lt;/Objs&gt; | </output> | </processing> | <logging> | <processing> | 2021-01-26 12:18:18Z [DEBUG]:[GENERAL]:[5620] Log filename: C:\Windows\TEMP\Hornbill\SIS Package Processor\4edc654c-3770-480c-b0fe-9a9780aec6e6\Processing.log | 2021-01-26 12:18:18Z [DEBUG]:[GENERAL]:[5620] Local computer name: W2K12R2-DC01 | 2021-01-26 12:18:18Z [NOTICE]:[GENERAL]:[5620] Package filename: C:\Windows\TEMP\Hornbill\SIS Package Processor\4edc654c-3770-480c-b0fe-9a9780aec6e6\37fe560b5772fe22073a78dca8dec234bcb34ae2.pkg | 2021-01-26 12:18:18Z [NOTICE]:[GENERAL]:[5620] Operation: Demo Powershell | 2021-01-26 12:18:18Z [DEBUG]:[GENERAL]:[5620] XML result filename: C:\Windows\TEMP\Hornbill\SIS Package Processor\4edc654c-3770-480c-b0fe-9a9780aec6e6\Result.xml | 2021-01-26 12:18:18Z [DEBUG]:[GENERAL]:[5620] Timeout: 60 | 2021-01-26 12:18:18Z [DEBUG]:[GENERAL]:[5620] Encoded parameters: okpfR9fnZEwMovC0_-G_42TYE2Mo5b75u0qQUTTgsa6mx5GSj7HFkit8--pAYT5phA0eaL4rLSF7-3SCmrveB88s8xKb5-G-lMfX7ymR-ygH50E5HY2v9bygyA-LIlOxyAIid43gRBk-81GLXCuCY3qyIoiMXfHCWuJvP9n2zmHnVA-8IlLvO53I_FJsykBKJYlM7_1Rt944Py3RmwFfMax8YWgw4zF6TrTG2QVh3e85AaAGyoww-yjxDmbPSxzjmavAr2c3WESNzZLNUx6fmPmq4XDXjrtIEtoKNcabyWciQmT31mAwcFcBPp_4Y4JgfpYpryE9no91PZmgUnzPK54kJ93yt3BOB_vH9E3N8yYy2PweSzZSuUQSGuAxJYq-3WDcH7ScVPX5QmLosR58ylpohabfrd_qNIyndMeTDPreq2PdUwU-JDYDeDniRiYwSiAOeE__Iwz6Bqzd_vSwPaNMhVKWaDv4U7OfaZ8uXOj9XJD6ggd- | 2021-01-26 12:18:18Z [DEBUG]:[GENERAL]:[5620] Encoded credentials: RMFrQFMVdXvfl5MRvBNLUrH8QwNHF3CeioK1TGCfUO-TsWEwS2TMFuHY3OOAs3M7Mgq8vdFJC19IEKGpWoIEkcw2JDIsnFwU9TT61iUm-Ro | 2021-01-26 12:18:18Z [DEBUG]:[GENERAL]:[5620] Callback context: zEmgs7Gp31vYr23mB4kYjIXvYis_uEMG51ke4_KbXAx8MWKJORKBIh9faqQ8-6QZ9gAStYQpeveDemPQAVNc43aDJVxmZ54Q3iFyyx_-eGg2B4kYd8aN9UwdIKxCyLmUgroE4Dl2qS--Mas8fiwjNWiK216nZ0Vgml1syioI0qY6kC-xBeP5KqDD_TwJxCsdG7E0x44ij97ltLQZ_Vtqwgyf96c_i2hAUP4h64oTVEv4OXGj93-4FM1NmABnwazyMeL4w6NVtbBCFe0J8QE7RIHjohf7gECEZ3yD5gD9qKRRaZxMpWtwyFkDFPQZOqUiLfuHWMQHe0xwdYrgwIsDR4GmPbwHjK0dbzSXt2arP-veAnD5QzNvEwHT808S15PHP6jSULvdGywGePC8bchuk26RyiyMQCU11dw8WWd2Q91ZMwO3MHF5eZmiCiPFSA5fV_eynbE3zVS4xW8neMjBpcj6UrO8hhHlnx6UdIoLO4_8qAFG | 2021-01-26 12:18:18Z [DEBUG]:[GENERAL]:[5620] Log line prefix: P | 2021-01-26 12:18:18Z [ERROR]:[GENERAL]:[5620] Failed to post callback command &apos;log&apos; to http://0.0.0.0:11117/_exec_callback/log/fXPLYTZHy-tWyOJOgrW1TO3o4ckMSaAnZLuZ5HbxH0q9I9gG4SanVGwvr90P9KOgGMpewaNYi09VeBVO7CLUTf2s_z4JDQbvkAYu2isSwbVqDCIFRwX-flqgUbkitPlLjyo_X8-DU9ZkX1avwkzvDnuz5070poI7FCN-WymtMWie8UPGfnL65BGb0qj-wd1WY753UMfvPhe0drIrF4Z5_ZASUGvgeyeaX78Vy38i8VVN8xVZ. No response was available. | 2021-01-26 12:18:18Z [DEBUG]:[GENERAL]:[5620] Package processing started as HORNBILL\Administrator. PID: 3128 | 2021-01-26 12:18:18Z [NOTICE]:[GENERAL]:[5620] Analysing input parameters | 2021-01-26 12:18:18Z [NOTICE]:[GENERAL]:[5620] Parameter: Name: ParamA Value: test | 2021-01-26 12:18:18Z [NOTICE]:[GENERAL]:[5620] Parameter: Name: ParamB Value: 10 | 2021-01-26 12:18:18Z [NOTICE]:[GENERAL]:[5620] Parameter: Name: ParamC Value: true | 2021-01-26 12:18:18Z [NOTICE]:[GENERAL]:[5620] Target platform: win64 | 2021-01-26 12:18:18Z [NOTICE]:[GENERAL]:[5620] Command Type: ps1 | 2021-01-26 12:18:18Z [NOTICE]:[GENERAL]:[5620] Timeout: 60 | 2021-01-26 12:18:18Z [DEBUG]:[GENERAL]:[5620] Using the native variant of PowerShell | 2021-01-26 12:18:18Z [NOTICE]:[GENERAL]:[5620] Using executable C:\Windows\system32/WindowsPowerShell\v1.0\PowerShell.exe | 2021-01-26 12:18:18Z [NOTICE]:[GENERAL]:[5620] Parameter ParamC is Boolean - modifying value for PowerShell | 2021-01-26 12:18:18Z [NOTICE]:[GENERAL]:[5620] Plain text arguments: .\&quot;DemoPowershell.ps1&quot; -ParamA test -ParamB 10 -ParamC true | 2021-01-26 12:18:18Z [NOTICE]:[GENERAL]:[5620] Base64 arguments: LgBcACIARABlAG0AbwBQAG8AdwBlAHIAcwBoAGUAbABsAC4AcABzADEAIgAgACAALQBQAGEAcgBhAG0AQQAgAHQAZQBzAHQAIAAtAFAAYQByAGEAbQBCACAAMQAwACAALQBQAGEAcgBhAG0AQwAgAHQAcgB1AGUA | 2021-01-26 12:18:18Z [DEBUG]:[GENERAL]:[5620] Console Output: C:\Users\ADMINI~1.WIN\AppData\Local\Temp\Hornbill\SIS Package Processor\3d69f3ae-6187-406c-8d70-d55a1571678d\Output/Output.txt | 2021-01-26 12:18:19Z [NOTICE]:[GENERAL]:[5620] Processing result: Exit Success | </processing> | </logging> | </result> | 2021-01-26 12:18:23Z [INFO]:[GENERAL]:[4452] Result: Success 2021-01-26 12:18:23Z [INFO]:[GENERAL]:[4452] Setting job 2073 status to processingOutput 2021-01-26 12:18:23Z [INFO]:[GENERAL]:[4452] Setting job 2073 status to succeeded Regards, Ricky

Hi James, We have identified an issue within the Runbook processing in that if an IT Automation node is the last node before an exit node a timing issue is caused which results in the error message that you are experiencing. It is confirmed that the automation is still being executed however Runbook process completes before the node exits, causing the error in the log. To resolve the issue two steps are required the first is to set the Wait For Response property for the IT Automation node to Yes. The next step is to add a decision node after the IT Automation node as can be seen in the screenshot: This should ensure that your process will always trigger the IT Automations and wait for them to exit. Regards, Ricky

Hi James, I have managed to replicate the issue and have passed the details onto the development team for investigation and will update you as soon as I get some further information. Regards, Ricky

Hi James, I have not seen this error before and am currently looking into it for you and will get back to you as soon as I find any further information. Regards, Ricky Fearon

Hi @Jamie A, thanks for your post. The Id field as specified in the error message can only contain alphanumeric characters that acts as the unique identifier for the new group once the entry is created the Organisation Id is modified to contain the parent entity's. For example if you were creating a new team "Team A" under Org1 for IT Department then you would enter "TeamA" for Organisation Id and "Team A" for Name, and once created the Organisation Id would change to "Org1\ITDepartment\Team" Regards Ricky

Hi @AndyGilly You will need to assign these user rights the account that is used as the ITOM Admin account for the Job / Scheduled Job, or if you have configured your SIS to use a service account, then this account must have these rights assigned. Regards, Ricky

@Paul Alexander, ITOM access should now be available on your instance. Regards Ricky

Hi @Paul Alexander I have asked the team for an update on this and will get back to you asap. My apologies for any inconvenience that this delay may be causing you. Ricky

Hi @Adam Toms, Great news on your first successful automation, glad that we were able to provide you with some assistance and will be more than happy to provide any further assistance as required. Ricky

Hi @Paul Alexander, changes are still required to be pushed out to the Live Stream in order for access to the Free ITOM offering becoming available. These updates are scheduled to be applied this Wednesday, and access should become available automatically. Apologies for any inconvenience this delay may have caused you. Regards, Ricky

@AndyGillywe have identified and resolved the issue, you should now be able to create new processes as required. Regards Ricky

Hi @AndyGilly, Apologies for the inconvenience there were some changes applied to the subscription manager internally that may have affected you, one of our developers is looking into this for you. Regards Ricky

@AndyGilly I have asked one of our developers to look into this for you, and hopefully will get a response soon. Alternatively you could raise the request and the update the request via the Hornbill Automation node using Type Update Request. Regards Ricky

You need to provide the Request Id, as the auto feature will not work with this node as the request is created within a runbook and not a Service Manager business process. to resolve this you will need specify the Request Id using the output from the Cloud Automation node &[global["HornbillServiceManagerLogNewRequestLogNewServiceRequest"]["requestRef"]] Ricky

Hi Andy, The error suggests that you have not supplied a mandatory parameter that the API is expecting before the custom B parameter. Can you post a capture of the node properties that you are using? Regards Ricky

Hi @AndyGilly, I have been informed that the admin tool has now been patched and you should now be able to access the package files. We apologise for the inconvenience caused. Regards Ricky

@AndyGillyThe fix should be pushed to the live stream this week, however I am looking at getting a patch that can be applied to your instance asap, to speed the process up. Regards Ricky

Apologies for the delay, I can confirm that the ITOM Free offering should be available for use on Thu 10th of this month. Unfortunately the move from Preview to the Early adopter release has required several major changes to be applied within different components of the Hornbill platform and these are all required to be pushed to the live stream, before access is made available. Once again my apologies for any inconvenience caused. Regards Ricky

@AndySorry for the delay in responding, I have been on leave, and am still waiting a response from the development team. I will give them a nudge this morning and get back to you with further information. Apologies Ricky

Hi Guys, apologies for the delay in gaining access to our ITOM offering, this is due to changes within the delivery process which requires changes to be rolled to the live stream, I don't currently have an exact date for this rollout, but believe it will be around Dec 7 date. I will provide a more specific update once I have been provided with more up to date details. Regards Ricky

Hi Dan, sorry to hear that your access has not been enabled I will inform the team, and get someone to look into it for you. Regards, Ricky

Hi Andy, I believe this issue has been resolved, sorry for any inconvenience, I will get the team to have a look and get this sorted in your instance asap. Regards Ricky

Hi @AndyGilly The issue is with the Runbook Process, in that the Human Task node will suspend the Runbook Process, waiting for user input. There was a design decision to remove all actions that have the protentional to suspend Runbook processes. I have been looking at possible workarounds that can be put in place, by moving the creation of tasks into a business process. This would involve temporarily storing the task details in a custom field and using the details to populate the Human Task from within the Requests Business Process. This would of course link the task to the BPM which would be suspend until all tasks were completed. I will also have a discussion with our development to see if there is any possibility in providing a feature similar to the Human Task that does not suspend the Runbook Process, possibly via a Cloud Automation. Regards, Ricky

Hi Andy, I noticed this issue late last week, and have asked our development team to have a look at it, which hopefully will be today, and will get back to you with an update as soon as I have further details. Regards, Ricky

@AndyGilly Unfortunately it is not possible to use the Human Task node as provided within the BMP as it would block the process from completing until the task was completed. I will have look to see if there are any other methods that can used to do something similar. Ricky