Michael Sharp Posted June 17, 2020 Share Posted June 17, 2020 We're unable to open ANY requests on our Service manager - please can this be looked into ASAP??? Error below which seems to have followed the 17/06 update. Thanks, Mike. 1 Link to comment Share on other sites More sharing options...
Michael Sharp Posted June 17, 2020 Author Share Posted June 17, 2020 Please ignore this post - not sure why the update wouldn't be immediately removed if you had such severe reports earlier in the day? Link to comment Share on other sites More sharing options...
Gerry Posted June 17, 2020 Share Posted June 17, 2020 @Michael Sharp Just checking, so things are working? or is there still an issue? Gerry Link to comment Share on other sites More sharing options...
Michael Sharp Posted June 17, 2020 Author Share Posted June 17, 2020 Hi @Gerry thanks for the late response - working now following the cache clearing but like I said, disappointing that this wasn't pulled/fixed/reprovisioned in lieu of the issues it causes? Link to comment Share on other sites More sharing options...
Gerry Posted June 17, 2020 Share Posted June 17, 2020 @Michael Sharp Ok thanks, I am afraid pulling the release would not solve the issue, it was a dirty cache issue that needed a cache flush, the most effective resolution was a cache reset on each affected instance. Sorry for any inconvenience caused. Gerry Link to comment Share on other sites More sharing options...
Michael Sharp Posted June 17, 2020 Author Share Posted June 17, 2020 OK thanks @Gerry and thanks for coming back to me - no way to build the cache flush command into the update command? Mike. Link to comment Share on other sites More sharing options...
Gerry Posted June 17, 2020 Share Posted June 17, 2020 @Michael Sharp I thought you would have more faith in us than that Yes its built in, the problem is, there was a problem with the build and the order in which things were done got out of step, its not a usual problem but after investigation we found the issue and solved it, the fastest workaround was a cache reload sadly. Gerry Link to comment Share on other sites More sharing options...
Michael Sharp Posted June 17, 2020 Author Share Posted June 17, 2020 ok thanks @Gerry - as you can appreciate in our profession the stupid questions always have to be asked!! :-) Maybe something as rugged as text within the release notes (preferably in red or bold) to suggest this might be required going forwards perhaps? To be fair, found the fix (as I wasn't the first to jump in with this update) fairly quickly and you came back really quickly too fortunately on this occasion. Was really eager to start exploring the "most available analyst" function I guess which looks like a game changer. Cheers, Mike. 1 Link to comment Share on other sites More sharing options...
Paul Morrow Posted June 18, 2020 Share Posted June 18, 2020 I'm having the same issue this morning after just updating. Is this an ongoing issue? Link to comment Share on other sites More sharing options...
Paul Morrow Posted June 18, 2020 Share Posted June 18, 2020 Found the post elsewhere...ignore this.... 1 Link to comment Share on other sites More sharing options...
Victor Posted June 18, 2020 Share Posted June 18, 2020 For reference I will now lock down this thread if you like to discuss this further please use the above thread. Thanks. Link to comment Share on other sites More sharing options...
Recommended Posts