203: Failure in OB Data TPS eval

Clovertech Forums Cloverleaf 203: Failure in OB Data TPS eval

  • Creator
    Topic
  • #122380
    Ib H
    Participant

      Can anyone tell me why I see this after migrating an integration from Cloverleaf 6.2 to 2022.09.03 ?

      What I really need, is to understand what it means – I know that there is not mush information to go on.
      The messages end up in the errordb, below is a sanitized version of a single message :

      msgHostName : prcloprod022v
      msgOrigSrcThread : tilFraWAS_ib
      msgOrigDestThread : push_MADS
      msgSrcThread : tilFraWAS_ib
      msgDestThread : push_MADS
      msgXlateThread :
      msgSkipXlate : 0
      msgSepChars :
      msgNumRetries : 0
      msgGroupId : 0
      msgDriverControl : {CONNID 0} {IPVERSION 4} {CLIENTIP 10.161.5.61} {CLIENTPORT 37924} {_TRXID_ MADS-update}
      msgRecordFormat :
      msgRoutes :
      msgUserData : {SRCUUID bf6fb9ca-fa1e-46a5-8d29-dc82d53a97a7} {SIZE 2180} {FILENAME msgFrom62{bf6fb9ca-fa1e-46a5-8d29-dc82d53a97a7}.xml} {FROMFILE msgFrom62{bf6fb9ca-fa1e-46a5-8d29-dc82d53a97a7}.xml} {FROMDIR {listening on port: 22022}} {TRXID MADS-update} {SUBSCRIBER MADS} {RECEIVER receiver} {RECEIVERTYPE RSD} {SENDER SYS005_RSD_CLOVERLEAF} {SENDERTYPE RSD} {MSGID 34444766} {CPR1 0123456789} {CPR2 {}} {FORNAVN ChristianName} {EFTERNAVN Surname} {MSGTYPE INT015} {SENDERSYSTEMID SYS066_RSD_WAS} {RECEIVERSYSTEMID SYS005_RSD_CLOVERLEAF} {RETURNTOSENDER tilFraWAS_ib}
      msgStaticIsDirty : 0
      msgVariableIsDirty: 0
      msgRetryTimes :
      msgTimeStartIb : 1773649214.994(Mon Mar 16 09:20:14 2026)
      msgTimeStartOb : 1773649215.307(Mon Mar 16 09:20:15 2026)
      msgTimeCurQueStart: 0.000(Thu Jan 1 01:00:00 1970)
      msgTimeTotalQue : 0.007
      msgTimeRecovery : 1773649215.269(Mon Mar 16 09:20:15 2026)
      msgEoConfig : 0x(nil)
      msgData (BO) : 0x0x7face98b9248
      message : ‘<?xml version=”1.0″ encoding=”ISO-8859-1″ standalone=”yes” ?>…

      Yours sincerely

      Ib Højme

    Viewing 2 reply threads
    • Author
      Replies
      • #122381
        Ib H
        Participant

          I found out what the issue was, it was in an UPOC that relied on another UPOC being run beforehand 😐
          Side-effect hit again.
          So the ‘203: Failure in OB DataTPS eval’ is actually spot on – I just had to look in the right logfile.

          /Ib

        • #122382
          Peter Heggie
          Participant

            Is there any information in the process log that shows the error? Can you share that information?

            Peter Heggie
            PeterHeggie@crouse.org

          • #122383
            David Barr
            Participant

              You can also add “-c” to your hcidbdump command if you want to see TCL errors.

          Viewing 2 reply threads
          • You must be logged in to reply to this topic.