Sage 100

 View Only
  • 1.  Sage 100 2015 advanced. Running as an application

    Posted 09-12-2018 07:15
      |   view attached
    Sage 100 2015 advanced. Running as an application - just started getting ""regular"" (every few minutes) ""Sage100 ERP has stopped working"" on the server - APPCRASH - usually with fault module MSVCR100.DLL. Users do not seem to be complaining but these really pile up on the server admin console. Sage100 2018 is installed on the Server (they are testing), but this did not start when 2018 was installed. Does anyone have any insights on this ? TIA


  • 2.  RE: Sage 100 2015 advanced. Running as an application

    Posted 09-12-2018 07:43
    I think that is a c++ dll that gets installed with the workstation. Can you verify it is present and registered on the server and/or on the machines? Maybe replace and register it with a fresh one? Or reinstall the workstations or prerequisites?


  • 3.  RE: Sage 100 2015 advanced. Running as an application

    Posted 09-12-2018 07:54
    MSVCR100.dll is component of the Visual C++ 2010 Redistributable Package (x64) - http://www.microsoft.com/en-us/download/details.aspx?id=14632 It's used by the 64-bit ODBC driver. Perhaps CS ODBC driver was recently installed and configured for some users too? Maybe reinstall 64-bit ODBC or this package if it seems to occur when someone is printing.


  • 4.  RE: Sage 100 2015 advanced. Running as an application

    Posted 09-12-2018 08:53
    When you installed 2018 on the server, did you deploy the CR patch to all workstations and copy the config file to the server's 2015 home directory?


  • 5.  RE: Sage 100 2015 advanced. Running as an application

    Posted 09-12-2018 08:54
    No, that was not possible at this client. They are doing their initial testing on one new PC that has 2018 installed. No other PC had 2018 installed. No users are reporting any errors in 2015


  • 6.  RE: Sage 100 2015 advanced. Running as an application

    Posted 09-12-2018 08:57
    I'm guessing you can't print from 2015 on the server then. Perhaps it's caused when a user is processing something through Paperless...? (Just a guess).