Sage 100

 View Only

  • 1.  V2017 Migration to V2020

    Posted 02-17-2021 21:37
    Edited by Jeff Schwenk 02-17-2021 21:44
    Migrating from v2017 to v2020.  For the most part, going smoothly.  However in every company, neither AR nor BM is being recognized as existing during the conversion phase.  Sage sets up a new AR/BM folder every time I convert.  Have tried several times to convert the existing data but neither are recognized.  I do have APS CC installed.

    Not seeing anything in the KB.

    Thoughts?

    TIA

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


  • 2.  RE: V2017 Migration to V2020

    Posted 02-18-2021 12:51
    Can you let it setup AR and BM as blank then pull in the 2017 data folders for AR and BM.
    I don't know the root cause but wonder if  Sage would carry on with converting once you get the blank folders setup?

    ------------------------------
    Wayne Schulz - Schulz Consulting - 860-516-8990
    ------------------------------



  • 3.  RE: V2017 Migration to V2020

    Posted 02-18-2021 12:53
    Does this happen in just 1 company?  Any chance there is a folder within a folder in AR & BM.  or some type of security on those folders?

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

    Original Message


  • 4.  RE: V2017 Migration to V2020

    Posted 02-18-2021 16:53
    Edited by Jeff Schwenk 02-18-2021 18:50
    When I convert those folders, Sage's routine is to rename the existing folders (XXXAR - not set up) and then recreates the blank tables.  Appears to be looking for a table and can't find it.  It did it in every company that had AR.  Will test some of the other thoughts tonight.  I also saved the vanilla Sage set up before I installed the APS enhancement.  Maybe there is something APS is impacting.

    Migrated data using my backup vanilla v2020 install.  It too created new AR/BM folders.  Sounds like I will be on the phone with Sage tomorrow.

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

    Original Message


  • 5.  RE: V2017 Migration to V2020

    Posted 02-18-2021 19:12
    Also check the read only flag (in addition to permissions) for the migrated folders.

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

    Original Message


  • 6.  RE: V2017 Migration to V2020

    Posted 02-18-2021 19:23
    Edited by Jeff Schwenk 02-18-2021 21:16
    Apparently the conversion does not like old .SOA files from prior migrations.  I neglected to clean up all the folders when I migrated from v3.71 to v2017.  Once I deleted them, life continued merrily down the road.

    Thanks @Nancy Hanson and @Wayne Schulz and @Kevin Moyes for getting me thinking.....
    ​​

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

    Original Message


Related Content