Sage 100

Are you sure this couldn't be a TLS or some other issue with reaching the licensing servers? I think v2022 was supposed to be TLS 1.2 compliant though I remember Sage had patches for earlier version. 

I'm not sure this is so much a licensing decline as Sage support refusing to provide help for an unsupported version.

I also ran into and documented this issue which I think had to do with my client using some type of proxy server.

Sage 100 Registration Expiration Does Not Change or Update

@Wayne Schulz  Did your customer have an unsupported version?

I also ran into and documented this issue which I think had to do with my client using some type of proxy server.

Sage 100 Registration Expiration Does Not Change or Update

@Wayne Schulz  Did your customer have an unsupported version?

I also ran into and documented this issue which I think had to do with my client using some type of proxy server.

Sage 100 Registration Expiration Does Not Change or Update

This was in February 2025 and I believe they were on v2022 Premium. As of Feb 2025 I think v2024, 2023 and 2022 were supported. I would not lean toward Sage intentionally shutting down licensing unless they did not have a TLS 1.2 option for the older version ( which I believe 2022+ natively has).

My guesses would continue to be something blocking. If practical, try installing 2022 on your local machine and register with the customer's keys

My internal notes on this client case:

Tried these steps and could not see any change ( license did not update - did not see 

1. Had to turn off proxy on the sever - Jack thinks that Zscaler is somehow blocking the update

Further along of the KB. ( linked above ) Sage note also says - 

• TLS 1.2 is required to connect with Sage License Server. Verify Sage 100 version is not retired as retired verions used older TLS 1.0 & 1.1 which cannot connect to the Sage 100 License Server.

This does not seem to imply that Sage intentionally shuts down access. I think it implies if the version is so old that it cannot use TLS 1.2 to reach SLS OR there isn't an available patch to enable that functionality THEN you are SOL

@Wayne Schulz  Did your customer have an unsupported version?

I also ran into and documented this issue which I think had to do with my client using some type of proxy server.

Sage 100 Registration Expiration Does Not Change or Update

Thanks Wayne.  If Sage isn't intentionally shutting down access then that's great.  My stress level goes down a lot.  Worst case scenario is I install the customer unlocking keys on my office system, register it and copy the relevant files back to the live installation.

This was in February 2025 and I believe they were on v2022 Premium. As of Feb 2025 I think v2024, 2023 and 2022 were supported. I would not lean toward Sage intentionally shutting down licensing unless they did not have a TLS 1.2 option for the older version ( which I believe 2022+ natively has).

My guesses would continue to be something blocking. If practical, try installing 2022 on your local machine and register with the customer's keys

My internal notes on this client case:

Tried these steps and could not see any change ( license did not update - did not see 

1. Had to turn off proxy on the sever - Jack thinks that Zscaler is somehow blocking the update

Further along of the KB. ( linked above ) Sage note also says - 

• TLS 1.2 is required to connect with Sage License Server. Verify Sage 100 version is not retired as retired verions used older TLS 1.0 & 1.1 which cannot connect to the Sage 100 License Server.

This does not seem to imply that Sage intentionally shuts down access. I think it implies if the version is so old that it cannot use TLS 1.2 to reach SLS OR there isn't an available patch to enable that functionality THEN you are SOL

@Wayne Schulz  Did your customer have an unsupported version?

I also ran into and documented this issue which I think had to do with my client using some type of proxy server.

Sage 100 Registration Expiration Does Not Change or Update

Not very nice of Sage to hide behind the "unsupported version" explanation.  Just another reason that users need to stay current.  What kind of mods are holding them back?

Thanks Wayne.  If Sage isn't intentionally shutting down access then that's great.  My stress level goes down a lot.  Worst case scenario is I install the customer unlocking keys on my office system, register it and copy the relevant files back to the live installation.

This was in February 2025 and I believe they were on v2022 Premium. As of Feb 2025 I think v2024, 2023 and 2022 were supported. I would not lean toward Sage intentionally shutting down licensing unless they did not have a TLS 1.2 option for the older version ( which I believe 2022+ natively has).

My guesses would continue to be something blocking. If practical, try installing 2022 on your local machine and register with the customer's keys

My internal notes on this client case:

Tried these steps and could not see any change ( license did not update - did not see 

1. Had to turn off proxy on the sever - Jack thinks that Zscaler is somehow blocking the update

Further along of the KB. ( linked above ) Sage note also says - 

• TLS 1.2 is required to connect with Sage License Server. Verify Sage 100 version is not retired as retired verions used older TLS 1.0 & 1.1 which cannot connect to the Sage 100 License Server.

This does not seem to imply that Sage intentionally shuts down access. I think it implies if the version is so old that it cannot use TLS 1.2 to reach SLS OR there isn't an available patch to enable that functionality THEN you are SOL

@Wayne Schulz  Did your customer have an unsupported version?

I also ran into and documented this issue which I think had to do with my client using some type of proxy server.

Sage 100 Registration Expiration Does Not Change or Update

Jeff,

Sage , in my opinion, is hiding behind a lot of technical issues/changes. Let's start with product updates. Despite Sage 'supporting' N-2, they only issue a product update for N-1. The entire process of issuing product fixes that are freely available appears to have gone by the wayside in favor of the need to call Sage and request a waiver and then get a download. And the downloads aren't even listed which may require you to place a call to Sage just to ask if they know about an issue. And the Sage KB now appears to be sporadically updated, lacks any notation of which version(s) the article relates to and once posted the articles are seldom updated or consolidated ( see: bunches of Paperless Office articles - some of which are outdated ). The product defect with DTR stopping ( Not Responding ) only for specific Windows 11 versions and the lack of a patch and requirement to update to 64-bit. The crazy "We Love The 80s!!" Way that workstations are still installed and maintained. The lack of a fast reliable way to verify that Paperless Office drivers are installed and working. But, hey, after 25 years we got Sage to add the customer name to the installed application list.

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
CT
------------------------------


Original Message:
Sent: 08-04-2025 15:33
From: Jeff Schwenk
Subject: Sage Shutting Down License if Not a Supported Version

Not very nice of Sage to hide behind the "unsupported version" explanation.  Just another reason that users need to stay current.  What kind of mods are holding them back?

------------------------------
Jeff Schwenk
Owner
Bottomline Software, Inc.
Waynesboro VA
(540) 221-4444

Improving bottom lines for over 25 years!


Original Message:
Sent: 08-04-2025 15:12
From: Doug Higgs
Subject: Sage Shutting Down License if Not a Supported Version

Thanks Wayne.  If Sage isn't intentionally shutting down access then that's great.  My stress level goes down a lot.  Worst case scenario is I install the customer unlocking keys on my office system, register it and copy the relevant files back to the live installation.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles


Original Message:
Sent: 08-04-2025 14:15
From: Wayne Schulz
Subject: Sage Shutting Down License if Not a Supported Version

This was in February 2025 and I believe they were on v2022 Premium. As of Feb 2025 I think v2024, 2023 and 2022 were supported. I would not lean toward Sage intentionally shutting down licensing unless they did not have a TLS 1.2 option for the older version ( which I believe 2022+ natively has).

My guesses would continue to be something blocking. If practical, try installing 2022 on your local machine and register with the customer's keys

My internal notes on this client case:

Tried these steps and could not see any change ( license did not update - did not see 

1. Had to turn off proxy on the sever - Jack thinks that Zscaler is somehow blocking the update

Further along of the KB. ( linked above ) Sage note also says - 

• TLS 1.2 is required to connect with Sage License Server. Verify Sage 100 version is not retired as retired verions used older TLS 1.0 & 1.1 which cannot connect to the Sage 100 License Server.

This does not seem to imply that Sage intentionally shuts down access. I think it implies if the version is so old that it cannot use TLS 1.2 to reach SLS OR there isn't an available patch to enable that functionality THEN you are SOL

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
CT


Original Message:
Sent: 08-04-2025 14:03
From: Doug Higgs
Subject: Sage Shutting Down License if Not a Supported Version

@Wayne Schulz  Did your customer have an unsupported version?

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles


Original Message:
Sent: 08-04-2025 14:01
From: Wayne Schulz
Subject: Sage Shutting Down License if Not a Supported Version

I also ran into and documented this issue which I think had to do with my client using some type of proxy server.

Sage 100 Registration Expiration Does Not Change or Update

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
CT

Not very nice of Sage to hide behind the "unsupported version" explanation.  Just another reason that users need to stay current.  What kind of mods are holding them back?

Thanks Wayne.  If Sage isn't intentionally shutting down access then that's great.  My stress level goes down a lot.  Worst case scenario is I install the customer unlocking keys on my office system, register it and copy the relevant files back to the live installation.

This was in February 2025 and I believe they were on v2022 Premium. As of Feb 2025 I think v2024, 2023 and 2022 were supported. I would not lean toward Sage intentionally shutting down licensing unless they did not have a TLS 1.2 option for the older version ( which I believe 2022+ natively has).

My guesses would continue to be something blocking. If practical, try installing 2022 on your local machine and register with the customer's keys

My internal notes on this client case:

Tried these steps and could not see any change ( license did not update - did not see 

1. Had to turn off proxy on the sever - Jack thinks that Zscaler is somehow blocking the update

Further along of the KB. ( linked above ) Sage note also says - 

• TLS 1.2 is required to connect with Sage License Server. Verify Sage 100 version is not retired as retired verions used older TLS 1.0 & 1.1 which cannot connect to the Sage 100 License Server.

This does not seem to imply that Sage intentionally shuts down access. I think it implies if the version is so old that it cannot use TLS 1.2 to reach SLS OR there isn't an available patch to enable that functionality THEN you are SOL

@Wayne Schulz  Did your customer have an unsupported version?

I also ran into and documented this issue which I think had to do with my client using some type of proxy server.

Sage 100 Registration Expiration Does Not Change or Update

I just had this issue last week with a client on 2022 premium. Turned out it was a sage issue. After working all day on it, the next morning it was working fine. 

Ronnie Aspe seems to be the only one who understands the registration server issue.  He has assisted several times.  I am sure you have reviewed with their IT which websites need to be allowed through the firewall.  Maybe their IT has "forgotten" this conversation.

October seems like a long runway.

I just had this issue last week with a client on 2022 premium. Turned out it was a sage issue. After working all day on it, the next morning it was working fine.