Premium: Data files for XXX have not been converted. You must convert before copying

SOLVED

Upgrade this week to  v2020.2 (PR 2.21), Premium (with DSD Multi-Currency and APS).

When trying to refresh test company codes with fresh data we get the error.  I even tried creating a blank company code ZZY, with just CI and GL, and I get the same thing.

Yes, I ran company conversion.  This is a Live Premium system with no ability to run a parallel system to test things so some of the KB troubleshooting steps are impossible (i.e. KB 35489's playing with folder renaming and Activate...).

SY_Activation's DataLevel values are all clean.

The only thing I can see is that the "EnhancementLevel" in SY_EnhancementModule is set to 6.2 instead of 6.20.  Is that enough to cause the error?  Would it be safe to edit these values to 6.20?  (Again, Premium, with only the Live system so I can't test this safely).

  • FormerMember
    0 FormerMember

    Premium requires more than an advanced skill level.

    Personal Belief: (don't hang me)

    ProvideX started off as a character based top down Business BASIC. NOMADS was added to stear SOTA away from VB Classic. I was impressed at the time MK could get a Windows API message based event paradigm working. OOP emulation was the icing on the cake.

    Thankfully computers have become faster and memory cheap. Running multiple copies ProvideX emulates multi-threading.

    Is adding ODBC emulation of native ProvideX IO to provide a native SQL DB the 'straw'?

  • 0 in reply to FormerMember

    We have dozens of customers running Premium just fine and it is absolutely our first recommendation for many reasons (with data integrity / security and custom reporting performance at the top of the list of reasons why).

    But none of that pertains to the question I am asking here.  Do you have anything helpful to contribute pertaining to the specific question I am asking about?

  • FormerMember
    0 FormerMember in reply to Kevin M

    Just sharing a perspective. You can put away the rope.

  • 0 in reply to FormerMember

    If you want  to start a thread to pontificate about the merits of different aspects of the system architecture, no problem. 

    Here I am asking about a specific real problem on a Live customer system, and off topic posts are unhelpful.

  • FormerMember
    0 FormerMember in reply to Kevin M

    Got it. Sorry for stepping on your emergency need for support thread.

  • 0

    Hey Kevin,

    You're probably way ahead of me here but Jon Reiter of DSD would be the next person I'd contact re the SY_Enhancement file. He will be able to answer your question. 

    I'm curious whether you upgraded them from a Standard or Advanced or if this was a Premium to Premium upgrade. I'm guessing you've already looked for the "usual suspects", like files that don't belong and odd modules in SY0CTL (does a Premium system still have that?).

    I'm not familiar with APS, is that a credit card payment mod?

  • +1
    verified answer

    Kevin,

    When copying data to a new company code, that message is triggered under two conditions.  The first is if the data is newly migrated which wouldn't be the issue for you.  The second condition is if one or more of the Sage Modules or an Enhancement requires conversion.  My guess is that this is what is happening for you.

    Without more information, I can't say for sure if it is a Sage Module or one of the Enhancements that is failing the conversion check.

    It should not be related to the EnhancementLevel being 6.2 instead of 6.20 but there would be no harm in editing those values.

    Take a look at the CI_EnhancementActivation table and make sure all those records appear to have the proper values for data level and sub level.  Do the same for the Sage Module records in SY_Activation.

    You may want to open a case with Customer Support on this and/or reach out to the Development Partners that created the Enhancements.


    Thank you,

    Kent

  • 0 in reply to rclowe

    Premium to Premium.  (I did email DSD support... which I assume will escalate to Jon if necessary.  I have yet to find where the DSD version #'s are stored).

    APS is an alternate to Paya for CC processing, yes.

    I just checked... SY0CTL.SOA is clean.  All "l" records are current. 

  • 0 in reply to Kent Mackall

    Thanks for the feedback Kent. 

    I hadn't noticed CI_EnhancementActivation before.  The APS record seems to be for the  wrong DataLevel and Sublevel, but editing values to match SY_EnhancementModule didn't help.

    The developer code is wrong too (with APS now being developed in house, DeveloperCode 568, instead of by ASI).

    BTW, I can't edit the values in SY_EnhancementModule from 6.2 to 6.20 because it's a numeric field... the extra zero won't save.

    I'd open a Sage case, but with enhancements I know support will need me to look there first.

    I've reached out to DSD, and APS is still troubleshooting something else which is more important than the company copy problem.

  • 0 in reply to Kevin M

    Thanks for the update Kevin. 

    Working with the Development Partners to determine if one of the enhancements has an issue is always a good idea.  However, you should be able to open case with Sage for this, just let them know it is a developer support issue and it should be assigned to the appropriate analyst and if needed escalated to Sage 100 Development.

    Thank you,

    Kent