Jump to content

Jack_Podmore

Hornbill Users
  • Content Count

    50
  • Joined

  • Last visited

Community Reputation

2 Neutral

About Jack_Podmore

  • Rank
    Advanced Member

Recent Profile Visitors

428 profile views
  1. Hi @Steve Giller Sorry about that, I filtered wrongly on "date modified"! I have checked over our configuration and we only have 1 "Data Import Configuration" setup which has always worked without issue. Could this be to do with the "LDAP Hardening" Microsoft have introduced? Thanks, Jack LDAP_User_Import_2020-03-16T16-52-37Z.log
  2. Hi @Steve Giller Thanks for replying on this. There is nothing in the logs from what we can see (attached with API key removed). The configuration hasn't been touched within Hornbill and nothing has changed with the user account that runs this. We have updated the LDAP Import Tool as our first try at resolving this but with no luck. What is odd is that existing accounts are being updated without issue it just wont import any new ones. Thanks, Jack LDAP_User_Import_2018-09-24T13-02-36+01-00.log
  3. Hi guys, For some reason our LDAP import setup has stopped creating new user accounts. No changes have been made to our setup that we are aware of. Existing users attributes are updating normally without issue - does anyone have any ideas!? This started happening around the 1st March. Thanks in advanced!
  4. Hi guys, I'm not sure if its us not looking in the right place but when a ticket is on hold the "category" button is greyed out: When trying to change this under Hornbill Service Manager > Configuration > Request Settings this doesn't seem to be available as an "on hold" setting to change. Are we looking in the wrong place? Thanks, Jack
  5. @ArmandoDM Thank you for getting back to me so promptly on this - much appreciated. What's the normal lead time on something like this, its been like it for some time now Thanks again, Jack
  6. Hi guys, @Hornbill Support Team @Victor @James Ainsworth Sorry to pick you out directly but we have been dealing with this issue for a number of weeks now and cant get to the bottom of it. For some reason since the upgrade to build 1805 we are getting the below error message within our tickets. In terms of BPM a task is is assigned to a ticket which is then resolved which changes the status of the ticket, its at this point the error message is coming up. If I "restart the last step" it seems to then re-process this step without issue. We haven't made any BPM changes and have "re-published" just in case. This is taking up a lot of time each day as the only sys admin to restart the last step to clear the issue. Any advice welcome! We have also got this error on 1 or 2 occasions
  7. We are now also getting this error on some tickets. Please can someone help @Hornbill Support Team?
  8. Hi guys, We have lost access to our instance (phservicedesk): Please advise! Thanks
  9. Hi guys, For some reason since the upgrade to build 1805 we are getting the below error message within our tickets. In terms of BPM a task is is assigned to a ticket which is then resolved which changes the status of the ticket, its at this point the error message is coming up. If I "restart the last step" it seems to then re-process this step without issue. Any advice welcome! Thanks, Jack
  10. @Keith Stevenson our instance now seems to be running a lot smoother with no errors. Thanks for looking/resolving this so quickly!
  11. +1 We are also seeing issues with Hornbill and are not able to connect!
  12. Hi @Deen, I was wondering if you have been able to query this with the dev's at all? Thanks, Jack
  13. Thanks @Deen - much appreciated!
  14. Hi guys, Has anyone else noticed that "Calibri" as a font is missing from the main email section within Hornbill? By default our email templates are of this font but if we manually send an email out this is missing. From within a ticket is fine: When composing a new email from the "email" section: Thanks, Jack
×
×
  • Create New...