Sage 100

Alright here is another gotcha for those payroll clients. If you notice when upgrading or entering new keys because of the payroll subscription, if you see 2 keys on the portal do not enter the sub payroll ones. They put my clients system in a trial demo to expire in 30 days and I can't get into Library master at all. Sage has to generate new keys and I will have to hack to get them installed. Also found out their is a Server A that I guess generates the keys and in about 48 hours Server B looks for the keys and updates the system to the new date for expiration.

What a cluster...

What file are the keys stored in? I'm thinking a backup before entering new keys would be a good idea.

SY_SYSTEM

So very irritated with Sage right now. We had a customer who is 100c and payroll sub. They had multiple keys out there too. When we enter the 100c ones they don't have access to payroll. When we called Sage support about it they said we had to enter the 100c keys then activate it, then enter the PR sub keys and activate those (apparently they have been telling other customers to do that). Of course, just like Kelly said, now they can't get into anything because their trial period expired. I've hacked them back to the keys that don't give them payroll and am waiting for Sage to pick up the call. GRRR!!

First I'm aware that there are separate payroll keys - the last few I did I just put in the new keys and everything activated. Sage actually pushed out a new key on one that had elected to drop a module and some users.

Sage generated new keys but there still seems to be a problem because the *info PR Expiration date says 10/29/16 instead of their actual PR Sub expiration date. Sage wants to wait till tomorrow and test the keys because they think it might reach out to the server and then extend the expiration date out another 30 days. None of these dates relate at all to any of the customers actual expiration dates for 100c or PR sub.

Carmen at Sage Support told me there are 2 servers and server A creates the keys and server B comes around, something like 24-48 hours and validates the keys and will change the date. If they are on a Payroll subscription (month to month) it will throw it out 30 days and then keep refreshing as payment is posted. If they paid the Payroll subscription for the year the date will reflect next year payroll renewal date. if a month to month some time (unknown exactly) if that monthly payment is not met, there will be a warning so many days left to access payroll module.

Thanks @KellySappington! I hope that happens now that we have good keys from Sage.