Sage 100

 View Only
  • 1.  Providex to SQL migration issue - ""the source data

    Posted 12-01-2014 14:21
      |   view attached
    Providex to SQL migration issue - ""the source data version 4.40.0.6 is higher than the target data version 0.0.0.0. the migration will now exit."" SQL version is 5.10 and verified that version in the SY_Company SQL table. Any ideas?


  • 2.  RE: Providex to SQL migration issue - ""the source data

    Posted 12-01-2014 14:33
    Eric, you will need to step up, by doing the upgrade from 4.4 to 2014, and then another upgrade to SQL. It will not allow migrations straight to SQL


  • 3.  RE: Providex to SQL migration issue - ""the source data

    Posted 12-01-2014 14:39
    I have seen this error when there is an extended solution. I got around it by temporarily renaming the LINKS folder and then restoring once the upgrade is complete.


  • 4.  RE: Providex to SQL migration issue - ""the source data

    Posted 12-01-2014 14:41
    Thanks Erin - is that a new 2014 SQL constraint? The last one of these I performed was from mas 90 4.3 to 2013 SQL and I didn't take it in 2 steps. Kate, I'll give that a shot. I already migrated once though (forgot to mention that) and didn't get the message.


  • 5.  RE: Providex to SQL migration issue - ""the source data

    Posted 12-01-2014 14:51
    I had the same thing with my 4.5 Advanced to 2013 SQL a year ago. One time it would migrate fine and the next I would see the error. The extended solutions were Multi-Company and Multi-Currency in case they are the same ones.


  • 6.  RE: Providex to SQL migration issue - ""the source data

    Posted 12-01-2014 14:59
    https://www.evernote.com/l/AQ56XO9qWtFCLLebmTENKkfsDXhEsZvRhss


  • 7.  RE: Providex to SQL migration issue - ""the source data

    Posted 12-01-2014 15:36
    thanks everyone, I'll test the solution in Wayne's evernote file tomorrow


  • 8.  RE: Providex to SQL migration issue - ""the source data

    Posted 12-02-2014 10:47
    no customizations on either version, nothing in SY_enhancement or SY_EnhancementModule on either version, renamed Links folder and version error message still pops up. But reinstalling modules (and PU) on the new 2014 SQL version took care of the migration problem. Went back in a tried to migrate another company code and error is not there, so that's good. I think something got messed up in the MAS_System SQL database - even though the version and everything looked ok in the SY_system table.