Sage 100

 View Only
  • 1.  Working on a upgrade SAGE 100 STD v4.40 to v2014.

    Posted 12-15-2014 05:51
      |   view attached
    Working on a upgrade SAGE 100 STD v4.40 to v2014. Received this error and could not find a resolution in KB or Sage City. Any ideas what I should try next?


  • 2.  RE: Working on a upgrade SAGE 100 STD v4.40 to v2014.

    Posted 12-15-2014 05:56
    Did you try rebuilding that file in the old version? I would do that, rename the IM folder in the 2014 install, copy in the one from 4.4 and start the conversion again.


  • 3.  RE: Working on a upgrade SAGE 100 STD v4.40 to v2014.

    Posted 12-15-2014 06:16
    My memory is same - some type of data issue. I've seen it before.


  • 4.  RE: Working on a upgrade SAGE 100 STD v4.40 to v2014.

    Posted 12-15-2014 06:19
    I'd run the rebuild key files utility and then the rebuilt sort files utility in the old version anytime I'd get a physical update abort (as per Sage's suggestion). Move it like Mary Jo suggested. Sage used to have this in their KB.


  • 5.  RE: Working on a upgrade SAGE 100 STD v4.40 to v2014.

    Posted 12-15-2014 08:08
    I agree with the rebuilding of Keys and Sort files, you may even want to run the Inventory recalc which will recalc this file.


  • 6.  RE: Working on a upgrade SAGE 100 STD v4.40 to v2014.

    Posted 12-15-2014 08:50
    Thanks everyone. Just to be safe I went back into v4.40 and rebuilt all Key, Indexed and Sort files for ALL modules for this one company code. I then re-migrated the data files for this company into v2014. The conversion went thru with no errors this time. Soapbox click on<> Why did SAGE remove this important information from the KB? What other information are they ""holding back"" that we used to have access to? <> click off.