Sage 100

I went back and did a search of inquiries and found multiple inquires on this forum regarding various versions and post upgrade the printing running very slow. I have seen many suggestions but have not seen where anyone has a definitive solution with their problem. It is possible we are all suffering slow printing with no solution (in my case particularly related to terminal server). We have 1) Turned off the antivirus 2) Tried direct printing 3) Tried a local PDF and XPS file 4) Turning on and off paperless with same results on or off. VERY slow performance (about 25 seconds to 40 seconds) to produce a invoice or register. This client is on 2017. I have seen others in differing versions. Anyone have a list of settings for optimizing printing? On a terminal server in particular would be great.

What's the response time on a ping from the location using the printer to the computer the remote desktop is connected to?

Standard? Advanced? Premium?

Have you confirmed that it is also slow printing for MS Word and other, non-Sage products? If so, this is not a Sage problem, so not yours. Explain it to customer, and tell him to get his IT consultant to fix it. We refuse to cover for IT's incompetence when it is clear that a problem like this affectes ALL printing, not just Sage.

<1 on ping from Terminal Server to Sage server. They are on Advanced. And sometimes IT is willing to let the customer suffer more than I am willing.

For what it's worth, Larry, we have found server resources to be the culprit alot. 1. People mis-understand that that RAM per user required (on the SPM) refers to the number of users on that server, not just the Sage users. 2. Relevant drives are often partitioned pretty small on some of these VM servers. 3. And we just got a big boost on report performance by IT tweaking processing power by (in this case) allocating 4 sockets versus two logical processors.

12 seconds to print from excel.

I have not seen experienced this as a widespread issue. There are various other things such as payroll direct deposit stub printing which is very slow. I have a mix of regular desktop (probably 80%) and perhaps 20% that are Terminal Server. Not saying this doen't exist but that it hasn't come up as an issue. I seem to recall the allocation of cores on VM was brought up once before when also dealing with virtual servers (which I think @RhondaMcNamara item #3 may be alluding to)

Already passed the potential solution onto the VM manager. We will see what we get back.

@LarryBradford Not the speed from the terminal server to the Sage server... From the terminal server to the server at the remote location. Crystal reports is client side processing. It doesn't matter if it is advanced premium or standard. The print data has to pass over the network from the terminal server to the printer.

@DougHiggs , So are you saying the C/S ODBC may help with the issue?

All I am saying is the Crystal job sends data from the workstation, in your case the terminal server to the printer. Check the data transfer speed between the workstation and the printer. Sending a graphics print job over a slow WAN connection may take a while.

CS ODBC should help with Advanced print speed.

It is the blue bar that comes up that seems the slowest in generating the job. If it has to get driver information from the local machine in California to produce (even for a preview) that would explain a lot.