Sage 100

 View Only
  • 1.  Notes from a recent Sage 100 2017 install: (1)

    Posted 03-31-2017 13:56
    Notes from a recent Sage 100 2017 install: (1) Just because the installer says the license keys don't include payroll doesn't mean it's true. Proceed and check the Payroll Subscription Expiration date in System Configuration, modules. If it says FAIL, go to the registration tab, click Edit, don't change anything, and click activate. then check the Payroll Subscription Expiration date again. (2) Make a copy of the fresh install before running migration. If the customer is using Webroot AV, make them turn it off. Xcopy error and most of MAS_System is gone...


  • 2.  RE: Notes from a recent Sage 100 2017 install: (1)

    Posted 03-31-2017 13:59
    Oh, good call, most of our clients are using Webroot now (at our recommendation). Thanks for being the guinea...er pioneer, yeah, pioneer!


  • 3.  RE: Notes from a recent Sage 100 2017 install: (1)

    Posted 03-31-2017 14:00
    Sage support has a group of six people, including Ron Aspe, cataloging all the ways the payroll keys can screw up...and they have multiple records of issues with webroot, including it demolishing a bunch of payroll files during payroll processing


  • 4.  RE: Notes from a recent Sage 100 2017 install: (1)

    Posted 03-31-2017 14:09
    And don't assume the keys on the client's portal are the same as on your portal as I have had differences in both. I have also had issues with getting the correct keys now for months. This new payroll separation has been one of the biggest blunders I've seen from Sage in the 25 years I've been using it! One hand is not speaking to the other...still shaking my head over the many lost billable hours from dealing from Sage's lack of communication. My client's are very upset with this transition and the lack of communication they've received and the way they have been treated with trying to renew. And PLEASE DON'T SEND THEM A FAX because they go to a big hole! I've sent the same faxes up to 5 times with no results, so frustrating!


  • 5.  RE: Notes from a recent Sage 100 2017 install: (1)

    Posted 03-31-2017 14:11
    I've also had damaged program files with the migration process while using Webroot...


  • 6.  RE: Notes from a recent Sage 100 2017 install: (1)

    Posted 03-31-2017 15:41
    I see Webroot being deployed more and more. Are there anything specific directions to provide to IT when using Webroot, such as file extension and directory exclusions as we have in the past?


  • 7.  RE: Notes from a recent Sage 100 2017 install: (1)

    Posted 03-31-2017 15:51
    One of the cases Ronnie told me about said that even doing the exclusions didn't stop webroot from eating the payroll files


  • 8.  RE: Notes from a recent Sage 100 2017 install: (1)

    Posted 03-31-2017 15:58
    _The evil AV ate my paycheck_...that would get the IT staff's attention...


  • 9.  RE: Notes from a recent Sage 100 2017 install: (1)

    Posted 03-31-2017 18:21
    Webroot seems to be popular with the managed services crowd. The version deployed with desktop monitoring bundles doesn't even allow exclusions, it's on or off. We have moved several clients who had 100c subscriptions to advanced and that eliminated the issues we were having with the legacy modules (PR and WO) and files randomly disappearing.