Spooler Performance Issue Update?

Hi Support,

Any update on the spooler performance issue?

LINK TO IDEA

This issue is already logged in the Ideas hub over a year ago and a business analyst did post:
[11 Months ago:
I have since raised this with our operational support teams, rather than product delivery. I will be in touch shortly to let you know the progress.
Thanks for highlighting this issue.
Adrian]

I've got more sites in past few months in addition to the previous sites that upgraded to 2015/2016 and are all complaining of the spooler speed.
Deleting spools is not a solution (or workaround) especially in high volume processing, aswell as retaining for audit purposes some clients use the spooler as part of their day-to-day processes with multiple workstations in large production environments.

Would really appreciate an update on this.

Thanks,

Paul

  • 0
    Hi Paul, have you heard anything on this yet?
  • 0
    Hi Gary,

    No, have not heard anything.

    Clients are noticing it more and more now in busier times, it can take anywhere from 15 to 60 seconds to open the spooler window, and if you happen to click anything in sage while it is trying to open the spooler sage becomes unresponsive until it has eventually finished the task of opening the spooler.
    Same thing happens if you already have the spooler window open and click refresh - takes same amount of time to refresh.
    Hearing it from other BP's too as you can see over on the raised idea.

    Thanks,
    Paul
  • 0
    Thanks Paul, we have a customer who has this problem every payment run. This might not be possible for your customer, but for ours we get rid of spool files (not ideal as you say above) but also clearing the local user temp and sage folders in %appdata%. Sadly this is a weekly/bi-weekly process. I've raised a case with the support team to see if anything has been logged though I couldnt see anything on the Known Issues and i cant remember hearing anything when i worked there.
  • 0

    Thanks Gary, yes that's exactly the case with our customers.
    Have to clear spooler and temp folders more frequently
    ( in saying that clearing the local user temp files seems to improve performance of Sage 200 in general not just the spooler)

    It is obviously something to do with the infrastructure change to Windows Auth in 2013, as Sage has to read each spooler and see if that user has access to that spooler in the relevant company before loading the list - so even if you have only a few hundred spools this can still be 10-15 seconds to load.

    Just an FYI, Incident 190216-E2327 going back to early 2016 would be an example of a old logged call
    Thanks,
    Paul

  • 0
    If i get any useful details i'll let you know and post it here for others to see.
  • 0
    Has there been any more updates on the Spooler issue. I am experiencing issues with Sage 200 V2015. It takes approx. 30 - 1 min for the spooler to open. I have cleared the users Temp Folder and cleared the server temp folder but still takes as long to load. Any ideas?
  • 0
    Sadly not, i was advised to vote up the idea on the original post.
  • 0
    Hi Paul (And other interested parties)
    I've noticed bug 7684 has been logged on the Known Issues.
    Might be worth passing details of your contacts to Sage on this.
    Gary
  • 0
    Cheers Gary, just seen the issue
    Took long enough to be recognised as a bug/issue

    The question is how long will it take to be looked at considering it was first raised as an issue back in 2015.
  • 0
    Weâ€Tmve been following this discussion closely and appreciate your patience whilst weâ€Tmve been investigating a number of possible solutions to the speed issue. Iâ€Tmm really pleased to say that our development team have been working on a solution that not only addresses the speed issue but also introduces a new filtering system that enables you to quickly find the reports you are interested in. We are hopeful this new feature will be introduced in the upcoming Summer 2018 release.

    The new filtering mechanism enables you to filter on report name, status, company, user and date range. Weâ€Tmd like your feedback on whether the filter should default to a known setting and if so what that setting should be. For example we could default to show all the reports you have sent to the spooler or alternatively all reports for the company you are currently logged into. Please feel free to add your thoughts on the default filter in the comments below.
  • 0
    Thanks for the update
    That's great.

    For a default filter, other partners/users may have a different approach,
    But I think my suggestion below would apply for most scenarios/setups:

    The default filter should be for the current user against the current company they are logged into and then sorted by datetime descending (or id descending),
    With the option of removing filters to see other company/user spoolers etc.. (obviously based on role and company access)

    Is there any chance this would be released as a service pack for 2016 version?

    Thanks,
    Paul
  • 0
    I think logically the settings Paul mentions would fit most people in my opinion.