derekgreen Posted May 1, 2018 Share Posted May 1, 2018 Hi - we have just upgraded our instance and now receive the attached error on calls raised since then. Can someone advise? Thanks! Link to comment Share on other sites More sharing options...
derekgreen Posted May 1, 2018 Author Share Posted May 1, 2018 Oops! Looks like the error has rectified itself - maybe I tried accessing our instance before the upgrade had completed! Sorry. Link to comment Share on other sites More sharing options...
derekgreen Posted May 1, 2018 Author Share Posted May 1, 2018 My mistake - what seems to happen is that the error appears whenever I access a new call for the first time or two, then it disappears. Bit anooying! Link to comment Share on other sites More sharing options...
derekgreen Posted May 1, 2018 Author Share Posted May 1, 2018 Further info - if I restart the BPM the call progresses ok, but there is still something wrong if I'm getting an error on every call raised. Link to comment Share on other sites More sharing options...
James Ainsworth Posted May 1, 2018 Share Posted May 1, 2018 Hi @derekgreen There was a platform update just released (Hornbill ESP Build Number: 2913). This update will be automatically applied to your instance. It is possible that a correction made in this update might also help with your reported issue. From your Profile menu in the top right of Hornbill, you can access the About information which will show you the current platform build. Please let us know if you are still experiencing this after 2913 or greater is listed here. Regards, James Link to comment Share on other sites More sharing options...
derekgreen Posted May 2, 2018 Author Share Posted May 2, 2018 Hi James - thanks for the above. New issue this morning is that no one can access the service portal. ADFS is running ok, and we haven't changed any settings here. Wonder if you can advise? Link to comment Share on other sites More sharing options...
James Ainsworth Posted May 2, 2018 Share Posted May 2, 2018 Hi @derekgreen My first thoughts would be to look at changes to your network environment. If the configuration in Hornbill has not changed, and it can no longer connect with ADFS, it is possible that something has changed in your environment. Please post back if a solution is found or if this is still occurring. Regards, James Link to comment Share on other sites More sharing options...
Claire Holtham Posted May 3, 2018 Share Posted May 3, 2018 It's not a soon to be expiring adfs certificate is it? If it's swapped from the primary to the secondary, the new certificate number may need manually updating in ServiceManager. Just a thought. Link to comment Share on other sites More sharing options...
derekgreen Posted May 22, 2018 Author Share Posted May 22, 2018 Hi All sorry for the delay in getting back. One of our network guys had made a change (as some suspected!) - all ok when he reversed it! Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now