XLT config file unloadable

Clovertech Forums Read Only Archives Cloverleaf Cloverleaf XLT config file unloadable

  • Creator
    Topic
  • #50288
    Gena Gill
    Participant

      I get this message when I check the error database to see why some ADT messages have failed.  It’s not isolated to any particular message type, but runs the spectrum of all ADT types that I send.

      I have one thread where it’s happened on every message for the last 10 minutes, then I have other times when it’s intermittent on other threads.

      Here’s an excerpt of the message that I get.  Any ideas?  My first thought was that I had built the XLT on another site, but the XLT was built on our master site and the thread in question is also on the master site.

      msgType           : DATA

         msgClass          : ENGINE

         msgState          : XLT config file unloadable (300)

         msgPriority       : 5120

         msgRecoveryDbState: 3

         msgFlags          : 0x8002

         msgMid            : [0.0.10197370]

         msgSrcMid         : midNULL

         msgSrcMidGroup    : midNULL

         msgOrigSrcThread  : fr_sms_adt

         msgOrigDestThread : to_hed_adt

         msgSrcThread      : fr_sms_adt

         msgDestThread     : to_hed_adt

         msgXlateThread    :

         msgSkipXlate      : 0

         msgSepChars       :

         msgNumRetries     : 0

         msgGroupId        : 0

         msgDriverControl  :

         msgRecordFormat   :

         msgRoutes         :

         msgUserData       :

         msgStaticIsDirty  : 0

         msgVariableIsDirty: 0

         msgTimeStartIb    : 1221491785.857

         msgTimeStartOb    : 1221491715.440

         msgTimeCurQueStart: 0.000

         msgTimeTotalQue   : 0.003

         msgTimeRecovery   : 1221491785.891

         msgEoConfig       : 0x0

         msgData (BO)      : 0x30000120

      Thanks

      Gena Gill

      Interface Analyst/Proj Mgr

      Skaggs Community Health Center

      gsgill@skaggs.net

    Viewing 0 reply threads
    • Author
      Replies
      • #65483
        Gena Gill
        Participant

          I found the problem on the one that is giving this error for every message.  There was a problem in the translation.  We recently migrated to a new engine, and this is the first time this thread was turned on.  It seems that the translation would not compile on the new engine, where it would compile without issues on the old one.  I was able to deactivate the offending parts of the translation.

      Viewing 0 reply threads
      • The forum ‘Cloverleaf’ is closed to new topics and replies.