As Sage has communicated to partners and customers for over a year, TLS 1.0 and 1.1 will no longer be supported by Sage License Servers beginning in October 2023. This means that Sage 100 subscription products using these older TLS protocols may not communicate with the Sage License Servers and could go into read-only mode.

Today, Sage announced they’ve developed a means to pace the impact on customers in batches. The timing of this change means that some customers will now have until March 1, 2024, when Sage expects to complete the TLS changes.

Which Sage 100 versions are already TLS 1.2 compliant?

2023.x
2022.x
2021.x
2020.1 (PU1)
2019.4 (PU4)
2018.10 (PU10)

If you are on one of these releases or higher, your Sage 100 product is already compatible with TLS 1.2 and will not be impacted by this change.

What happens to customers not using a TLS 1.2 compliant version of Sage 100 or Sage 300?

Noncompliant customers will begin receiving warnings beginning with renewals dated October 2023. The notice will say that their product subscription has expired, and they have 45 days to upgrade their product to a TLS 1.2 compliant version before it goes into read-only mode.

How is Sage pacing the impact on customers?

To minimize any business impact, Sage is pacing the TLS 1.0/1.1 deprecation in batches, which they expect to finalize by March 1, 2024. These batches’ timing, size, and allocation are still being determined.

What can customers do to prepare for the TLS 1.2 compliance requirement?

If you use a version of Sage 100 that is not TLS 1.2 compliant, you should contact your Sage partner or reseller to discuss your upgrade options.

We encourage all customers to upgrade to a TLS 1.2 compliant version of Sage 100 as soon as possible to avoid disrupting their business.

Sage 100 version 2018 users may experience problems sending email forms such as invoices or statements through Paperless Office. This issue can be sporadic or it may cause a complete shutdown of email delivery. The root cause is the lack of support for TLS 1.2+ by the 2018 ( and earlier ) versions of Sage 100.

Sage 100 v2018 uses TLS 1.0 which is an outdated protocol no longer accepted by many email providers. Versions 2019 and higher of Sage 100 provide support for TLS 1.2 and therefore won’t experience this type of error.

On November 3, 2021, Sage released a patch for Sage 100 version 2018.x which enables the use of TLS 1.2 when communicating with email servers.

Sample Sage 100 Paperless Delivery Error Message

If your email delivery fails you due to incompatible TLS levels you will see the following as part of your error message.

Connection closed by server.
Failed to read beginning of SSL/TLS record.
Failed to read incoming handshake messages. (1)
Client handshake failed.
Failed to establish TLS connection.
–SMTP_Connect
Failed to connect to SMTP server.
Failed.
–VerifySmtpLogin
–ChilkatLog

How Can I Fix Sage 100 Paperless Email Delivery Issues?

The most complete way to resolve Paperless Office email delivery issues with Sage 100 2018 is to update to Sage 100 v2021 which includes both TLS 1.2 support as well as OAuth (Open Authorization): This new option ( available for subscription versions of Sage 100 only ) is an open standard authorization protocol used to grant access using access tokens instead of sharing a user name and password.

Update – Sage released LM6026T on 11-3-2021. It may resolve this issue for those users on Sage 100 2018 as it adds the ability to use TLS 1.2 with email servers.

What If We Can’t Upgrade Sage 100 Right Away?

If you cannot upgrade your Sage 100 to the latest release there are several options available to restore the ability of your Sage 100 v2018 email capabilities.

SMTP2GO – External SMTP Email Server

The easiest way to resolve this issue is by using a third-party SMTP service like smtp2go. These types of services charge a fee for the flexibility of configuring their SMTP server to accept external email and many won’t require a specific level of TLS.

With an external SMTP server, you’ll swap in the external server’s address and configure Sage 100 to send all email

SMTP Relay Using An Office 365 Connector

SMTP relay lets Microsoft 365 or Office 365 relay emails on your behalf by using a connector that’s configured with your public IP address or a TLS certificate.

Follow these instructions to create an SMTP relay if you are using Office 365.

Wait For A Sage Patch for Sage 100 2018

Sage has indicated they are working on a patch for Sage 100 2018. This is likely the only version that will receive a patch and even with the patch to allow for TLS 1.2 compatibility the version 2018 release still lacks OAuth which may soon be required to connect an email to Microsoft Office 365.

The issue that many on older versions of Sage 100 have experienced underscores the importance of remaining current on Sage 100. If you have not updated we recommend doing so as soon as practical and adopting version 2021 or higher for maximum compatibility with future technology.

Sage TLS 1.2 Change Deferred For Some Through March 2024

Sage 100 2018 Paperless Email Delivery Problems?