com.mirth.connect.donkey.server.data.DonkeyDaoException

Channel ID 93c88a07-b6a9-4bb5-8a9b-59cbc006d922 does not exist

Solutions on the web5

  • Channel ID 93c88a07-b6a9-4bb5-8a9b-59cbc006d922 does not exist
  • via Mirth Project by Nick Rupley, 9 months ago
    java.sql.SQLException: Transaction (Process ID 63) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
  • via Mirth Project by Nick Rupley, 1 year ago
    java.sql.SQLException: Transaction (Process ID 56) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
  • Stack trace

    • com.mirth.connect.donkey.server.data.DonkeyDaoException: Channel ID 93c88a07-b6a9-4bb5-8a9b-59cbc006d922 does not exist at com.mirth.connect.donkey.server.data.jdbc.JdbcDao.getLocalChannelId(JdbcDao.java:2721) at com.mirth.connect.donkey.server.data.jdbc.JdbcDao.prepareStatement(JdbcDao.java:2613) at com.mirth.connect.donkey.server.data.jdbc.JdbcDao.updateStatistics(JdbcDao.java:379) at com.mirth.connect.donkey.server.data.jdbc.JdbcDao.addChannelStatistics(JdbcDao.java:354) at com.mirth.connect.donkey.server.data.DonkeyStatisticsUpdater.commit(DonkeyStatisticsUpdater.java:87) at com.mirth.connect.donkey.server.data.DonkeyStatisticsUpdater.run(DonkeyStatisticsUpdater.java:52)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You are the first who have seen this exception. Write a tip to help other users and build your expert profile.