x Want to participate? Join the group to interact
Options
  • State Not Answered
  • Replies 55 replies
  • Subscribers 112 subscribers
  • Views 29496 views
  • Users 0 members are here
Browse Forums
Announcements
289
topics
370
replies
Business Object Interface
1k
topics
7k
replies
Core Financial Modules
2k
topics
8k
replies
Customization and Productivity
3k
topics
12k
replies
Distribution, Manufacturing, and Applications
2k
topics
7k
replies
General Discussion
1k
topics
3k
replies
Partner Cloud
43
topics
90
replies
Payroll, Time Tracking, and Job Cost
775
topics
1k
replies
Reporting and Analytics
960
topics
3k
replies
Sage CRM for Sage 100
164
topics
357
replies
Technical and Installation
2k
topics
9k
replies
Year-end Forum
89
topics
237
replies
Keir_B

Printing Reports taking abnormally long time since switching to workstations from Terminal Server.

Posted By

Since moving my client from a Server 2008 Terminal Server to individual workstations, printing reports of any kind are now taking over 5-10 mins to print 5 pages.  This includes just running print preview.

I'm currently running Mas 100 ERP version 5.10.7.0 with 10 users now running Sage client on individual workstations.  Each workstation is Win 7 pro 64bit with 8GB ram. Printers are Dell Printers using an HP Driver mimic from the Terminal Server.

I have attempted to try printing to shared printer both from the Terminal Server and also a print server.  I have installed the printers locally as well with no luck.Logging into the MAS server and printing the reports still prints the jobs in 5-10 secs.  I have attached computers directly to the same switch that the server is on, but that does not help.  I have tried to get outside help from a Sage Support Company, but they were unable to help and just said they cant do anything with it.

Please let me know what I need to do to the client PCs to speed up printing in MAS!  Every other aspect, Office, web printing all print normally, just an issue in MAS

Thanks,

Keir

Parents
  • 0
    Printing speed depends on what is between your server and workstation - cabling wise. If you are working over a WAN/VPN then 10 minutes to print a report is to be expected. You say that you switched from terminal server to workstation so I highly suspect you are NOT running on a LAN.
    Ping the server from a workstation, what are your average round trip times?
  • 0 in reply to 49153
    This is your most likely issue. My second suggestion would be anti-virus/malware scanning. If you are running Sage 100 Advanced you'll see fast performance on screens and posting but the printing can bottleneck because it's running Crystal locally, creating work files and passing that data at local speeds between server and workstation.
  • 0 in reply to Wayne Schulz
    I have disabled all AV and anti malware software.
    The terminal server is not the mas server so it ran as a client but does not have the issue. Only the win 7 machines have the issue.
Reply Children
  • 0 in reply to Keir_B
    So directly on the term server, speed is good, but for the users dialing into the term server, there are issues? Sounds kind of more like their connection than Sage.
  • 0 in reply to Rsmcnamara
    Sorry to mislead you if I did. The terminal server is over 5 years old and the speed is great but as we started to replace the end users thin clients with full pc workstation the workstations print slow. People who still connect to the terminal server still have no issues.
  • 0 in reply to Keir_B
    As an additional speed test - try copying a large file from the server to your workstation and see how many MB per second you are getting. Cliently recently was having slowness issues from two workstations. Transfer speed was only about 1.5 MB per second. Other workstations were getting 4-5 MB second. They replaced the network cabling and ended up getting about 11 MB second. Vast improvement in Sage 100 responsiveness.

    On my own server, we saw dramatic differences between Raid 5 and Raid 10 hard drive configuration. 10x speed improvement.
  • 0 in reply to TomTarget
    I use a utility LAN Speed Test (Lite) www.totusoft.com/lanspeed1.html for testing LAN speed.
    You will be surprised what you find. We were getting 8Mbps instead of the advertised 100Mbps and after some investigation we found the problem, corrected it and all printing issues went away. Reports printing in about 10 minutes now print in less than 10 seconds.
  • 0 in reply to 49153
    Yea!

    Out of curiosity, what did you trace the problem to?
  • 0 in reply to TomTarget
    Bandwidth throttling on the router :(
  • 0 in reply to 49153
    Thanks for the info.
  • 0 in reply to TomTarget
    Traffic does not go through router. This all happens on a gigabyte switch (running cat5e cables)
  • 0 in reply to Keir_B

    Did you check your network speed with the utility that 49153 suggested? I downloaded it and tried it on my system. If found that I was getting about 50MB throughput from my workstation to one server and about 80MB throughput to a different server. A different workstation was getting about 90MB. I have not tried it yet on any of my clients with noticeable slow operations (note that none of them are nearly as bad as your situation).

    The utility doesn't really tell you exactly what is wrong. It just tells you that something is slowing your throughput down and then you have to go hunting.

  • 0 in reply to TomTarget
    The Sage 100 system architecture matters, and while you said something about "the local odbc driver on the clients but also didn't help", but that is not the CS-ODBC configuration (which does not involve installing drivers on the client machines). Normally, with a Providex back end, the workstation's Crystal Reports print engine talks directly with the data files, over the network. These files can be large, and take time to open directly, line by line, linking table data... When configured, the CS-ODBC service (running on the server) does this for you. The client workstation doesn't access the Providex data files over the network, the service does that and returns the results to the client's print engine, which bypasses the heavy network traffic when printing.
    To set this up, look in the KB for details on configuring the CS-ODBC service. Then enable the option in User Maintenance for the people you want to test with.

*Community Hub is the new name for Sage City