Sage 100

 View Only
Back to discussions
Expand all | Collapse all

Error 80 Invalid key definition, number or name (company data conversion)

  • 1.  Error 80 Invalid key definition, number or name (company data conversion)

    Posted 11-18-2022 14:06
    Upgrade from v2018 Standard to v2022 Standard
    System migration goes fine, but during company conversion I get this error (where the M4T is deleted).
    The file was empty to begin with, and v2018 rebuild key files was done prior to the migration.

    Sage case opened... we confirmed an enhancement is not to blame (DSD ARDR, which does not appear to affect this file) by escape trapping and renaming the Links folder contents.  No answers so far.

    I tried manually creating the file, with the same error.

    ABC demo data converts fine, but copying that M4T to the customer data folder does not help (same error, M4T deleted).

    DFDM of the source v2018 file shows a different order to the field list, including a few extra fields (that should not be in a v2018 file), which is odd, but I have no idea if that is related to the problem.

    Any ideas?

    (Error text to help with searches later):
    The following conversion record failed while converting TST:\06.20.00.00:DATA:AR_CashReceiptsHeader:000000:000 - Failed to create table AR_CashReceiptsHeader: Create Table failed for E:\Sage\Sage2022\MAS90\MAS_TST\ARTST\AR_CashReceiptsHeader\PHYSICAL UPDATE ABORT: AR_CashReceiptsHeader - Unable to create file <E:\Sage\Sage2022\MAS90\MAS_TST\ARTST\AR_CashReceiptsHeader.M4T>

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


  • 2.  RE: Error 80 Invalid key definition, number or name (company data conversion)

    Posted 11-18-2022 14:36
    it could be a data dictionary issue.  Try creating / adding a UDF to 2018 AR_CashReceiptsgeader before migrating.

    ------------------------------
    Doug Higgs
    Midwest Commerce Solutions, Inc
    (312) 315-0960
    Chauffeur, Chef, and Personal Assistant to Sprinkles
    ------------------------------



  • 3.  RE: Error 80 Invalid key definition, number or name (company data conversion)

    Posted 11-18-2022 15:48
    Thanks for the suggestion Doug.  Worth a try. 
    I did that after migration (using ABC to open UDF maintenance) with no change, but I've restart the migration (including system) after adding a UDF in the source system.
    *fingers crossed*

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

    Original Message


  • 4.  RE: Error 80 Invalid key definition, number or name (company data conversion)

    Posted 11-18-2022 16:50
    No luck.  Same error.

    Sage suggestion: disable Anti-Virus (Webroot Endpoint Protection)... no change.

    Testing a few suggestions from Alnoor from this post (link): no change.



    Fun.

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

    Original Message


  • 5.  RE: Error 80 Invalid key definition, number or name (company data conversion)

    Posted 11-18-2022 17:01
    Edited by David Speck II 11-18-2022 17:59
    Couple things.
    1. In your attempt to use SY_Activate_Bus, you didn't output the returned value of the Activate method or its LastErrorNum$ and LastErrorMsg$ properties.  
    2. Have you tried launching SYZCON then typing dd and pressing ENTER on your keyboard to launch the Data Dictionary Maintenance task and then pull up the table in question and review its indexes and compare them between the source, the destination, and another known good source for the versions?


    ------------------------------
    David Speck II
    Tennessee Software Solutions
    ------------------------------

    Original Message


  • 6.  RE: Error 80 Invalid key definition, number or name (company data conversion)

    Posted 11-18-2022 17:35
    How do I remove an index?  KUNENCRYPTED seems to be extra...

    ...and it references a field in this DD, but not in Sage FLOR.


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

    Original Message


  • 7.  RE: Error 80 Invalid key definition, number or name (company data conversion)

    Posted 11-18-2022 17:55
    Edited by David Speck II 11-18-2022 17:57
    Which version is that data dictionary screenshot from because I don't believe the kEINVOICE index should exist on 2018.  As for the kUNENCRYPTED one, sounds like a third-party is responsible.

    To delete the index, remove all fields in the key segments box and when you click OK, it should prompt if you are sure you want to delete the key.

    EDIT:

    Here is what my 2018.10 system looks like.

    Here is what my 2022.1 system looks like.

    ------------------------------
    David Speck II
    Blytheco LLC
    ------------------------------

    Original Message


  • 8.  RE: Error 80 Invalid key definition, number or name (company data conversion)

    Posted 11-18-2022 18:06
    Thanks again David.  That is what I did... (the pic was the v2022 data dictionary).

    Alnoor recommended I do the Activate afterwards, which I'm going to do next.

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

    Original Message


  • 9.  RE: Error 80 Invalid key definition, number or name (company data conversion)

    Posted 11-18-2022 18:04
    I think that did it!  I removed the elements of the extra index and that removed it.  Company conversion now runs to completion without error.

    The field EncryptedCreditCardNo was from the v4.x days.  I have no idea how it is still in this file, or where that index came from, but this customer doesn't even use Sage credit cards (and never has).

    I think this can be moved out of Urgent now.  Thanks a ton to all who made suggestions!  :-)

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

    Original Message


  • 10.  RE: Error 80 Invalid key definition, number or name (company data conversion)

    Posted 11-18-2022 17:01
    This is all about a missing key definition in AR_cashteceiptsheader table.  If you have any mods, they could have created a new one.   I would open the table in DFDM  for the problem child and check what keys there are.  Do the same for another company and compare.  




    Original Message


  • 11.  RE: Error 80 Invalid key definition, number or name (company data conversion)

    Posted 11-18-2022 17:02
    Maybe try an intermediate step to 2020.  Put the keys on your office computer version of 2020 and see if it converts without the enhancements.  If so then try and convert from 2020 to 2022.

    ------------------------------
    Doug Higgs
    Midwest Commerce Solutions, Inc
    (312) 315-0960
    Chauffeur, Chef, and Personal Assistant to Sprinkles
    ------------------------------

    Original Message


  • 12.  RE: Error 80 Invalid key definition, number or name (company data conversion)

    Posted 11-19-2022 20:21
    Does Reinitialize Data Files work for any company codes?
    If you brought in the clients dataset to a vanilla install of Sage that you may have personally will it let you drop that file then?
    Will it let you convert the data on that vanilla system?
    Does it work correct in Sage 100 2018 for Reinitialize Data Files?
    Did you try, just for testing, rename the header and detail file and bring in brand new files from like the ABC company just to see if it would convert then?

    ------------------------------
    Carmen Cruz
    Sage Consultant
    CompuData
    ------------------------------



  • 13.  RE: Error 80 Invalid key definition, number or name (company data conversion)

    Posted 11-21-2022 10:10
    Carmen,
    Thanks for the reply... there was an extra index in the data dictionary for that file.

    Robert / Anne...,
    This can be moved out of Urgent.

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

    Original Message


Related Content