Sage 100

 View Only
Expand all | Collapse all

Error with Payroll conversion 2017 to 2019.2/PR2.19.4

  • 1.  Error with Payroll conversion 2017 to 2019.2/PR2.19.4

    Posted 10-25-2019 13:11
    One of their companies converted fine.  2 other companies are failing with this message:, which occurs early in the PR conversion, just after I see the message that it's starting Department conversion.  One of the companies is a copy of their live data (a Payroll backup).  Anyone encountered this error?


    ------------------------------
    Barbara Goldstein
    Sr. Consultant
    DSD Business Systems
    San Jose CA
    800.627.9032 x221
    ------------------------------


  • 2.  RE: Error with Payroll conversion 2017 to 2019.2/PR2.19.4

    Posted 10-25-2019 14:39
    Does the Activity Log provide any further info/details?  Although your error doesn't reference J/C, I found the following in the Sage KB:

    Error: "The following conversion record failed while converting XXX 02.17.00.00:DATA:PR_ConvertToFramework:000000:000-Error #12: File does not exist (or already exists). File:JC_JobTransactionDetail"

    Products
    Sage 100

    Country
    North America

    Description
    <content>

    Error: "The following conversion record failed while converting XXX 02.17.00.00:DATA:PR_ConvertToFramework:000000:000-Error #12: File does not exist (or already exists). File:JC_JobTransactionDetail" where "XXX" is the company code in Sage 100

    </content>

    Cause
    <content>

    The JC_JobTransactionDetail file cannot be found to convert. Either the file is missing, or the Job Cost module is not used but there are Job Cost data files.

    </content>

    Resolution
    <content>

    Restore the missing JC_JobTransactionDetail from backup.

    OR

    If the Job Cost application module is not installed AND not in use AND is not integrated, then rename the "JCXXX" data folder, where "XXX" is the company code being converted.

    </content>

    Additional information
    <content>

    In one case, there was an unused "JCXXX" Job Cost company data folder from over 15 years ago that had been copied into the new installation during the migration process. That folder was not in use, but was causing the error. Renaming that folder (to "badJCXXX") allowed conversion to proceed.

    </content>

    Category
    Conversion
    From Sage products


    ------------------------------
    - Brett
    ------------------------------



  • 3.  RE: Error with Payroll conversion 2017 to 2019.2/PR2.19.4

    Posted 10-25-2019 14:45
    I also noticed in your screen-shot that some of the modules for 19P are at 4.5 and P/R shows as 5.30 (v2016), but you said you were upgrading from v2017 - so I'm thinking that might have something to do with it.

    ------------------------------
    - Brett
    ------------------------------



  • 4.  RE: Error with Payroll conversion 2017 to 2019.2/PR2.19.4

    Posted 10-25-2019 15:13
    One of these days, if I live long enough, I'll master the art of searching for KB articles.
    They do not have Job Cost and there is no JCXXX folder in either company.  And I misspoke, I'm upgrading from 2016.  As I look at that company in Company Maintenance, it now looks like this:
    I've tried re-converting, but still fails with the same error.

    ------------------------------
    Barbara Goldstein
    Sr. Consultant
    DSD Business Systems
    San Jose CA
    800.627.9032 x221
    ------------------------------



  • 5.  RE: Error with Payroll conversion 2017 to 2019.2/PR2.19.4

    Posted 10-25-2019 15:26
    If all modules for 19P aren't at 5.30 in your source system, you may want to try getting them to that and re-migrate.

    ------------------------------
    - Brett
    ------------------------------



  • 6.  RE: Error with Payroll conversion 2017 to 2019.2/PR2.19.4

    Posted 10-25-2019 15:31
    All modules at 5.3 in source system.

    ------------------------------
    Barbara Goldstein
    Sr. Consultant
    DSD Business Systems
    San Jose CA
    800.627.9032 x221
    ------------------------------



  • 7.  RE: Error with Payroll conversion 2017 to 2019.2/PR2.19.4

    Posted 10-25-2019 15:43
    Oh.  So where'd 4.5 come from that was in your original screen-shot?

    ------------------------------
    - Brett
    ------------------------------



  • 8.  RE: Error with Payroll conversion 2017 to 2019.2/PR2.19.4

    Posted 10-25-2019 16:50
    No idea where that 4.5 came from.  Weird and weirder.  Here's screenshot of the company in 2016.



    ------------------------------
    Barbara Goldstein
    Sr. Consultant
    DSD Business Systems
    San Jose CA
    800.627.9032 x221
    ------------------------------



  • 9.  RE: Error with Payroll conversion 2017 to 2019.2/PR2.19.4

    Posted 10-25-2019 17:55
    I just remigrated that company.  All modules showed at 5.30.  Started conversion.  Conversion failed.  Same message.  Here's what shows in company maintenance.  How strange.


    ------------------------------
    Barbara Goldstein
    Sr. Consultant
    DSD Business Systems
    San Jose CA
    800.627.9032 x221
    ------------------------------



  • 10.  RE: Error with Payroll conversion 2017 to 2019.2/PR2.19.4

    Posted 10-25-2019 18:05
    Silly question (I had a customer connecting to the wrong server a couple days ago):
    Are you sure you're migrating from the correct server / path for the Live data (and not an old copy)?


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



  • 11.  RE: Error with Payroll conversion 2017 to 2019.2/PR2.19.4

    Posted 10-25-2019 18:09
    Yes, pinky swear.

    ------------------------------
    Barbara Goldstein
    Sr. Consultant
    DSD Business Systems
    San Jose CA
    800.627.9032 x221
    ------------------------------



  • 12.  RE: Error with Payroll conversion 2017 to 2019.2/PR2.19.4

    Posted 10-25-2019 19:29
    I generally will open another Company Maintenance and watch (back in the day when you could do all companies) and I think I've seen where it does look like it goes backwards and ​if the error popped up during that time it would say 4.5.  I think you happen to just catch the screenshot at the 'wrong' time.  I wouldn't worry about it.

    ------------------------------
    Nancy Hanson
    Blytheco LLC
    Eagan MN
    ------------------------------



  • 13.  RE: Error with Payroll conversion 2017 to 2019.2/PR2.19.4

    Posted 10-27-2019 14:15
    I am sure you done this, but just tossing it out there.

    I ran into a similar error early on in my upgrades.  Not knowing what else to do, I ran the rebuild utilities for PR key and line files.  This found a lot of garbage records.  Reran the migration from the start and everything proceeded according to plan.  Been doing it ever since.

    ------------------------------
    Jeff Schwenk
    FORMER 90M Board Member
    Bottomline Software, Inc.
    Waynesboro VA
    540-221-4444
    ------------------------------



  • 14.  RE: Error with Payroll conversion 2017 to 2019.2/PR2.19.4

    Posted 10-30-2019 17:54
    Edited by Thomas Rogers 10-30-2019 17:55
    I've seen this one.   If I recall correctly there is a missing file in the PR folder.  PRU.SOA I believe.  Copy it from the old version into the new version.

    Usually happens during final migration/conversion after you have done a test run initially.

    ------------------------------
    Thomas Rogers (TomTarget)
    Target System Technology, Inc.
    Spokane Valley WA
    ------------------------------



  • 15.  RE: Error with Payroll conversion 2017 to 2019.2/PR2.19.4

    Posted 10-30-2019 20:04
    Thanks Tom.  I checked and found all the legacy files were also present in the 2019 folder.  Rebuilding keys didn't help, either.

    One of the companies is a payroll backup company, so we won't bother trying to convert it.  The other company hasn't had Payroll active since 2017, so I removed the module in the migrated data and it converted.  I'll set the user up to access the old version after Go Live so she can view data if necessary.

    By the way, I opened a case with Sage on this, and I re-migrated, including system files.  Still no success.  Their recommended next step was to uninstall v2019 and start over, which I'm not going to do. The client is fine with "Plan B".

    ------------------------------
    Barbara Goldstein
    Sr. Consultant
    DSD Business Systems
    San Jose CA
    800.627.9032 x221
    ------------------------------