Sage 100

 View Only
  • 1.  Has anyone run across this before..... we have a c

    Posted 02-10-2014 18:22
    Has anyone run across this before..... we have a client finally upgrading from MAS 4.05 to 4.5. they own DSD's Multi-currency packages. The migration stops because it thinks the CU module in 4.05 is CRM program files when it is DSD's MC module. @Sage100Routine


  • 2.  RE: Has anyone run across this before..... we have a c

    Posted 02-10-2014 19:01
    What happens when it stops? Any message/error?


  • 3.  RE: Has anyone run across this before..... we have a c

    Posted 02-11-2014 07:39
    Dealing with this presently on a 410 to 450 upgrade with Ext Sol Mod. I did get the conversion to run finally. However I did have to generate new 450 files for the couple modules affected. Now for some reason I can't find the article reference. But basically I had to take fresh inventory files (new activation on dumby company) and replace the ones that were present. I determined which module to do by running the embedded io script in the 450 release and those that weren't successful I replaced the BF files with new ones. Zero returned on SO and IM but only had to replace BF files in IM.


  • 4.  RE: Has anyone run across this before..... we have a c

    Posted 02-11-2014 08:03
    Ah found the article I used in reference for the failing conversion. KB # 1004804 ( ""Data needs to be converted"" message occurs.....)


  • 5.  RE: Has anyone run across this before..... we have a c

    Posted 02-11-2014 08:42
    . You have to convert to 4.30 first, to get the M/C to convert to C/X, then go to 5.00


  • 6.  RE: Has anyone run across this before..... we have a c

    Posted 02-11-2014 08:52
    thanks @KennethPhillips


  • 7.  RE: Has anyone run across this before..... we have a c

    Posted 02-11-2014 10:00
    you can also resolve by just removing the sy_module record for CU using Data File Display & Maintenance, and then converting.


  • 8.  RE: Has anyone run across this before..... we have a c

    Posted 02-11-2014 10:05
    If @KennethPhillips fix doesn't work you may also have to edit SY0CTL to remove the l record (that's a lower case ""L"") corresponding to that module.