No announcement yet.

DefaultEventController error adding event ERROR: relation "event" does not exist

  • Filter
  • Time
  • Show
Clear All
new posts

  • DefaultEventController error adding event ERROR: relation "event" does not exist

    I keep seeing this error in the Mirth server logs. We recently upgraded from to We have it installed on RHEL 5.4 and use Postgres as the local database for Mirth. Did the upgrade require some database scripting? If it did, it didn't fire off during the install using the .sh file.

    [2011-06-17 16:48:34,474] ERROR (com.mirth.connect.server.controllers.DefaultEvent Controller:94): Error adding event.
    com.ibatis.common.jdbc.exception.NestedSQLExceptio n: --- The error occurred in postgres/postgres-event.xml. --- The error occurred while applying a parameter map. --- Check the Event.insert-event-param. --- Check the statement (update failed). --- Cause: org.postgresql.util.PSQLException: ERROR: relation "event" does not exist
    at com.ibatis.sqlmap.engine.mapping.statement.MappedS tatement.executeUpdate(
    at com.ibatis.sqlmap.engine.impl.SqlMapExecutorDelega te.insert(
    at sert(
    at com.ibatis.sqlmap.engine.impl.SqlMapClientImpl.ins ert(
    at com.mirth.connect.server.controllers.DefaultEventC ontroller.addEvent(
    at com.mirth.connect.server.mule.ExceptionStrategy.lo gException(
    at faultHandler(DefaultComponentExceptionStrategy.jav a:76)
    at faultHandler(
    at org.mule.impl.DefaultExceptionStrategy.handleRouti ngException(
    at org.mule.impl.AbstractExceptionListener.exceptionT hrown(
    at org.mule.providers.AbstractMessageReceiver.handleE xception(
    at com.mirth.connect.connectors.mllp.MllpMessageRecei ver$
    at .java:290)
    at eadPoolExecutor.runWorker( 1061)
    at eadPoolExecutor$ :575)
    at by: org.postgresql.util.PSQLException: ERROR: relation "event" does not exist
    at org.postgresql.core.v3.QueryExecutorImpl.receiveEr rorResponse(
    at org.postgresql.core.v3.QueryExecutorImpl.processRe sults(
    at org.postgresql.core.v3.QueryExecutorImpl.execute(Q
    at org.postgresql.jdbc2.AbstractJdbc2Statement.execut e(
    at org.postgresql.jdbc2.AbstractJdbc2Statement.execut eWithFlags(
    at org.postgresql.jdbc2.AbstractJdbc2Statement.execut e(
    at org.apache.commons.dbcp.DelegatingPreparedStatemen t.execute(
    at org.apache.commons.dbcp.DelegatingPreparedStatemen t.execute(
    at com.ibatis.sqlmap.engine.execution.SqlExecutor.exe cuteUpdate(
    at com.ibatis.sqlmap.engine.mapping.statement.MappedS tatement.sqlExecuteUpdate( )
    at com.ibatis.sqlmap.engine.mapping.statement.MappedS tatement.executeUpdate(
    ... 15 more

  • #2
    The schema should have been automatically upgraded when you first started 2.1.0. Was there an error in the log the first time you started 2.1.0? If so, can you post that?
    Jacob Brauer
    Director, Software Development
    NextGen Healthcare