Announcement

Collapse

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

Sql database error

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

  • Sql database error

    Hello,

    I have changed Mirth connection to database SQL but when i tried to log in to the administrator I got this error "verify that server is up and information is valid"

    and here is my error log

    INFO | jvm 1 | 2007/12/02 12:28:04 | WARN 2007-12-02 12:28:04,078 [SslListener0-1] org.mortbay.jetty.context./: /users:
    INFO | jvm 1 | 2007/12/02 12:28:04 | com.webreach.mirth.server.controllers.ControllerEx ception: java.sql.SQLException: Network error IOException: Connection refused: connect
    INFO | jvm 1 | 2007/12/02 12:28:04 | at com.webreach.mirth.server.controllers.UserControll er.authorizeUser(UserController.java:116)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at com.webreach.mirth.server.servlets.UserServlet.log in(UserServlet.java:114)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at com.webreach.mirth.server.servlets.UserServlet.doP ost(UserServlet.java:62)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at javax.servlet.http.HttpServlet.service(HttpServlet .java:616)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at javax.servlet.http.HttpServlet.service(HttpServlet .java:689)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:428)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at org.mortbay.jetty.servlet.ServletHandler.dispatch( ServletHandler.java:666)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:568)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at org.mortbay.http.HttpContext.handle(HttpContext.ja va:1530)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at org.mortbay.http.HttpContext.handle(HttpContext.ja va:1482)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at org.mortbay.http.HttpServer.service(HttpServer.jav a:909)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at org.mortbay.http.HttpConnection.service(HttpConnec tion.java:816)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at org.mortbay.http.HttpConnection.handleNext(HttpCon nection.java:982)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at org.mortbay.http.HttpConnection.handle(HttpConnect ion.java:833)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at org.mortbay.http.SocketListener.handleConnection(S ocketListener.java:244)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at org.mortbay.util.ThreadedServer.handle(ThreadedSer ver.java:357)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at org.mortbay.util.ThreadPool$PoolThread.run(ThreadP ool.java:534)
    INFO | jvm 1 | 2007/12/02 12:28:04 | Caused by: java.sql.SQLException: Network error IOException: Connection refused: connect
    INFO | jvm 1 | 2007/12/02 12:28:04 | at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(C onnectionJDBC2.java:372)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at net.sourceforge.jtds.jdbc.ConnectionJDBC3.<init>(C onnectionJDBC3.java:50)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at net.sourceforge.jtds.jdbc.Driver.connect(Driver.ja va:178)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at java.sql.DriverManager.getConnection(DriverManager .java:525)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at java.sql.DriverManager.getConnection(DriverManager .java:171)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at com.ibatis.common.jdbc.SimpleDataSource.popConnect ion(SimpleDataSource.java:580)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at com.ibatis.common.jdbc.SimpleDataSource.getConnect ion(SimpleDataSource.java:222)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at com.ibatis.sqlmap.engine.transaction.jdbc.JdbcTran saction.init(JdbcTransaction.java:48)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at com.ibatis.sqlmap.engine.transaction.jdbc.JdbcTran saction.getConnection(JdbcTransaction.java:89)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at com.ibatis.sqlmap.engine.mapping.statement.General Statement.executeQueryForObject(GeneralStatement.j ava:104)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at com.ibatis.sqlmap.engine.impl.SqlMapExecutorDelega te.queryForObject(SqlMapExecutorDelegate.java:566)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at com.ibatis.sqlmap.engine.impl.SqlMapExecutorDelega te.queryForObject(SqlMapExecutorDelegate.java:541)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at com.ibatis.sqlmap.engine.impl.SqlMapSessionImpl.qu eryForObject(SqlMapSessionImpl.java:106)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at com.ibatis.sqlmap.engine.impl.SqlMapClientImpl.que ryForObject(SqlMapClientImpl.java:83)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at com.webreach.mirth.server.controllers.UserControll er.authorizeUser(UserController.java:107)
    INFO | jvm 1 | 2007/12/02 12:28:04 | ... 16 more
    INFO | jvm 1 | 2007/12/02 12:28:04 | Caused by: java.net.ConnectException: Connection refused: connect
    INFO | jvm 1 | 2007/12/02 12:28:04 | at java.net.PlainSocketImpl.socketConnect(Native Method)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at java.net.PlainSocketImpl.doConnect(PlainSocketImpl .java:333)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at java.net.PlainSocketImpl.connectToAddress(PlainSoc ketImpl.java:195)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at java.net.PlainSocketImpl.connect(PlainSocketImpl.j ava:182)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at java.net.SocksSocketImpl.connect(SocksSocketImpl.j ava:366)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at java.net.Socket.connect(Socket.java:507)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at java.lang.reflect.Method.invoke(Method.java:585)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at net.sourceforge.jtds.jdbc.SharedSocket.createSocke tForJDBC3(SharedSocket.java:289)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at net.sourceforge.jtds.jdbc.SharedSocket.<init>(Shar edSocket.java:250)
    INFO | jvm 1 | 2007/12/02 12:28:04 | at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(C onnectionJDBC2.java:297)
    INFO | jvm 1 | 2007/12/02 12:28:04 | ... 30 more

    Could any one help me with this?inch:

    Regards,

  • #2
    Re:Sql database error

    This seems that Mirth can't connect to this database.

    Comment


    • #3
      Re:Sql database error

      Sure!

      But I do not know why?
      I have run SQL server script which attached with Mirth files to create Mirth database
      and I am connecting using user "sa" with a password

      Did I miss any thing else?!

      please help

      Comment


      • #4
        Re:Sql database error

        What is the url you've used to the sql server ?

        You could test if the db at sql server is fine: try to connect to it using a genera purpose jdbc tool (db Visualizer, aqua data studio, etc...) This way you could use the jdbc string too.

        User "sa" is used for the derby database. You should use the one you've used to create the SQL server db.

        Comment


        • #5
          Re:Sql database error

          Hi all,

          what SQL database version is?. If you are using MS SQL 2005 you should configure its surface in order to establish TCP/IP connections.

          Let us know about,

          Ricard Bernat

          Comment


          • #6
            Re:Sql database error

            My SQL server version is SQL server 2002

            And I could connect from UDL successfully using sa user

            any other suggestions?!

            Thanks for Help :blush:

            Comment


            • #7
              Re:Sql database error

              Hi all,

              sorry but, as far as I know, if you are talking about MS SQL Server this version (2002) does not exist!. Or SQL 2000 or SQL 2005, there was no other versions between those.

              Greetings,

              Ricard Bernat

              Comment


              • #8
                Re:Sql database error

                ┬┐UDL? This is fine, but try to access it using a Java tool. This way you can be sure about the URL to use at the JDBC configuration.

                Comment


                • #9
                  Re:Sql database error

                  JDBC connection string for SQL Server 2000 is:

                  jdbc:jtds:sqlserver://TestServer:1433/TestDB

                  NOTE: The forum is stripping of few characters. It is "read" as
                  jdbc colon jtds colon sqlserver://TestServer:1433/TestDB

                  TestServer: SQL Server 2000 Server Name

                  TestDB: Database Name

                  For SQL Server 2000, the default Port is 1433

                  To find out the port number of your SQL Server, Open Enterprise Manager / Right-click on server / Properties / General Tab / Network Configuration / TCP/IP / Properties.

                  Additional Information:
                  In the Microsoft KB article below, refer to the section, "1. Determine the TCP/IP port number of the instance of SQL Server."

                  How to connect to a named instance of SQL Server 2005 or SQL Server 2000 by using the client tools in the earlier version of SQL Server
                  http://support.microsoft.com/kb/265808

                  Hope this helps!

                  Comment

                  Working...
                  X