Sage 100

 View Only
Expand all | Collapse all

We have at least 5 test upgrades with Sage 100 Pay

  • 1.  We have at least 5 test upgrades with Sage 100 Pay

    Posted 07-12-2018 08:00
    We have at least 5 test upgrades with Sage 100 Payroll included in them. While we can convert the data for the test upgrade, we can't seem to convert the data again for the ""live"" upgrade. The error refers to an Error 13, referencing ""PR_ ConverttoFramework"". We have two Sage cases logged, but with no result. I do have a meeting with someone this morning that I hope to get some movement on, but I'm just wondering if anyone else has experienced this problem in doing a second conversion after a test upgrade.


  • 2.  RE: We have at least 5 test upgrades with Sage 100 Pay

    Posted 07-12-2018 08:02
    Are you doing a full migration (system files and all) on the live or just company data?


  • 3.  RE: We have at least 5 test upgrades with Sage 100 Pay

    Posted 07-12-2018 08:05
    We were told by Sage that we could copy the MAS_### folder from old to 2018 and re-run the conversion... but have not tested this yet. (Customer is still sourcing a new server for the upgrade). I'm very interested in the answer to this thread!


  • 4.  RE: We have at least 5 test upgrades with Sage 100 Pay

    Posted 07-12-2018 08:35
    @Nancy.Hanson - we were just doing the company data, but I think we'll try @Kevin.Moyes suggestion to copy the MAS_### folder over. I'll let you know what happens with that - both of these suggestions make sense because it goes through the first conversion with no issues/problems whatsoever. It's only the 2nd conversion it can't do. (Now the question is - why have we had this issue, with 2 Sage cases, and no one at Sage could tell us this? Thank goodness for this group!)


  • 5.  RE: We have at least 5 test upgrades with Sage 100 Pay

    Posted 07-12-2018 08:41
    Unless there's a reason not to my standard upgrade practice has been (a) Migrate everything for the test, then (2) for additional testing or final upgrade copy just the MAS_XXX. When paperless is in play I use the utility to either search/replace paths or the merge utility.


  • 6.  RE: We have at least 5 test upgrades with Sage 100 Pay

    Posted 07-12-2018 08:51
    Oh - and I will indeed let you know what happens once we try the second conversion with the entire MAS_### folder. Just makes sense to me that would work - I didn't know we were only converting the data and nothing else...


  • 7.  RE: We have at least 5 test upgrades with Sage 100 Pay

    Posted 07-12-2018 09:52
    I'm also interested to hear if the method of copying the MAS_### folder only for final migrations works. I can't find it in any notes I've taken, but I could swear Sage told us you couldn't use that method with 2018 + Payroll.


  • 8.  RE: We have at least 5 test upgrades with Sage 100 Pay

    Posted 07-12-2018 10:00
    I'm interested in the answer also. I'm with @BarbaraGoldstein, I also seem to remember something with Payroll and the encryption of the PII data.


  • 9.  RE: We have at least 5 test upgrades with Sage 100 Pay

    Posted 07-12-2018 10:08
    @Barbara.Goldstein - I fear you are correct. Copying over just the MAS_### folder does NOT relieve us of the error. We get the same error. Which is going to be a MAJOR problem if we do have to redo the entire conversion (system files and all) as we do a lot of work in the test system, doing a lot of tweaking in Payroll to come up with the right configuration for each individual payroll client. Incidentally, I'm sure everyone has already discovered that the only way to have an ""Exempt"" employee in Payroll 2018 is to set the Employee Dependents as high as they'll go. We no longer have the ability to override the tax tables through Employee Maintenance with an adjustment by using a zero dollar amount, or even to ""adjust"" the tax tables to add an additional amount. The ""Exempt"" flags in the Employee Masterfile mean that Withholding Wages will be zero...so we can't use that. (ie Withholding wages should show with a dollar amount on the W-2, but we don't want taxes taken out on employees claiming a filing status of ""exempt"". High Dependent Number is the only way to do that now.)


  • 10.  RE: We have at least 5 test upgrades with Sage 100 Pay

    Posted 07-12-2018 10:11
    @SueBennett Remigrating the system files did the trick for us. Sage was totally clueless...blamed it on lack of hard drive space even though the data drive had over 50GB of free space.


  • 11.  RE: We have at least 5 test upgrades with Sage 100 Pay

    Posted 07-12-2018 10:32
    @John.Shaver - Hahahaha! (At least they didn't ask you if the printer was plugged in and working.) Okay, so Nancy Hanson alluded to the System Files - it's just resetting up the Roles, Paperless Office, etc. stuff will be more expensive for the clients, but it sounds like it is what it is. We'll try that this afternoon and let everyone know if that works...


  • 12.  RE: We have at least 5 test upgrades with Sage 100 Pay

    Posted 07-12-2018 10:34
    And not obviously as ""major"" as I made it sound...


  • 13.  RE: We have at least 5 test upgrades with Sage 100 Pay

    Posted 07-12-2018 10:37
    Elliott told me to use the folder copy method for an especially complex upgrade we're planning. I know you can't do this from 2018 to 2018 (because of the encryption key) but our PR source data will be in v2017 to start with. I'm curious if he is aware of your cases...? Pritchard, Elliott <Elliott.Pritchard@sage.com>


  • 14.  RE: We have at least 5 test upgrades with Sage 100 Pay

    Posted 07-12-2018 10:38
    We just did a final conversion today. The test conversion was done before update3/PR 2018.2. We installed the updates before remigrating the company data (not system data) and got error 13 like message above. We went back to update2/2018.1 and then migrated only company data. Conversion had no issues. Applied update3/2018.2 after converting.


  • 15.  RE: We have at least 5 test upgrades with Sage 100 Pay

    Posted 07-12-2018 10:40
    @Alan.Neirgarth - that makes perfect sense. We've only had one conversion that went through a final upgrade, and that was prior to PU3. I have an appointment today with a Sage Engineer - I'll bring that up with him...maybe we can get a hot fix for PU3...


  • 16.  RE: We have at least 5 test upgrades with Sage 100 Pay

    Posted 07-12-2018 10:41
    @Kevin.Moyes - like Alan said, I think you'll be able to do it if you're not using PU3 ... I believe PU3 is where the problem is...


  • 17.  RE: We have at least 5 test upgrades with Sage 100 Pay

    Posted 07-12-2018 16:35
    No news yet - but we'll be working on this with a Sage Engineer tomorrow morning...live and online. I'll let you know what happens...


  • 18.  RE: We have at least 5 test upgrades with Sage 100 Pay

    Posted 07-12-2018 18:01
    This was provided to use by Sage after a roundtable on PR: It may help http://www.evernote.com/l/AQ6rwolxcORLsqSFC4dMbr7rKKeSWIaDs3Y/


  • 19.  RE: We have at least 5 test upgrades with Sage 100 Pay

    Posted 07-13-2018 08:01
    We've confirmed Alan's positive experience with re-converting Payroll data from PU2 and NOT PU3. We still consistently get the error trying to do Payroll re-conversions using PU3 (after initially converting data for a test upgrade with no problem but then trying to re-convert the data again for the Go Live.) Our meeting with the Sage Engineers got postponed yesterday, but two of them will be streaming into one of our client sites this morning to drill around the error to see if they can find out why we cannot convert data a second time.


  • 20.  RE: We have at least 5 test upgrades with Sage 100 Pay

    Posted 07-13-2018 08:05
    I wonder if renaming the text files mentioned in Moira's notes would fix the problem.


  • 21.  RE: We have at least 5 test upgrades with Sage 100 Pay

    Posted 07-13-2018 08:07
      |   view attached
    @Moira.Goggin - thank you! Sage also sent the attached notes to me, which I thought other folks could use as well. Attached!


  • 22.  RE: We have at least 5 test upgrades with Sage 100 Pay

    Posted 07-13-2018 08:23
    @Kevin.Moyes - Pretty sure that has nothing to do with it. I would think if that was true, we would have the same issue using PU2. But PU2 works.


  • 23.  RE: We have at least 5 test upgrades with Sage 100 Pay

    Posted 07-13-2018 08:37
    The more I read the more confused I get. **4)Licensing for employees when doing a parallel migration is it impacted?** Yes somewhat. When you migrate your data over and start to do test runs, these tests will utilize your payroll tier license and still enforce that you do not exceed your tier. Sage 100 would still consider the new system a live system and will enforce the tier rules. However, when you re-migrate the same data it will essentially start the counter anew on those employees that were tested previously. For example: 1) ABC Company is migrated and converted. Employee 01-0000001 is now assigned EmployeeKey of 1a (this is a 32 character randomly generated key, but using 1a as a short example) This company is setup to do some sample test pay calcs, which would record employee 1a as an employee that had been paid this month, so our employee count = 1 2) Next Everything went well but we want to re-migrate ABC to the latest data Employee 01-0000001 is now assigned EmployeeKey of a9, since this is a random assignment it is almost assured that this key will be different. This company runs a payroll for the same month, this employee would increment the employee counter because the key is different.


  • 24.  RE: We have at least 5 test upgrades with Sage 100 Pay

    Posted 07-13-2018 08:44
    yes somewhat"". Under the example given , I think the answer is yes unless my reading comprehension is fading.


  • 25.  RE: We have at least 5 test upgrades with Sage 100 Pay

    Posted 07-13-2018 09:56
    PROBLEM SOLVED! So - it really has nothing to do with PU2. PU2 worked only because we had to do a total re-installation of the program files to install PU2 where we previously had used PU3. So - that's not it. What is it: Sage was trying to ""clean up"" some of the old program files, which are automatically deleted in the first migration/conversion and one of those files is the old tax table file: PRX.SOA. So - the first data conversion deletes it, but it still is necessary for the second data conversion - hence the Error 13. So - you can still use PU3, but if you do a test install and then a ""final"" conversion, you have to manually copy the PRX.SOA file from the previous Sage 100 version (in the PR subdirectory) into the 2018 Payroll PR subdirectory. And that works! Hurray! (Obviously it is a mistake that Sage automatically deletes that PRX file when it is required for the second conversion. But - it's a simple fix!)


  • 26.  RE: We have at least 5 test upgrades with Sage 100 Pay

    Posted 07-13-2018 10:29
    Since it is a simple fix, what does Sage plan to do about it? This is a common way of converting unless you are a member of 90M and read this thread, you will get stumped by this.


  • 27.  RE: We have at least 5 test upgrades with Sage 100 Pay

    Posted 07-13-2018 10:37
    ^^ @WayneSchulz on the licensing, Sage sent this after the roundtable: http://www.evernote.com/l/AQ4hkO0aBkxCoI_vEPu8hwcCVJF69s3ekbw/


  • 28.  RE: We have at least 5 test upgrades with Sage 100 Pay

    Posted 07-13-2018 10:42
    Appears to be largely the same vague document that @SueBennett posted


  • 29.  RE: We have at least 5 test upgrades with Sage 100 Pay

    Posted 07-13-2018 10:45
    ELI 5: So, can a user still copy/paste MAS_XXX from a pre-2018 version into a 2018 release and then use company maintenance - convert data if they do the PRX copy or is it now mandatory to do a proper re-migration and then conversion through the Sage menu?


  • 30.  RE: We have at least 5 test upgrades with Sage 100 Pay

    Posted 07-13-2018 11:08
    @Jeff.Schwenk: Obviously the Sage Help Desk doesn't know anything about the PRX file, as we have multiple cases into Sage about the issues with no resolution there. The Engineers did say they would put the fix in the September release - Payroll Version 2019 - but I'm guessing they'll just do a KB Article about copying the PRX from the old installation into the 2018 PR folder before re-converting the data. I don't know for a fact that they won't come out with an actual ""fix"" before that release - it's just total conjecture on my part.


  • 31.  RE: We have at least 5 test upgrades with Sage 100 Pay

    Posted 07-13-2018 11:10
    @Wayne.Schultz: I don't the answer to the copy/paste MAS_XXX question. We are choosing to do the proper re-migration and conversion to be safe!