Sage 100

 View Only
  • 1.  Well, since I've been on hold with Sage for 23 min

    Posted 06-21-2017 11:27
    Well, since I've been on hold with Sage for 23 minutes now, I guess I'll post this here while I wait. Customer gets ""Could not contact Sage Licensing Service. Please use the Update button on the Registration tab in System Configuration to try again."" IT thinks he has any hint of firewall excluded, put in an outbound rule, etc, etc. Anyone else seen this and had something other than a firewall be the issue? The Sage tech actually logged in and spent a half hour on this and still no fix.


  • 2.  RE: Well, since I've been on hold with Sage for 23 min

    Posted 06-21-2017 11:32
    Bad DNS or missing Default Gateway on the server's networking properties?


  • 3.  RE: Well, since I've been on hold with Sage for 23 min

    Posted 06-21-2017 11:34
    This post has the license URL: https://90minds-com.socialcast.com/messages/34637006


  • 4.  RE: Well, since I've been on hold with Sage for 23 min

    Posted 06-21-2017 12:04
    Beth, are you blocking foreign gateways the licensing server is in Ireland amazon cloud the ip is 52.31.248.165 we ran into it with our sonic wall.


  • 5.  RE: Well, since I've been on hold with Sage for 23 min

    Posted 06-21-2017 12:06
    Thanks everyone - I'm throwing this at IT because I am NOT network savvy...


  • 6.  RE: Well, since I've been on hold with Sage for 23 min

    Posted 06-21-2017 18:21
    Are they using a Proxy Server? Had similar message recently and as soon as the proxy was disabled everything worked.


  • 7.  RE: Well, since I've been on hold with Sage for 23 min

    Posted 06-22-2017 05:06
    I'll check on the proxy, but I don't think so. What we ended up doing was that Scott Brady at Sage had me send him the 2 files involved (SY_Modules and SY_System) and he manually modified them and sent them back. The bad part is that the client is up for renewal in just 2 weeks, so we will have to go through this again if it's not fixed by then.


  • 8.  RE: Well, since I've been on hold with Sage for 23 min

    Posted 06-22-2017 06:03
    IMO, we just have to figure out what to edit in those 2 files.


  • 9.  RE: Well, since I've been on hold with Sage for 23 min

    Posted 06-22-2017 06:04
    I have copies before and after.... but haven't delved in yet.


  • 10.  RE: Well, since I've been on hold with Sage for 23 min

    Posted 06-22-2017 06:09
      |   view attached


  • 11.  RE: Well, since I've been on hold with Sage for 23 min

    Posted 06-22-2017 10:05
    Sage suggested the below for a client who had PR expire date issues. Their IT whitelisted the below and it did take care of their problem. It may apply here too. Have their IT add an Inbound Firewall exception for the following websites: https://licensing.services.sage.com/lic/services/LicenceService 52.31.248.165 (port 443)