Sage 100

 View Only
Expand all | Collapse all

Migrating data from 4.20 to 2014 and at the end of

Ron Peterson

Ron Peterson12-12-2014 07:57

  • 1.  Migrating data from 4.20 to 2014 and at the end of

    Posted 12-12-2014 06:07
    Migrating data from 4.20 to 2014 and at the end of the process it fails with error Finalize Failed with the following error M/R is invalid. They have never owned nor installed M/R. Anyone have any suggestions?


  • 2.  RE: Migrating data from 4.20 to 2014 and at the end of

    Posted 12-12-2014 06:32
    Do they have any old enhancements or modules they aren't using any longer on the old system? I ran into something similiar one time with a client that had old IT (ebm) data.


  • 3.  RE: Migrating data from 4.20 to 2014 and at the end of

    Posted 12-12-2014 06:33
    Just a hunch--Could there be an old MRP folder hanging out there. All you need to do is rename the folder--Sage won't recognize it for converting.


  • 4.  RE: Migrating data from 4.20 to 2014 and at the end of

    Posted 12-12-2014 07:04
    Normally, MAS90 will give you a message if the 2014 install license has different modules than the previous and tell you to install or un-install from the new or the old to continue. Maybe at one time they turn on a module for a trial test? On the older levels you could install and turn on a module for 40 days (or 40 accesses, I can't remember). Look for a MRXXX (company code) in the MAS_XXX folder or you can look at the SY_Module.M4T or the SY_Activation.M4T in the MAS_System folder using DFDM.


  • 5.  RE: Migrating data from 4.20 to 2014 and at the end of

    Posted 12-12-2014 07:11
    Might be off assistance - https://90minds-com.socialcast.com/messages/19932531


  • 6.  RE: Migrating data from 4.20 to 2014 and at the end of

    Posted 12-12-2014 07:13
    We can't find reference to M/R anywhere within their files at all. We have also already looked in the Sy_module and Sy_activation file and can't find any reference.


  • 7.  RE: Migrating data from 4.20 to 2014 and at the end of

    Posted 12-12-2014 07:46
    If you change up the migration, for example, from all company codes to just migrating one company code, do you get the same result? If you end up narrowing it down to one company code, then one of my tricks in my bag of tricks is to do a simple copy company to another company code and then see if the migration will run on the copied company.


  • 8.  RE: Migrating data from 4.20 to 2014 and at the end of

    Posted 12-12-2014 07:57
    Pam, What about the SY0 file?


  • 9.  RE: Migrating data from 4.20 to 2014 and at the end of

    Posted 12-13-2014 08:56
      |   view attached
    I received the same error this morning when migrating a customer from 4.3 to 2014. @PamScott, do you have any third party stuff on your customer's install. We have HT POS and are going to IIG. On 4.3, I copied their active company to a temporary company code, cleaned up inventory there, removed HT POS data for the temporary company, migrated and received the error. I have looked at the Sy_Module, SY_Activation and SY0CTL and they appear clean. Nothing on new KB. Archive KB article 110-511841 addresses the same or similar issue when migrating from 4.0 to 4.3. See Attached. I have looked at the SY1Q0x files in DFDM and there is no reference to MR. One idea is to copy the active 4.3 install to another location, run it, remove POS data for all companies, remove the HT programs and see if migrate to 2014 will work from there. Any ideas?


  • 10.  RE: Migrating data from 4.20 to 2014 and at the end of

    Posted 12-15-2014 04:59
    This client also has HT POS. The PM working on this was trying some suggestions from Sage and I'm not sure if she had success over the weekend or not. Once I talk with her this morning, I'll let you know what we tried and what did or did not work.


  • 11.  RE: Migrating data from 4.20 to 2014 and at the end of

    Posted 12-15-2014 10:14
    @RonPeterson Yes, we've reviewed the SY0 file, also, and find no mention of it there.


  • 12.  RE: Migrating data from 4.20 to 2014 and at the end of

    Posted 12-15-2014 10:19
    @JohnBroadfoot Yes, there are third parties, including HT POS and are going to Fusion. I've restarted with a clean v.2014 install and tried to migrate only the system files and it still errors, though slightly different. We're now looking into the system files (someone much more knowledgeable than me), and Ron at Sage has requested the SY_Migration.pvc file to review. The next steps will be to replace the DDICTS folder and 4 providex files in a copy of the v4.2 install MAS90 folder, then try to migrate from that folder.


  • 13.  RE: Migrating data from 4.20 to 2014 and at the end of

    Posted 12-15-2014 11:14
    Also make sure SY0CTL has no record like ""M/R.."" or ""lM/R.."" or ""lMR"" (lower case L, not a 1 or an I).


  • 14.  RE: Migrating data from 4.20 to 2014 and at the end of

    Posted 10-20-2017 12:19
    How was this resolved? I am getting the same error and this customer has no Mods, they are upgrading from 2013 to 2017