Announcement

Collapse

Mirth Connect 4.1.0 Released!

Mirth Connect 4.1.0 is now available as an appliance update and on our GitHub page. Mirth Connect 4.1.0 includes new features such as new event log messages, additional fields to the Welcome to Mirth Connect screen, new information included in alerts as well as many smaller changes, updates, and improvements. This release also contains several improvements to commercial extensions. See the release notes for the list of fixes and updates.

Download | See What's New | Upgrade Guide | Release Notes

For discussion on this release, see this thread.
See more
See less

ERROR-300: Transformer error

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • ERROR-300: Transformer error

    We are trying to take a message recieved, not change it at all, then send it to another system. I don't need to modify it at all but I am getting this error.

    ERROR-300: Transformer error
    ERROR MESSAGE: Error evaluating transformer
    com.webreach.mirth.model.converters.SerializerExce ption: org.xml.sax.SAXParseException: Element type "c3R" must be followed by either attribute specifications, ">" or "/>".

  • #2
    Re:ERROR-300: Transformer error

    Are you receiving and forward XML data? If so, is your channel configured so? Also, is the XML you are receiving valid?
    Gerald Bortis | Chief Information Officer | Mirth Corporation

    Comment


    • #3
      Re:ERROR-300: Transformer error

      What version of mirth are you using? What format messages are you dealing with?

      If you are using 1.7 release (aka 1.7.0.3285), and you are using Hl7 2.x messages, does the message causing the error contain data which reads <c3R somewhere in the message?

      If so, you are seeing the bug I filled as:

      http://www.mirthproject.org/communit...owse/MIRTH-745

      The 1.7 release version of Mirth is unable to process Hl7 2.x messages if they contain a < anywhere in message and the type of error you are seeing is what it shows up as. We have reverted to using Mirth 1.7.0.3207 (the last 1.7 beta) which doesn't have this bug.

      Comment

      Working...
      X