Sage 100

 View Only
  • 1.  Sage 100C - V2017 ADV (but client is currently run

    Posted 09-15-2018 12:29
    Sage 100C - V2017 ADV (but client is currently running it as STD) on a WIN 2016 VM server. (the install from hell). Two issues this week - Client is running in STD mode mainly due to sluggishness printing Crystal in ADV. Based on timing comparison tests yesterday, when printing an AP invoice register update in ADV, the report took 1:22 to preview. The same update to 12 seconds in STD to preview. Something is rotten in Denmark, but what? I have poured over the SPM (in spec), it appears to have plenty of memory, yada, yada, yada. When users run it in STD mode, life is good except for mornings where it takes a server reboot before everyone can get in. Usually one person can get in, but everyone else hangs until the server is rebooted. IT claims the server is rebooted around 3 AM everyday. After rebooting it manually at 7:30, everyone can get in. Thoughts? I know I haven't provided a lot of detail information, but just looking for wild ideas.


  • 2.  RE: Sage 100C - V2017 ADV (but client is currently run

    Posted 09-15-2018 13:38
    Have you tried using the CS/ODBC printing service (don't recall the official name)? Have a client with many users running Advanced with this. The service hangs every 6-8 weeks and gets manually restarted, but otherwise works great!


  • 3.  RE: Sage 100C - V2017 ADV (but client is currently run

    Posted 09-15-2018 14:07
    Yes. Ran the update in ADV with it on and once with it off for the user. Nearly the exact same time both times. I had rebooted the server that morning so the ODBC service doesn't seem to the issue.


  • 4.  RE: Sage 100C - V2017 ADV (but client is currently run

    Posted 09-16-2018 08:47
    Anti-virus?


  • 5.  RE: Sage 100C - V2017 ADV (but client is currently run

    Posted 09-16-2018 09:27
    Good thought. I told them to shut it off, but will have to double back and check that one.


  • 6.  RE: Sage 100C - V2017 ADV (but client is currently run

    Posted 09-16-2018 09:35
      |   view attached
    A single workstation set to scan network locations can really throw things off. Checking for files being accessed through shares can help.