Sage 100

Heads Up on Sage 100 2018 Conversions: **The encryption key is invalid. See your system administrator.** **Products** Sage 100 **Description** The encryption key is invalid. See your system administrator. **Cause** Copying MAS_XXX (XXX=Company Code) data into the MAS90 folder of Sage 100 2018 installation. Installing Sage 2018 in the same location as any prior installation and not removing the MAS90 folder prior to the installation. **Resolution** Remove the MAS_XXX folder that was copied into the Sage 100 2018 Mas90 directory. Do NOT copy only MAS_XXX data under the MAS90 directory as done in 2017 and prior versions. **Due to the encryption in version 2018, this will not work.** Must also copy **MAS_System folder** when attempting to bring data into version 2018. Uninstall the Sage 100 2018, remove the MAS90 folder and anything in it prior to reinstall. Do NOT install version 2018 over an existing MAS90 directory from a prior installation. [Source](https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=87143&sliceId=1&cmd=displayKC&dialogID=132547&docType=kc&isLoadPublishedVer=&stateId=132549&docTypeID=DT_Article&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl) #2018pioneer

This appears to be a new limitation on final conversions of data. In some (many?) cases we skip another migration of the data (including system files) and just copy over the MAS_XXX data and have Sage go through a final conversion. That still leaves paperless to contend with but in some cases, the customer isn't using paperless or we use alternate ways to copy and merge paperless. I'm not entirely certain exactly what steps the Sage KB is suggesting. It appears to say that you must also bring over MAS_SYSTEM. I don't know what problems this might (or might not) cause. FYI - just a note for anyone who is contemplating a 2018 upgrade. In all likelihood, you wouldn't run into this until undergoing the final conversion on a Sunday night with a customer expecting to be live Monday at 8 am ...

Encryption of what?

Sage added encryption keys which you can change to protect additional data fields

I'm hoping that if you use the migration utilities you can still migrate ONLY the company data during the live upgrade and skip the system files that you (we) already migrated during the pilot upgrade. The bigger problem I see is all those CPAs, accountants and bookkeepers who take copies of their customers MAS_XXX data files back to their offices for write-up work.

Here's one spot where Sage talks about the new encryption - http://help-sage100.na.sage.com/2018/index.htm#Subsystems/PR/Concept/Security_for_PII.htm#kanchor80

To change the encryption key Log on to Sage 100 using the Administrator account. In the Administrative Tools window, click Personally Identifiable Information. In the Change PII Encryption Key window, enter the new key in both fields. For more information, see Change PII Encryption Key - Fields. Click OK. The encryption key is changed.

Huh, I never noticed that as a new feature, thanks Wayne!

It's borderline gross negligence that Sage doesn't mention this on a partner ""welcome to Sage 100 2018 - here's what's new"" call.

@WayneSchulz - stay in your lane! What's even better is that as of yesterday there was still no documents for v2018 in the Sage 100 Playbook on Sage Sell. In fact, there is no mention of Sage 100 v2018 on Sage Sell. How good is that???

That's pretty similar to how things rolled out last year (poorly). There is an updated SPM.

Wow, this is a super PITA. Copying the MAS_xxx folder has been the standard way of doing the final conversion on a Sunday night...... And the CPA's who have been picking up PR business (and resellers) because end user doesn't want to pay the extra coin to Sage now so they drop PR and send the PRxxx files over.... As I said, wow! Sage isn't expecting the vast majority of PR users to convert prior to year end so maybe they will have something in the playbook by January, 2018.

I am asking Sage dev about this and will update if/when something substantive comes back from them.

That will create a nightmare! I also wish they would give us more time to absorb new levels before they send emails to the clients. I have received emails all week, ""do we have to upgrade again"" and ""will we need this to get through year end""? I believe the clients should be informed however their emails are more intimidating to my clients than help. Thanks for the info!

If you have not in the past, I urge all of you to provide feedback to your PAMs about Sage bypassing the channel and creating confusion for the customer. I also ask that you request Scott Ehmen be on your next call with your PAM, if possible. Sage is not listening to the people who know best about the sh*t storm they keep fueling.

Can't wait for MOTM 2018 in February for the Sage sessions. Should be a very interesting time.

And I just thought of another ""ouch"". At YE, I process w2's for about 10 clients. Used to pull their PRxxx folder over to my system. Guess that will be changing once they eventually move to v2018.

According to our development team via other Master Developer resources, this PII change was applied to the Payroll module for now, and may be applied to other files in the future. It is also set up so that Master Developers may make use of it as well. So this only applies for 2018 for Payroll. Other data modules can be copied for testing/report writing, etc. I guess this means you can grab all of the GLXXX, ARXXX, APXXX, etc. data directories out of the MAS_XXX directory as long as you don't move the PRXXX directory. This is what we understand as of today.