Sage 100

 View Only
  • 1.  Upgrade from MAS 200 4.40 to Sage 100 2014 SU4 wit

    Posted 04-29-2015 12:53
    Upgrade from MAS 200 4.40 to Sage 100 2014 SU4 with enhancements. While converting data error 36, Line 273, program SY_CompanyConversion_Ui.pvc. Last file is SY_ActivityLog. My suspicion is a record(s) in some table from some old enhancement that is casing a problem writing to the activity log but this is just a guess at this point and looking for ideas of what to do to troubleshoot.


  • 2.  RE: Upgrade from MAS 200 4.40 to Sage 100 2014 SU4 wit

    Posted 04-29-2015 12:59
    Which enhancements? Have you tried applying product update 5 for v 2014 or are the enhancements not up to that patch yet?


  • 3.  RE: Upgrade from MAS 200 4.40 to Sage 100 2014 SU4 wit

    Posted 04-29-2015 12:59
    If you have any old enhancements that are no longer in use, have you tried removing any reference to them in the SY0CTL.soa file? I believe those records normally begin with a lower case l as in larry.


  • 4.  RE: Upgrade from MAS 200 4.40 to Sage 100 2014 SU4 wit

    Posted 04-29-2015 13:03
    They have DSD IMXL + DSD Custom Programming, Avalara Avatax Connector, B to B Ship Link + EDI and some are SU4 specific. I have removed a couple records from sy0ctl.soa that was keeping the IMXL from being unlocked but sounds like I may need to look at more records....


  • 5.  RE: Upgrade from MAS 200 4.40 to Sage 100 2014 SU4 wit

    Posted 04-29-2015 13:09
    Those l records should show you the version level recorded. If they're older than the version you're upgrading from then I would delete them. Here's an example of a record: lSYS_MUMDSD LMUM DSD Custom Programming 4.40 ?:1111 - Just backup the SY0CTL before changing, although I'm sure you've already done that.


  • 6.  RE: Upgrade from MAS 200 4.40 to Sage 100 2014 SU4 wit

    Posted 04-29-2015 13:11
    In process now, thanks for your input!


  • 7.  RE: Upgrade from MAS 200 4.40 to Sage 100 2014 SU4 wit

    Posted 04-29-2015 13:20
    Let's hope that takes care of it, if not, call Sage and ask them what that Line 273 is calling in the source code.


  • 8.  RE: Upgrade from MAS 200 4.40 to Sage 100 2014 SU4 wit

    Posted 04-29-2015 14:23
    That did fix it, conversion is running. Thanks again.