Announcement

Collapse

NextGen (Mirth) Connect 3.9.1 Released!

NextGen (Mirth) Connect 3.9.1 is now available as an appliance update and on our GitHub page. This release contains bug fixes and adds support for eHealth Exchange UDDI providers in the Interoperability plugin. 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

Mirth v1.2 - FAQ for Error deploying channels / Directory: [Path] exists but isn't a directory

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

  • Mirth v1.2 - FAQ for Error deploying channels / Directory: [Path] exists but isn't a directory

    ==============================
    Environment:
    Mirth v1.2 running as service, Java 1.5 Update 9, Windows XP Pro
    Channel: File Reader to Database

    INBOUND folder is on a different network domain and shared with "Full Control" for everyone.
    ==============================

    The logon account for Mirth v1.2 service should be from the same domain where the INBOUND folder share is created.

    Mirth v1.2 throws following exception otherwise:

    ===============================
    WARN 2006-11-13 15:18:13,821 [Thread-0] com.webreach.mirth.server.Mirth: Error deploying channels.

    org.mule.config.ConfigurationException: MuleManager Failed to initialise (org.mule.config.ConfigurationException)
    at org.mule.config.builders.MuleXmlConfigurationBuild er.configure(MuleXmlConfigurationBuilder.java:196)
    at com.webreach.mirth.server.Mirth.startMule(Mirth.ja va:131)
    at com.webreach.mirth.server.Mirth.restartMule(Mirth. java:117)
    at com.webreach.mirth.server.Mirth.run(Mirth.java:98)
    Caused by: org.mule.config.ConfigurationException: MuleManager Failed to initialise
    at org.mule.config.builders.MuleXmlConfigurationBuild er.configure(MuleXmlConfigurationBuilder.java:209)
    at org.mule.config.builders.MuleXmlConfigurationBuild er.configure(MuleXmlConfigurationBuilder.java:194)
    ... 3 more
    Caused by: org.mule.providers.FatalConnectException: ReconnectStrategy "org.mule.providers.SingleAttemptConnectionStrateg y" failed to reconnect receiver on endpoint "file:////TestServer/HL7Inbound"
    at org.mule.providers.SingleAttemptConnectionStrategy .doConnect(SingleAttemptConnectionStrategy.java:34 )
    at org.mule.providers.AbstractConnectionStrategy.conn ect(AbstractConnectionStrategy.java:67)
    at org.mule.providers.AbstractMessageReceiver.start(A bstractMessageReceiver.java:397)
    at org.mule.providers.AbstractConnector.registerListe ner(AbstractConnector.java:518)
    at org.mule.impl.model.AbstractModel.registerListener s(AbstractModel.java:230)
    at org.mule.impl.model.AbstractModel.start(AbstractMo del.java:364)
    at org.mule.MuleManager.start(MuleManager.java:730)
    at org.mule.config.builders.MuleXmlConfigurationBuild er.configure(MuleXmlConfigurationBuilder.java:207)
    ... 4 more
    Caused by: org.mule.providers.FatalConnectException: ReconnectStrategy "org.mule.providers.SingleAttemptConnectionStrateg y" failed to reconnect receiver on endpoint "file:////TestServer/HL7Inbound"
    at org.mule.providers.SingleAttemptConnectionStrategy .doConnect(SingleAttemptConnectionStrategy.java:34 )
    at org.mule.providers.AbstractConnectionStrategy.conn ect(AbstractConnectionStrategy.java:67)
    at org.mule.providers.AbstractMessageReceiver.connect (AbstractMessageReceiver.java:360)
    at org.mule.providers.SingleAttemptConnectionStrategy .doConnect(SingleAttemptConnectionStrategy.java:32 )
    ... 11 more
    Caused by: org.mule.providers.ConnectException: Initialisation Failure: Directory: //TestServer/HL7Inbound exists but isn't a directory
    at org.mule.providers.AbstractMessageReceiver.connect (AbstractMessageReceiver.java:373)
    at org.mule.providers.SingleAttemptConnectionStrategy .doConnect(SingleAttemptConnectionStrategy.java:32 )
    ... 14 more
    Caused by: java.io.IOException: Directory: //TestServer/HL7Inbound exists but isn't a directory
    at org.mule.util.Utility.openDirectory(Utility.java:8 5)
    at org.mule.providers.file.FileMessageReceiver.doConn ect(FileMessageReceiver.java:91)
    at org.mule.providers.AbstractMessageReceiver.connect (AbstractMessageReceiver.java:366)
    ... 15 more
    ===============================

  • #2
    Re: Mirth v1.2 - FAQ for Error deploying channels / Directory: [Path] exists but isn't a di

    Thanks for posting this, I will make sure it goes into the "Mirth Guide" we are building.

    -Chris
    Chris Lang

    Comment

    Working...
    X