Sage 100

 View Only
  • 1.  Conversion Failed - Sage 100 Premium

    Posted 02-26-2021 16:19
    Converting Sage 1000 2018 to Sage 100 2020 - Both are Premium.

    When converting Company tables, the following errors pops up.

    The following conversion record failed while converting TST:\06.10.03.00:DATA:SO_SalesOrderDetail:000000:000 - Error #80: Invalid key definition, number or name
    Errors were written to the conversion log while converting TST Company Data to version 06.20.00.01.
    Closed log

    What is this error and how is it resolved?  Third party enhancements are Avatax, DSD SO-1085, and Insych.

    ------------------------------
    Myron Stevenson
    Consultant
    Clearis Consulting, Inc
    Duluth, MN
    218-525-6720
    ------------------------------


  • 2.  RE: Conversion Failed - Sage 100 Premium

    Posted 02-26-2021 16:39

    It looks like you may have a bad or null record in either SO_SalesOrderHeader or SO_SalesOrderDetail.

     

    Try opening the SO_SalesOrderDetail table in the MAS_TST database in SQL Management Studio. Add "ORDER BY SalesOrderNo" to the end of the SELECT query and look for a record that has null or zeroes in the SalesOrderNo. If that doesn't find anything, try "ORDER BY LineKey" and look for any Line Keys with "000000" or "NULL" values. Unlike most sequence fields in Sage, 000000 is not a valid LineKey in this table. NULL values are also prohibited. If you don't see any issues in those two fields, check and see if there are any SalesOrderNo values in SO_SalesOrderDetail that do not exist in SO_SalesOrderHeader. You can use this query to check that:

     

    SELECT        dbo.SO_SalesOrderDetail.SalesOrderNo AS DetailSONumber, dbo.SO_SalesOrderHeader.SalesOrderNo AS HeaderSONumber

    FROM            dbo.SO_SalesOrderDetail LEFT OUTER JOIN

                             dbo.SO_SalesOrderHeader ON dbo.SO_SalesOrderDetail.SalesOrderNo = dbo.SO_SalesOrderHeader.SalesOrderNo

    WHERE        (dbo.SO_SalesOrderHeader.SalesOrderNo IS NULL)

     

    If that doesn't find anything, try calling Sage.

     

    Raymond Westcott

    Business Software Consultant

     

    Millennium black on white background without mbsg copyright logo

     

    ERP Software Specialists

    IT Strategy, MSSP Services

     






  • 3.  RE: Conversion Failed - Sage 100 Premium

    Posted 02-26-2021 16:42
    Whenever I see weird SQL errors, the first thing I check is the Collation method.  If this is wrong, do a complete uninstall of Sage and SQL, then start again.


    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------