Sage 100

**Sage 100 Payroll module expiration issues** _**The hot fix is different for Customers vs. Partners/SAN**_ From: Lavalais, Kalillya [mailto:Kalillya.Lavalais@sage.com] Sent: Monday, May 8, 2017 8:51 AM Subject: Payroll Expiration Issues Please review the following before escalating these type of expiration date issues. **Partners and SAN members** oHave a NFR License which does not contact the SLS servers for entitlement oProduct had a hard coded date to end entitlement on 4/30 in the System Configuration, Modules tab or *info. oAfter the expiration date you receive the following message with an expiration date including the 45 day grace period. Example: ""Your payroll subscription has expired you can continue processing payroll for 45 days. Please contact Sage before xx/xx/xxxx to renew your subscription"" oA communication to Partners was in Sage Sells regarding a patch that needs to be installed to adjust the date (date we change to depends on the version of the software they are using) oThe SAN team sent a communication to their customers with the same information oPartners and SAN members need to go to KB ID 82689 to install the appropriate patch oThe following patches are only for Partners/SAN. All partners/SAN have NFR licenses. **Customers do not have a NFR License. oThis is only for following versions and expiration date is based on the version per KB ID 82689 5.20.3 and 5.20.4 use LM5023-t 5.20.5 use LM5022-t 5.30.1 use LM5021-t 5.30.2 use LM5020-t 5.30.3 use LM5019-t 5.30.4 use LM5018-t 5.40.1 use LM5017-t ****After installation of hotfix, go to Library Master, Setup, System Configuration and Select the Update button or (Edit, Activate buttons on 2016.4 and 2017.1) oSome of these patches may also be used for Customers (Without NFR) that need the read-only access if they are not purchasing the Payroll Subscription. =============================================== **Customers (anybody who DOES NOT have an NFR* license)** oKB ID 68454 is applicable to this group of customers oProduct had a hard coded date to end entitlement on 4/30 in the System Configuration, Modules tab. oAfter the expiration date you receive the following message with an expiration date including the 45 day grace period. Example: ""Your payroll subscription has expired you can continue processing payroll for 45 days. Please contact Sage before xx/xx/xxxx to renew your subscription"" oCustomers on versions 5.20.5, 5.30.2, 5.40.0 and higher already have the ability to update the expiration date on their Payroll Subscription from the SLS server. oCustomers on the following versions use Hotfixes per KB ID 83158 to enable the extended 8/1/17 date to be updated. 5.20.3 use LM5026-t 5.20.4 use LM5025-t 5.30.1 use LM5024-t ****After installation of hotfix, go to Library Master, Setup, System Configuration and Select the Update button or (Edit, Activate buttons on 2016.4 and 2017.1) oUpdating their keys is a 2-step process. We are initially updating with a date in May to give the Cloud Enablement team time to write a script to update to 8/1/2017 oThis first update should take place by the end of this week to turn off the message customers may be receiving today oInternet access is needed to perform the expiration update. If no internet access, customer must contact Sales Advisors at Extension #340808 to have keys regenerated with the new expiration date of 8/1/2017.

Oh yeah, having this crap going on this week is SUCH good timing.

Any advise on quickly getting the BSAN/SAN codes since they removed them from the portal and you can't get through to Sage? We are getting slammed with calls and I thought they were changing the dates till August or was that just speculation? I hope everyone rips them a new one at Summit!

What codes are you referring to, @PamScott? You should just need to install the applicable hot-fix, which for customers it extends the expiration date to 8-1-17, and for Partners/SAN it appears it extends it to 12-31-2018 (at least according to the hot-fix .pdf).

Let me check with the team and I'll see why they are thinking they need them. Thanks, Pam

Fyi, I just confirmed that the *info screen now shows a 12-31-18 P/R Expiration Date for the SAN client I just installed the hot-fix for.

What a cluster. And of course on a day when travelling.

_**Some more info from Sage:**_ From: Leary, Carl [mailto:Carl.Leary@sage.com] Sent: Monday, May 8, 2017 12:19 PM Subject: Update on payroll issues Importance: High This is for customers that are current on the payroll subscription, but getting the errors directly from my Product Mgmt Team: Based on the message appearing on the customer's system, they are still using the temporary license keys with an expiration date of 5/20/2017. It appears they are not using the new keys that would have been generated when they purchased their actual subscription. My advice is that we work with these customers to obtain the correct licensing keys. There are knowledgebase articles on how to apply a Hot Fix to install the code to connect the system to the registration server if they are not on a version that already includes that connection. Then they simply need to download the correct information from the licensing server. Please also check to see which version these customers are on. If they are on 2015.3, 2015.4 or 2016.1, they need to apply a recent hotfix to get the software to update their expiration date. If they are on a more recent version, verify that they have Internet access or they won't be able to get to the Entitlement Server to get a new expiration date. Finally, check the Customer Entitlement database to see what the Payroll Subscription expiration date is set to. If the date is set correctly, there is an Internet connectivity issue. If the date is not set correctly, you may need to re-sync the customer after verifying the correct subscription date. Hope this helps.

I noticed that the P/R Expiration Date in *info says 2-16-18 for one of our clients who we installed the hot fix for yesterday. I was expecting to see 8-1-17. I'm wondering what others are seeing.

Apparently we're seeing a lot of different dates in *info after installing the hot fix for clients (""customers""). One thought was that maybe the 'Update/re-Activate' after installation wasn't performed, however I would then expect the P/R Expiration box/message to still be appearing. I guess it's possible that Sage has already put in place whatever they planned to so that the correct P/R Exp Date is present in the clients' systems. I guess time will tell. We had at least one situation where *info still showed a 4-30-17 Exp Date after installing the hot fix, and Sage had to provide an sy_sessions file (specific to that Sage 100 version) to fix it. The client still gets the date warning but can at least process until the end of May while Sage is addressing this particular issue. Not sure why the hot fix didn't work for them, but Sage has seen this before.

That also happened to one of my clients. It took the sy_sessions file for them to use Payroll.

We're also seeing some expected 8-1-17 expiration dates. A bit interesting that we're seeing mixed results. I wonder if the version of Sage 100 has anything to do with it.

Apparently there is a patch for read-only access for clients who do not plan on going to Tiered P/R, at least according to someone at Summit, Does anyone have that patch or know where to find it?

For Accountant/NFR copies: https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=82689&sliceId=2&cmd=&noCount=true&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl I think they blurted out the KB entry for the customer version but I didn't catch it. Maybe someone else in the session caught it and can update this post.

I _think_ you can disregard my last post re: read-only access. It _appears_ that KB #82689 (attached), which is specific to Partners and SAN, can be used for ""customers"" needing read-only access - at least that's what it _appears_. Can this be any more confusing?! (@WayneSchulz, the #82689 is in the link you just posted.)

I just heard that the apparent ""read-only"" patch didn't appear to work, at least for one client that it was tried. Anyone else have feedback on this?

I'm pretty certain @MaryJoKrueger did an upgrade recently and the ""read-only"" patch worked for them to still look at PR. Their PR expired last year, they never went on a PR Sub plan.

Jenny's right. I installed it a couple of weeks ago for a client who dropped maintenance because they're outsourcing. They're still able to get in and get at the data. When I followed up with him a few days later he said ""I performed a very short test and it appears to be working."" I don't know what his testing consisted of.