x Want to participate? Join the group to interact
Options
  • State Not Answered
  • Replies 55 replies
  • Subscribers 112 subscribers
  • Views 29599 views
  • Users 0 members are here
Browse Forums
Announcements
293
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
45
topics
91
replies
Payroll, Time Tracking, and Job Cost
777
topics
1k
replies
Reporting and Analytics
962
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 Reply Children
  • 0 in reply to D.Hart
    Still no fix for me as of yet. I have been given great advice, but still having issue.
  • 0 in reply to Keir_B

    Kier_B, did changing shortcut to the IP address help at all?

    Here are the step by step instructions for CS ODBC.

    Direct from the Sage Knowledge base:

    How to install and configure the Client/Server ODBC driver for Sage 100 Advanced version 2013 and higher
    Products
    Sage 100

    Description

    • How to install and configure the Client/Server ODBC driver for Sage 100 version 2013 and higher
    • How to install and configure the C/S ODBC driver (CSODBC Driver) for Sage 100 ERP Advanced
    • How to fix Registry entries for CS/ODBC when pathing or information is incorrect in Windows Services



    Disclaimer
    Network Warning
    This solution requires advanced knowledge of your network. Contact your system administrator for assistance. Modifying Windows security incorrectly can severely affect system operations. Sage is not responsible for operation issues caused by incorrectly modifying your Windows security. Always create a backup of your data before proceeding with advanced solutions.

    Operating System Warning
    This solution requires advanced knowledge of your computer's operating system. Contact your system administrator for assistance. Modifying your Windows Registry incorrectly can severely affect system operations. Sage is not responsible for operation issues caused by incorrectly modifying your Windows Registry. Always create a backup of your data before proceeding with advanced solutions.

    Note: For Sage 100 ERP Advanced (formerly Sage MAS 200) versions 4.10.1 through 4.50, there is a separate set of instructions. See the Related Resources section of this document.

    Client/Server ODBC driver components, when installed and configured, will allow remote workstations to process worktables using server-side ODBC processing. Report rendering is completed using a locally cached copy of the form or report and a local SAP Crystal Reports print engine.

    Remote workstations running over a WAN link connected through a VPN are ideal candidates for using the C/S ODBC Driver. Forms and reports will print significantly faster from remote workstations.Server-Side Configuration as an Application or as a Service
    Set up the Client/Server ODBC driver to run as an Application or as a Service before configuring the server. Decide which to use before proceeding.

    • To run as an Application:

    Note: This will have to be done each time the application is closed, such as when the server is shut down and restarted.

      1. Access the server where Sage 100 ERP Advanced is installed
      2. Open Windows Explorer and locate the pvxiosvr.exe file in "..\MAS90\Home"
      3. Right-click pvxiosvr.exe and select "Run as Administrator"
      4. A small "ProvideX File Server" window should appear a status message: "The Server is Running". Allow it to stay running. (It can be stopped by clicking the "Shutdown" button.)

    To run as a Service:

    • Create the Service:
      (Note: If the service is set to always start Automatically, it will do so each time the server is shut down and restarted.)
      1. Access the server where Sage 100 ERP Advanced is installed
      2. From the Windows Desktop, access Start, and Run
      3. Type: CMD 
      4. Press Shift+Enter to open Administrator Command Prompt
        (or Go to Start, Programs, Accessories. Right-click 'Command Prompt' and select 'Run as Administrator')
      5. Enter the local path to pvxiosvr.exe file, followed by a parameter of -i (Example: "C:\Sage\MAS90\Home\pvxiosvr.exe" -i)
      6. A service should be created, called "Sage 100 ERP Client Server ODBC Driver Service"
    • Configure the Service:
      1. Access the server where Sage 100 ERP Advanced is installed
      2. From the Windows Desktop, open Start, Control Panel, Administrative Tools, Services
      3. Verify the "Sage 100 ERP Client Server ODBC Driver Service" exists
      4. Right-click the service, select Properties
      5. On the General tab, select the Startup type "Automatic"
      6. Click Start to start the service, then click OK to exit Properties.
      7. Verify the service is "Started" before existing the Services window
    • How to fix Windows Service Manually when set up incorrectly
      1. From Windows go to Run and enter Regedit 
      2. HKEY_LOCAL_MACHINE\System\ControlSet001\Services\PVXIOSVR
      3. HKEY_LOCAL_MACHINE\System\ControlSet002\Services\PVXIOSVR
      4. HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\PVXIOSVR
      5. Update ImagePath to the correct Sage Path
        EX: C:\Sage\Sage 100 Advanced ERP\MAS90\Home\pvxiosvr.exe" -SERVICE 

    Workstation Configuration
    Set up the workstations (users) to take advantage of the C/S ODBC driver.

    1. Log into Sage 100 ERP Advanced
    2. Open Library Master, Setup menu, System Configuration
    3. On the ODBC Driver tab, select Enable C/S ODBC Driver
    4. For "ODBC Server Name", enter the server name or IP address where the client/server ODBC application or service is running
    5. For "ODBC Server Port", enter the default port 20222
    6. For the "Enable for All Users" checkbox:
      • Select if all Sage 100 ERP users will be using the C/S ODBC driver
      • Clear if specific users will be enabled. To enable for an individual user (after setting up in System Configuration):
        1. Open Library Master, Main menu, User Maintenance
        2. On the Preferences tab, select the "Enable C/S ODBC Driver" checkbox
        3. Click Accept to complete setup in User Maintenance
        4. Close and restart the workstation client
    7. Click Accept to complete setup System Configuration

    Access and Test the ODBC Data Source

    • If running a 32-bit system, perform the following steps:
      1. Access the server where Sage 100 ERP Advanced is installed
      2. From the Windows Desktop, open Start, Control Panel, Administrative Tools, Data Sources (ODBC)
      3. In ODBC Data Source Administrator, User DSN tab, select SOTAMAS90 and click Configure
      4. In ProvideX ODBC Driver Setup, Debug tab, click Test Connection
      5. In Sage 100 ERP Database Signon, enter Sage 100 ERP login credentials click OK
      6. If successful, you will the message "Connection succeeded"
      7. Click OK to exit the Setup and the Administrator windows
    • If running a 64-bit system, perform the following steps:
      1. Access the server where Sage 100 ERP Advanced is installed
      2. Open Windows Explorer and locate the ODBCAD32.exe file in "C:\Windows\SysWOW64"
      3. Right-click ODBCAD32.exe
      4. In ODBC Data Source Administrator, User DSN tab, select SOTAMAS90 and click Configure
      5. In ProvideX ODBC Driver Setup, Debug tab, click Test Connection
      6. In Sage 100 ERP Database Signon, enter Sage 100 ERP login credentials click OK
      7. If successful, you will the message "Connection succeeded"
      8. Click OK to exit the Setup and the Administrator windows


    ID:51211 Last Modified Date:9-17-20151442514011717   

  • 0 in reply to Jon_K
    Silly question, but in reading this thread, I don't think I ever saw a response to the question as to whether Sage 100 Standard or Advanced is being used? Or whether this is a WAN or a LAN?
  • 0 in reply to TomTarget
    I have replied to this in the past but FYI, advanced and LAN
  • 0 in reply to Jon_K
    Thank you. I will be testing this, this week and I will see if this corrects the problem.
  • 0 in reply to Keir_B

    Apologies for not noting those answers. On a LAN it doesn't seem highly likely that the CSODBC driver will do much unless the network speed is very low, but you have indicated it was up to par. Really strange. Can't hurt to try though.

    What is the available RAM on the workstations? Been years since I have seen it, but sometimes low available RAM can make crystal run very slowly.  Longshot possibility,  but nothing else seems to be working.

  • 0 in reply to TomTarget
    Another thought. Try monitoring the network traffic when running a report. Once had a client when running reports in the payroll module that should have only taken 30 seconds take more than 10 minutes to run. Watched the network traffic and there was a tremendously high network traffic. Probably 10x more than if I ran the same report on my own system with their data. Run from their server, everything looked good.

    Unfortunately we never did figure out what was going on in their system to cause it.
  • 0 in reply to TomTarget
    8gb of ram with 500gb solid state drives.
  • 0 in reply to Keir_B

    That shouldn't be an issue with that much RAM.

  • 0 in reply to TomTarget
    Tom, we have reports that run in seconds for our remoteapp users (halfway across the country) and those same reports take a good 30 seconds to 2 minutes for us on the LAN. My machine has 16GB of RAM and a 512GB SSD, the network is Gigabit. Obviously there is no back and forth network communication when they are running reports on the server, so I would expect them to be slightly slower for us. Do you see this as being normal? I am wondering if CS ODBC is an option we might try as well.

*Community Hub is the new name for Sage City