PrintBoss time again

I have a bit more information and still in search of a suggestion.  

On new/test server, running PB (newest version, just updated again yesterday) w/ Sage 300 v 2017, it takes 36 seconds for an AP check batch to begin to print if there are one or two checks.  A larger batch (73 checks) takes 1 min 17 seconds.  The current production system runs v6 with a PB version from 10 years ago. Both large and small batches start in around 15 seconds in the production environment.  We don't do anything else with the PB product so I have no other benchmarks.

In the test system, even if we print to Adobe on the server, we get this kind of response time.

If in the test system (soon to be the production system) the delay for all batch sizes was around the 36 second mark, they would be ok, but the longer time for large batches is causing concern.  They print upwards of 200 checks multiple times each week and are worried about how long it will take when they get to that size batch.  

We talked to PB tech support, and they have said this is environment/network.  The network people say it is PB.  Sage 300 long reports start to print in under 20 seconds, so I can see their point.

PB tech support thinks that other resellers have experienced something similar and solved it.  I welcome suggestions.

Thank you.

  • 0

    Hi Mary - we also have a site where this is a problem. Client also noticed that it got slower and slower during the day - not based on server load but based on how many times they had opened and closed PB that day. Wellspring support is generally excellent, but they were not able to solve this and neither was the IT dept. Our client doesn’t do such long check runs, but we have a Bill of Lading that goes thru PrintBoss many times a day, as each shipment is picked up. Support suggested that they open PB at the beginning of the day and keep it open, and that has helped a lot. Now the person who prints checks does the same and says it helps, but still slow. This client is also on 2017. Let me know if you want more info and I can log in and do some testing

  • 0 in reply to wheumann

    We're stiil struggling, but we are also having a problem with the printer not being found.  I'll be back in touch once we get that resolved.