Sage 100

Copied from Wayne's post on the topic.

Sage 100 2015.5 - LM5200T (for customers with a payroll subscription )

Sage 100 2016.2 to 2016.5 - LM5034T

Sage 100 2017.0 to 2017.6 - LM5035T

Sage 100 2018.0 to 2018.10 - LM6030T

Sage 100 2019.0 to 2019.5 - LM6126T

Wayne's original post:

https://community.90minds.com/discussion/sage-releases-tls-12-patches-for-v2016-to-2019

Copied from Wayne's post on the topic.

Sage 100 2015.5 - LM5200T (for customers with a payroll subscription )

Sage 100 2016.2 to 2016.5 - LM5034T

Sage 100 2017.0 to 2017.6 - LM5035T

Sage 100 2018.0 to 2018.10 - LM6030T

Sage 100 2019.0 to 2019.5 - LM6126T

I grabbed them all and can share a link to my Google Drive if needed. 

Anyone have any problems installing these on older (2017, 2018) Sage versions?

I grabbed them all and can share a link to my Google Drive if needed. 

@Lee Graham I have to install also on various customers...any feedback of known issues when installing these fixes???

Anyone have any problems installing these on older (2017, 2018) Sage versions?

@Lee Graham I have to install also on various customers...any feedback of known issues when installing these fixes???

Anyone have any problems installing these on older (2017, 2018) Sage versions?

I grabbed them all and can share a link to my Google Drive if needed. 

I installed a 2018 system. I have no idea how to test it!

@Lee Graham I have to install also on various customers...any feedback of known issues when installing these fixes???

Anyone have any problems installing these on older (2017, 2018) Sage versions?

I grabbed them all and can share a link to my Google Drive if needed. 

I believe you can only test the license server connection for new TLS in coordination with Sage's assistance.

I installed a 2018 system. I have no idea how to test it!

@Lee Graham I have to install also on various customers...any feedback of known issues when installing these fixes???

Anyone have any problems installing these on older (2017, 2018) Sage versions?

I grabbed them all and can share a link to my Google Drive if needed. 

Well...but at least the system is running with the fix installed... that is a step ahead...

I believe you can only test the license server connection for new TLS in coordination with Sage's assistance.

I installed a 2018 system. I have no idea how to test it!

@Lee Graham I have to install also on various customers...any feedback of known issues when installing these fixes???

Anyone have any problems installing these on older (2017, 2018) Sage versions?

I grabbed them all and can share a link to my Google Drive if needed. 

I installed a 2018 system. I have no idea how to test it!

@Lee Graham I have to install also on various customers...any feedback of known issues when installing these fixes???

Anyone have any problems installing these on older (2017, 2018) Sage versions?

I grabbed them all and can share a link to my Google Drive if needed. 

Getting all of the different customers upgraded to TLS 1.2 hasn't been too difficult except for one installation that IS NOT supposed to require a patch.  According to the compatibility matrix provided by Sage, version 6.20.1 is compatible "as is."  However, Sage says that this customer still pings TLS 1.

The Sage techs say this could be because it's finding an old test server or if they have Payroll and it isn't  updated.  I have confirmed that neither of these is the case. 

This system has been upgraded many times since the first install in 2006 and the Module Listing does show some old modules that aren't really installed. These include things like the old Sage Software Extended Solutions (ESLM) and the Customers with National Accounts (AR1068) but these are ghost records because they aren't really installed anymore.

The system also has AvaTax Connect and Repay installed.

Does anyone have any idea why this customer might be pinging the old TLS?

Interesting - I just had that pop up today.  I'm having IT check it out because it was on a 2012 server and they just recently updated to Windows 2019 (just updated the OS - same server), so wondering if tls just isn't set to default to 1.2.

Getting all of the different customers upgraded to TLS 1.2 hasn't been too difficult except for one installation that IS NOT supposed to require a patch.  According to the compatibility matrix provided by Sage, version 6.20.1 is compatible "as is."  However, Sage says that this customer still pings TLS 1.

The Sage techs say this could be because it's finding an old test server or if they have Payroll and it isn't  updated.  I have confirmed that neither of these is the case. 

This system has been upgraded many times since the first install in 2006 and the Module Listing does show some old modules that aren't really installed. These include things like the old Sage Software Extended Solutions (ESLM) and the Customers with National Accounts (AR1068) but these are ghost records because they aren't really installed anymore.

The system also has AvaTax Connect and Repay installed.

Does anyone have any idea why this customer might be pinging the old TLS?

This is a Windows 2016 Terminal Server environment.  Both the file server and the terminal server have their security set with TLS 1.0, TLS 1.1, and TLS 1.2 turned on. So, I find it hard to believe that it's the server.

Interesting - I just had that pop up today.  I'm having IT check it out because it was on a 2012 server and they just recently updated to Windows 2019 (just updated the OS - same server), so wondering if tls just isn't set to default to 1.2.

Getting all of the different customers upgraded to TLS 1.2 hasn't been too difficult except for one installation that IS NOT supposed to require a patch.  According to the compatibility matrix provided by Sage, version 6.20.1 is compatible "as is."  However, Sage says that this customer still pings TLS 1.

The Sage techs say this could be because it's finding an old test server or if they have Payroll and it isn't  updated.  I have confirmed that neither of these is the case. 

This system has been upgraded many times since the first install in 2006 and the Module Listing does show some old modules that aren't really installed. These include things like the old Sage Software Extended Solutions (ESLM) and the Customers with National Accounts (AR1068) but these are ghost records because they aren't really installed anymore.

The system also has AvaTax Connect and Repay installed.

Does anyone have any idea why this customer might be pinging the old TLS?

Getting all of the different customers upgraded to TLS 1.2 hasn't been too difficult except for one installation that IS NOT supposed to require a patch.  According to the compatibility matrix provided by Sage, version 6.20.1 is compatible "as is."  However, Sage says that this customer still pings TLS 1.

The Sage techs say this could be because it's finding an old test server or if they have Payroll and it isn't  updated.  I have confirmed that neither of these is the case. 

This system has been upgraded many times since the first install in 2006 and the Module Listing does show some old modules that aren't really installed. These include things like the old Sage Software Extended Solutions (ESLM) and the Customers with National Accounts (AR1068) but these are ghost records because they aren't really installed anymore.

The system also has AvaTax Connect and Repay installed.

Does anyone have any idea why this customer might be pinging the old TLS?

------------------------------
Chuck Peddy
Smartbridge Partners
------------------------------

Check that Windows has TLS 1.2 installed and active.  (For older versions of Windows, it was an option). 

Sage 100 can't use it if it isn't installed and active on the server / workstation.

Edit:

We ran into that problem in a few places when Paya made TLS 1.2 mandatory, and random machines had to get fixed by customer IT.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------


Original Message:
Sent: 09-11-2023 16:49
From: Chuck Peddy
Subject: tls hot fix for unsupported versions

Getting all of the different customers upgraded to TLS 1.2 hasn't been too difficult except for one installation that IS NOT supposed to require a patch.  According to the compatibility matrix provided by Sage, version 6.20.1 is compatible "as is."  However, Sage says that this customer still pings TLS 1.

The Sage techs say this could be because it's finding an old test server or if they have Payroll and it isn't  updated.  I have confirmed that neither of these is the case. 

This system has been upgraded many times since the first install in 2006 and the Module Listing does show some old modules that aren't really installed. These include things like the old Sage Software Extended Solutions (ESLM) and the Customers with National Accounts (AR1068) but these are ghost records because they aren't really installed anymore.

The system also has AvaTax Connect and Repay installed.

Does anyone have any idea why this customer might be pinging the old TLS?

------------------------------
Chuck Peddy
Smartbridge Partners

@Jeff Fiddelman, LM6028T?

Check that Windows has TLS 1.2 installed and active.  (For older versions of Windows, it was an option). 

Sage 100 can't use it if it isn't installed and active on the server / workstation.

Edit:

We ran into that problem in a few places when Paya made TLS 1.2 mandatory, and random machines had to get fixed by customer IT.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 09-11-2023 16:49
From: Chuck Peddy
Subject: tls hot fix for unsupported versions

Getting all of the different customers upgraded to TLS 1.2 hasn't been too difficult except for one installation that IS NOT supposed to require a patch.  According to the compatibility matrix provided by Sage, version 6.20.1 is compatible "as is."  However, Sage says that this customer still pings TLS 1.

The Sage techs say this could be because it's finding an old test server or if they have Payroll and it isn't  updated.  I have confirmed that neither of these is the case. 

This system has been upgraded many times since the first install in 2006 and the Module Listing does show some old modules that aren't really installed. These include things like the old Sage Software Extended Solutions (ESLM) and the Customers with National Accounts (AR1068) but these are ghost records because they aren't really installed anymore.

The system also has AvaTax Connect and Repay installed.

Does anyone have any idea why this customer might be pinging the old TLS?

------------------------------
Chuck Peddy
Smartbridge Partners

Getting all of the different customers upgraded to TLS 1.2 hasn't been too difficult except for one installation that IS NOT supposed to require a patch.  According to the compatibility matrix provided by Sage, version 6.20.1 is compatible "as is."  However, Sage says that this customer still pings TLS 1.

The Sage techs say this could be because it's finding an old test server or if they have Payroll and it isn't  updated.  I have confirmed that neither of these is the case. 

This system has been upgraded many times since the first install in 2006 and the Module Listing does show some old modules that aren't really installed. These include things like the old Sage Software Extended Solutions (ESLM) and the Customers with National Accounts (AR1068) but these are ghost records because they aren't really installed anymore.

The system also has AvaTax Connect and Repay installed.

Does anyone have any idea why this customer might be pinging the old TLS?

I seem to recall ta KB entry within Sage that advises an additional way to test whether TLS 1.2 is enabled. A brief search failed to uncover it so maybe it's somewhere in the download KB or Sage pulled it.

Getting all of the different customers upgraded to TLS 1.2 hasn't been too difficult except for one installation that IS NOT supposed to require a patch.  According to the compatibility matrix provided by Sage, version 6.20.1 is compatible "as is."  However, Sage says that this customer still pings TLS 1.

The Sage techs say this could be because it's finding an old test server or if they have Payroll and it isn't  updated.  I have confirmed that neither of these is the case. 

This system has been upgraded many times since the first install in 2006 and the Module Listing does show some old modules that aren't really installed. These include things like the old Sage Software Extended Solutions (ESLM) and the Customers with National Accounts (AR1068) but these are ghost records because they aren't really installed anymore.

The system also has AvaTax Connect and Repay installed.

Does anyone have any idea why this customer might be pinging the old TLS?

One of my notes included this site which seems to test for TLS though I cannot for sure say that it's going to be helpful in every situation - https://www.howsmyssl.com/

I seem to recall ta KB entry within Sage that advises an additional way to test whether TLS 1.2 is enabled. A brief search failed to uncover it so maybe it's somewhere in the download KB or Sage pulled it.

Getting all of the different customers upgraded to TLS 1.2 hasn't been too difficult except for one installation that IS NOT supposed to require a patch.  According to the compatibility matrix provided by Sage, version 6.20.1 is compatible "as is."  However, Sage says that this customer still pings TLS 1.

The Sage techs say this could be because it's finding an old test server or if they have Payroll and it isn't  updated.  I have confirmed that neither of these is the case. 

This system has been upgraded many times since the first install in 2006 and the Module Listing does show some old modules that aren't really installed. These include things like the old Sage Software Extended Solutions (ESLM) and the Customers with National Accounts (AR1068) but these are ghost records because they aren't really installed anymore.

The system also has AvaTax Connect and Repay installed.

Does anyone have any idea why this customer might be pinging the old TLS?

Doh!, bad KB searching on my part.  Thanks, @Steve Iwanowski.

One of my notes included this site which seems to test for TLS though I cannot for sure say that it's going to be helpful in every situation - https://www.howsmyssl.com/

I seem to recall ta KB entry within Sage that advises an additional way to test whether TLS 1.2 is enabled. A brief search failed to uncover it so maybe it's somewhere in the download KB or Sage pulled it.

Getting all of the different customers upgraded to TLS 1.2 hasn't been too difficult except for one installation that IS NOT supposed to require a patch.  According to the compatibility matrix provided by Sage, version 6.20.1 is compatible "as is."  However, Sage says that this customer still pings TLS 1.

The Sage techs say this could be because it's finding an old test server or if they have Payroll and it isn't  updated.  I have confirmed that neither of these is the case. 

This system has been upgraded many times since the first install in 2006 and the Module Listing does show some old modules that aren't really installed. These include things like the old Sage Software Extended Solutions (ESLM) and the Customers with National Accounts (AR1068) but these are ghost records because they aren't really installed anymore.

The system also has AvaTax Connect and Repay installed.

Does anyone have any idea why this customer might be pinging the old TLS?

I had the same problem at first @Brett Zimmerman!

Now I need to see about applying that patch or the product updates.  No matter what I do, I'm going to have to reinstall Avatax Connect and Repay so that everything plays nice together.

Doh!, bad KB searching on my part.  Thanks, @Steve Iwanowski.

One of my notes included this site which seems to test for TLS though I cannot for sure say that it's going to be helpful in every situation - https://www.howsmyssl.com/

I seem to recall ta KB entry within Sage that advises an additional way to test whether TLS 1.2 is enabled. A brief search failed to uncover it so maybe it's somewhere in the download KB or Sage pulled it.

Getting all of the different customers upgraded to TLS 1.2 hasn't been too difficult except for one installation that IS NOT supposed to require a patch.  According to the compatibility matrix provided by Sage, version 6.20.1 is compatible "as is."  However, Sage says that this customer still pings TLS 1.

The Sage techs say this could be because it's finding an old test server or if they have Payroll and it isn't  updated.  I have confirmed that neither of these is the case. 

This system has been upgraded many times since the first install in 2006 and the Module Listing does show some old modules that aren't really installed. These include things like the old Sage Software Extended Solutions (ESLM) and the Customers with National Accounts (AR1068) but these are ghost records because they aren't really installed anymore.

The system also has AvaTax Connect and Repay installed.

Does anyone have any idea why this customer might be pinging the old TLS?

I'm thinking the hot-fix might not need to have enhancements reinstalled, since it only affects three files.

I had the same problem at first @Brett Zimmerman!

Now I need to see about applying that patch or the product updates.  No matter what I do, I'm going to have to reinstall Avatax Connect and Repay so that everything plays nice together.

Doh!, bad KB searching on my part.  Thanks, @Steve Iwanowski.

One of my notes included this site which seems to test for TLS though I cannot for sure say that it's going to be helpful in every situation - https://www.howsmyssl.com/

I seem to recall ta KB entry within Sage that advises an additional way to test whether TLS 1.2 is enabled. A brief search failed to uncover it so maybe it's somewhere in the download KB or Sage pulled it.

Getting all of the different customers upgraded to TLS 1.2 hasn't been too difficult except for one installation that IS NOT supposed to require a patch.  According to the compatibility matrix provided by Sage, version 6.20.1 is compatible "as is."  However, Sage says that this customer still pings TLS 1.

The Sage techs say this could be because it's finding an old test server or if they have Payroll and it isn't  updated.  I have confirmed that neither of these is the case. 

This system has been upgraded many times since the first install in 2006 and the Module Listing does show some old modules that aren't really installed. These include things like the old Sage Software Extended Solutions (ESLM) and the Customers with National Accounts (AR1068) but these are ghost records because they aren't really installed anymore.

The system also has AvaTax Connect and Repay installed.

Does anyone have any idea why this customer might be pinging the old TLS?

@Kevin Moyes, I applied that patch last night and have received no complaints this morning.  Now I just need to have Sage ping them again to be sure that it's responding correctly.  Thank you for the help!

I'm thinking the hot-fix might not need to have enhancements reinstalled, since it only affects three files.

I had the same problem at first @Brett Zimmerman!

Now I need to see about applying that patch or the product updates.  No matter what I do, I'm going to have to reinstall Avatax Connect and Repay so that everything plays nice together.

Doh!, bad KB searching on my part.  Thanks, @Steve Iwanowski.

One of my notes included this site which seems to test for TLS though I cannot for sure say that it's going to be helpful in every situation - https://www.howsmyssl.com/

I seem to recall ta KB entry within Sage that advises an additional way to test whether TLS 1.2 is enabled. A brief search failed to uncover it so maybe it's somewhere in the download KB or Sage pulled it.

Getting all of the different customers upgraded to TLS 1.2 hasn't been too difficult except for one installation that IS NOT supposed to require a patch.  According to the compatibility matrix provided by Sage, version 6.20.1 is compatible "as is."  However, Sage says that this customer still pings TLS 1.

The Sage techs say this could be because it's finding an old test server or if they have Payroll and it isn't  updated.  I have confirmed that neither of these is the case. 

This system has been upgraded many times since the first install in 2006 and the Module Listing does show some old modules that aren't really installed. These include things like the old Sage Software Extended Solutions (ESLM) and the Customers with National Accounts (AR1068) but these are ghost records because they aren't really installed anymore.

The system also has AvaTax Connect and Repay installed.

Does anyone have any idea why this customer might be pinging the old TLS?