Sage 100 Price Changes Effective January 1, 2023

September 21, 2022 by Wayne Schulz Leave a Comment

Sage announced a changed to their Sage 100 price list which will take effect January 1, 2023. Pricing will change by up to 10% with most customers seeing around a 4% change.

Sage 100 and Sage 300 price changes

Given the high rate of inflation and the need to continually fund investment in the ,products, effective January 1, 2023, the following pricing changes will be going into effect for Sage 100 and Sage 300:

• Perpetual and M&S customers

Increasing 7%

• Subscription customers:

“Cloud” price list: Increasing 4%
“C” price list: Increasing 7%
Any customer below list price: Increase up to 10%

• Sage 100 and Sage 300 Payroll:

Eliminating “one-time set-up fee”
Increasing 7%

Note: We will be eliminating the “c” price list during FY23 and moving customers to the “cloud” price list. This will start with Sage 300 in October, followed by Sage 100 in the Spring. We will limit the increase of “c” customers currently at list price to 7%.

Current customers will see these increases reflected in their renewal notices, beginning in October.

Microsoft Offers One-Time Re-Enablement of Basic Authentication Through 12/31/2022

September 5, 2022 by Wayne Schulz Leave a Comment

According to a September 1, 2022 blog post, Microsoft will allow a one time extension through 12/31/2022 users who have not yet met the requirement to use OAuth for more secure login to MAPI, RPC, Offline Address Book (OAB), Exchange Web Services (EWS), POP, IMAP, Exchange ActiveSync (EAS), and Remote PowerShell.

Furthermore, in a 9-9-2022 blog post Microsoft clarifies that SMTP AUTH will NOT be disabled for active users of the authentication method. The company does urge users to adopt OAuth as a more secure method but clarifies that SMTP AUTH is not shutting down. At least not as of 9/9/2022.

From Microsoft blog post 9-1-2022
One-Time Re-Enablement
Today we are announcing an update to our plan to offer customers who are unaware or are not ready for this change.
When we turn off basic auth after October 1st, all customers will be able to use the self-service diagnostic to re-enable basic auth for any protocols they need, once per protocol. Details on this process are below.
Once this diagnostic is run, basic auth will be re-enabled for those protocol(s). Selected protocol(s) will stay enabled for basic auth use until end of December 2022. During the first week of calendar year 2023, those protocols will be disabled for basic auth use permanently, and there will be no possibility of using basic auth after that.

For more information on the Microsoft OAuth requirements please visit their website here.

The following Sage 100 versions currently meet the requirement use OAuth with Microsoft.

2021.4+
2022.1+

Sage Sets Summer 2023 Deadline for Sage 100 TLS 1.2 Requirement

July 25, 2022 by Wayne Schulz

Sage has begun to contact customers via their online knowledgebase and alert them about an upcoming change. In order for your Sage 100 accounting software to continue contacting the Sage licensing servers you must be on a supported version of Sage 100.

From the Sage KB 116278

In the summer of 2023, Sage will be making changes to your license verification to utilize a current Transport Layer Security (TLS) protocol recommended by third-party standards organizations. This measure is required as older versions of TLS do not meet current security standards and can pose a security risk. If you have a subscription business care plan and are not on a Supported Version of Sage 100, your software will convert to read-only mode.

What does this mean?:

Sage will be updating their internal licensing servers to use TLS 1.2. This is a a widely adopted security protocol designed to facilitate privacy and data security for communications over the Internet.

Previous versions ( prior to Sage 100 2019 ) utilize only older TLS 1.0 or 1.1. Starting in the summer of 2023 you will need to be on a supported version of Sage 100 which offers TLS 1.2 or your ability to maintain a license is jeopardized as Sage states that those who are not on current versions will find their system converted to a read-only mode.

Recommendation:

Our recommendation is upgrade to Sage 100 2021.4+ or 2022.1+ for maximum compatibility.

Resources:

Using Microsoft Exchange with Sage 100 and Paperless Office ( KB 116280)
Sage 100 product licensing and Transport Layer Security ( KB 116278 )

Sage 100 Supported Versions

Sage Issues Patch for “Unable to draw folder control” Issue in 2022.1 and 2021.4

July 18, 2022 by Wayne Schulz

Sage today issued a pair of patches which address what appears to be a bug with Custom Office enhanced screens which have an additional tab. During the application of Sage 1002 2022 product update 1 or Sage 100 20221 product update 4 users impacted by this bug saw an error “Unable to draw folder control”.

This was first reported in this Sage City post – Error Unable to draw Folder control – Issue with customized panels in 2022 Product update 1

Sage issued patches for both Sage 100 2022.1 and Sage 100 2021.4 which resolves this issue. No other versions of Sage 100 were impacted by the bug.

Important Information For Sage 100 Users About OAuth and TLS

July 6, 2022 by Wayne Schulz

By October 1, 2021 users of Sage 100 should be on versions 2021.4 / 2022.1 or higher if they are using Microsoft to send email through paperless office. This is due to Microsoft requiring OAuth for all API endpoints such as Exchange on-line and Office 365 email tenants.

In addition, Sage will no longer support TLS 1.0 or 1.1 effective by the end of the summer 2023. This is of more concern since a broader array of integrations may require TLS 1.2.

For TLS compatibility you should be on Sage 100 2019.4 or higher although we strongly recommend that you adopt the same requirements as OAuth as noted above which requires Sage 100 2021.4+ or Sage 100 2022.1+ no later than October 1, 2022.

Sage 100 & 300 Alert

By October 1, 2021 – Upgrade to at least 2021.4+ or 2022.1+ in order to maintain compatibility with Microsoft OAuth which will be required to use Microsoft email for sending documents from Sage 100. By upgrading to one of the above versions you will also meet the TLS 1.2 requirements.

What if I don’t upgrade by October 1, 2021? – You lose the ability to send email through Microsoft’s servers using a simple login and password.

By Summer 2023 – Upgrade to at least 2021.4 or 2022.1 in order to maintain compatibility with TLS 1.2 requirements for communicating with Sage. Note that if you are not sending email through a provider who requires OAuth you can upgrade to Sage 100 2019.4 as the minimum compatible level for TLS 1.2.

What if I’m not on 2021.4, 2022.1 or 2019.4 by Summer 2023? You will lose the ability to communicate to Sage using TLS 1.2 and your system will enter a read-only status.

We recommend strongly that you adopted either 2021.4+ or (preferred) 2022.1+ prior to October 1, 2022 for maximum compatibility with the changes noted above.

See also – Sage 100 FAQ on OAuth and TLS 1.2