Mirth Connect 3.12.0 Released!

Mirth Connect 3.12.0 is now available as an appliance update and on our GitHub page. This release includes database performance improvements, improves visual HL7 representation, message pruning, keystore handling, PDF generation, community contributions, and fixes several security vulnerabilities. This release also contains many 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

Problems accessing SQL Server

  • Filter
  • Time
  • Show
Clear All
new posts

  • Problems accessing SQL Server

    Hi Guys!

    Thanks for your help...
    I just got connection with my SQL Server database.

    But I got some new problems.

    I created some channels and I was trying to see the messages received and the messages sent. But I got a problem, as follow:

    Caused by: java.sql.SQLException: The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value.

    I guess that I need to apply some different configuration on the date format.

    Does someone know wich date format mirth should have to use with SQL Server ?

    I got another error message as follow:

    Caused by: java.sql.DataTruncation: Data truncation

    That happens when I was trying just to see the events in the "Mirth Administrator".

    Seems that the table EVENT should use a different format of field, or should I to apply a different configuration to treat "text" fields ?

    Thank you.