Deen

To close this one off, the patch should no longer be required as the fix has been included in the latest Service Manager build.

@Alberto M could be down to the following Service Manager setting, would be worth checking to see if it is enabled:

@DFarran @Logan Graham The patch has now been applied. In order to apply the patch you will need to reload the application. There is a button in the Admin view for this:

@DFarran @Logan Graham i'll ensure that your instances are also patched today.

@Jeremy would also be worth running the indexing out of working hours if possible.

@Paul Alexander @Adam Toms i'll look into getting your instances patched.

@Jack_Podmore we are aware of the problem and are currently working on a solution. There will be a further update shortly.

@Martyn Houghton your instance should now be patched, it would also be worth refreshing your browser cache before attempting to replicate. If you still have issues let me know on the request you have open and we can deal with it from there.

@HHH Your instance has also been patched.

@Cassie we now have a fix for this and your instance will be patched later today.

@Martyn Houghton @Alisha we now have a patch for this and your instances should be patched later today. Let me know if the problems persist afterwards.

Looking like a potential defect. I'll post back here shortly when I have confirmation and more info.

@Joyce I take it the team name has remained the same since 2017 as that is the only thing I can think that might have changed.

@7oaks that looks like a timeout, possibly during a period of inactivity. I take it your browser had not been idle for a while before this. Also have you seen it again since or was it a one off?

@TomW it may also be a timeout issue linked to either the size or number of reports being run, does the problem still occur if you set the json to only do one report, and also specify a simple report that only returns a few results?

@TomW would be worth looking at the log as there may be additional info in there, all logging output is saved in the log directory, in the same directory as the executable. The file name contains the date and time the import was run.

@Hollie @PeterL @Lauren @StephC @DFarran @AndyHill Hornbill ESP build 3237 has now been released to live and as detailed in the release notes contains a fix for this particular issue.

@J_Tamburrini @chriscorcoran the just released v1.3.0 of the Power BI Hornbill Data Source scripts should correct this issue. I have emailed you the full details on the requests you have open with us.

@7oaks as far as i'm aware, they would have to select the view and then select the 'Home' icon which has a 'Set Current view as my home' option to make it their default view.

@AndyHill it might be possible to configure using the business process engine. In terms of out of the box functionality i'll tag this as an enhancement.

This is still being looked into although there does appear to be a link between the volume of data, for instance a weekly report is unlikely to have problems but a monthly report is more likely to timeout and lead to the empty table.

@Alisha you can always add a comment to the time line entry for the link event. I've tagged this as an enhancement though.

@Adrian Simpkins the following wiki article may shed some light on the various notification settings: https://wiki.hornbill.com/index.php/Service_Manager_Notification_Settings I take it they are set to either Hornbill only or Both?

@nasimg RCA below: At 07:40 on Friday we noticed slower than usual SQL query responses. The root cause was found to be the inadvertent removal of an index during the prior night's update. This index was removed in error, as there were other query dependencies that required the index to be in place for some large data sets. The issue was identified, diagnosed and resolved for all affected instances by 09:18 the same morning, and there was no data loss. We recognize this issue caused some of our customers disruptions and for that, we unreservedly apologize, thank you for your patience and understanding.

@J_Tamburrini sorry to hear that, is it the same as before or is it giving you a specific error this time?