Sage 100

 View Only
Expand all | Collapse all

Sage 2013 to 2018 upgrade. One company conversion

  • 1.  Sage 2013 to 2018 upgrade. One company conversion

    Posted 08-13-2018 15:21
      |   view attached
    Sage 2013 to 2018 upgrade. One company conversion fails with the following error: ""The following conversion record failed while converting ACC: 06.00.00.00:DATA:CI_Options:000000:00 - Failed to create table CI_Options: Create Table failed for {lists folder names} PHYSICAL UPDATE ABORT: CI_Options {more folder names} {ends with} CI_Options.M4T is currently open. Cannot update at this time."" All other companies converted fine, including a ""test"" copy of this company. This is the only company with Job Cost. Anyone seen this before?


  • 2.  RE: Sage 2013 to 2018 upgrade. One company conversion

    Posted 08-13-2018 15:47
    Did you reboot server before starting? If the test converted, you could LM copy back to the 'real"" company and see if that clears the issue.


  • 3.  RE: Sage 2013 to 2018 upgrade. One company conversion

    Posted 08-13-2018 15:50
    I got this same error on an upgrade to 2018 this past weekend. There was a DSD enhancement that needed to be registered on the 2018 install and then the data conversion ran without any errors


  • 4.  RE: Sage 2013 to 2018 upgrade. One company conversion

    Posted 08-13-2018 15:54
    I just verified that it was the DSD 6 decimal enhancement. Apparently that not being registered was preventing the conversion from accessing the common information options file.


  • 5.  RE: Sage 2013 to 2018 upgrade. One company conversion

    Posted 08-13-2018 15:57
    @JeffSchwenk yes, rebooted server. Not sure what you mean by ""LM copy back to the real company"" . @BernieLehman 6 Dec Precision IS installed, checking to confirm it is registered...


  • 6.  RE: Sage 2013 to 2018 upgrade. One company conversion

    Posted 08-13-2018 16:12
    @BernieLehman 6 Decimal Precision IS registered. Went back into old version, ran DSD convert data, remigrated and converted - still same error.


  • 7.  RE: Sage 2013 to 2018 upgrade. One company conversion

    Posted 08-13-2018 16:28
    Tried copying CI_Options from the test company and changing the company code field before migration - still same error. I am also getting a message that the target installation is in use, but I am the only user on the server and clicking OK continues. The Integration Engine is stopped, but Advisor Update is still running.


  • 8.  RE: Sage 2013 to 2018 upgrade. One company conversion

    Posted 08-13-2018 18:40
    I recall doing the DSD registration in 2018, re-migrating the company file from the 2017 version, re-booting the server to make sure nothing was locked (even though no files were showing open) and then stopping the integration engine and the advisor when it came back up and finally running the company data conversion.


  • 9.  RE: Sage 2013 to 2018 upgrade. One company conversion

    Posted 08-13-2018 18:59
    Convert the test company, then do a library master copy back to the real company. Or perhaps library master copy the real company to the Test company, then library master copy the test company back to the real company, then migrate and convert.


  • 10.  RE: Sage 2013 to 2018 upgrade. One company conversion

    Posted 08-13-2018 20:18
    @JeffSchwenk if only the test company were current, sigh...


  • 11.  RE: Sage 2013 to 2018 upgrade. One company conversion

    Posted 08-13-2018 20:20
    @BernieLehman what do I have to lose (but more time - sheesh) I can try that.


  • 12.  RE: Sage 2013 to 2018 upgrade. One company conversion

    Posted 08-13-2018 20:53
    @BernieLehman that worked! Thanks so much.