Steve G

Hi @Martyn Houghton, 2.36.4 is now live, please feel free to upgrade Service Manager on your Hornbill instance to pick up the fixes contained within this patch. With regards to the restart of the BPM, I'll need to confirm this and get back to you. Kind regards, Steve

Hi @Ralf Peters, @Martyn Houghton, @Paul Morrow, @nasimg, The distinct errors that have been raised in this post, and those in the below post, are fixed, and the fixes will be included in the 2.36.4 patch. This patch is on course for release this afternoon. Kind regards, Steve

Hi @Martyn Houghton, We're looking to release 2.36.4 today. I'll let you know here as soon as this is in live. Kind regards, Steve

Hi @Martyn Houghton, Your initial issue on this post (regarding assignTeamOwnerCapacity) was evident in BPM nodes that assigned a request to the most available analyst. We've fixed this issue, and this will be released in Service Manager patch v2.36.4. The other BPM issue is currently under investigation. Kind regards, Steve

HI @DeadMeatGF, Glad to hear the first issue was just a problem with the API Key I'll put some extra logging in the next release of the utility to catch these errors a little more gracefully. With regards to the index storage error, this was due to an issue with the install scripts when the application was installed on your instance. We've fixed this for you, so the import should now work as expected. Let me know if you have any other issues! Kind regards, Steve

Hi @DeadMeatGF, It appears that the tool isn't getting as far as to connect to the SCCM database, it looks like you may have an issue with connecting to your Hornbill instance from the machine that the tool is running on. Do you have a valid APIKey, and InstanceID (case sensitive) in your configuration JSON? If you do, then this may be due to your proxy (should you have one) getting in the way of the traffic. Please see the HTTP Proxies section of the Asset Import wiki page for more information: https://wiki.hornbill.com/index.php/Database_Asset_Import Let me know if I can be of further assistance. Kind regards, Steve

Hi Bob, Apologies for the time taken to respond to your post. Are you still experiencing this issue with the Hornbill Cleaner tool? I've ran v1.0.3 against an instance with a number of assets on, and this is working fine on this instance. From the message you are receiving, the issue may be that the account that you are using for the delete may not have the correct permissions to run a query against the table that holds the primary asset records. Have you tried this with an administrator account for your instance? Kind regards, Steve

Hi @ljbrown, I've just released version 1.0.3 of the Hornbill Cleaner Utility to Github. This version allows you to specify the class of requests that you wish to delete. For further information please see the Hornbill Wiki page: https://wiki.hornbill.com/index.php/Hornbill_Clean_Utility And the Github Repository: https://github.com/hornbill/goHornbillCleaner/ Kind Regards, Steve

Hi Tony, Thanks for confirming that this utility is now working for you! For any other customers reviewing this thread, the issue experienced was due to two factors: 1. An incorrectly formatted configuration file. The conf.json should contain the following information: { "UserName": "adminusernamegoeshere", "Password": "adminpasswordgoeshere", "URL": "https://eurapi.hornbill.com/instancenamegoeshere/xmlmc/", "CleanRequests": false, "CleanAssets": false } 2. A customer-side corporate firewall rule blocking access to the API endpoint. Kind regards, Steve

Hi Tony, I've just emailed you a slightly modified version of the Hornbill Cleaner, which will output the actual API response to the screen, rather than just the currently displayed error message. I've also included a conf file, with the URL set, so you just need to add your admin account username and password in to the empty string holders for the cleaner to run. If you could try this version and post the resulting error message back here that would be great. Kind regards, Steve

Hi Tonyo, This error is being returned because the released binary was compiled on a 64bit Windows machine, and thus will not run on a 32bit Windows machine. I'll compile a 32bit version and sent it over to you directly. Please send me your contact details in a private message. Kind regards, Steve