Clovertech

ODBC Error

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › ODBC Error

  • Creator
    Topic
  • June 16, 2009 at 5:09 pm #50975
    Rick Pritchett
    Participant

      Has anyone else seen this error?

      [0:TEST] Tcl error:

      msgId = message0

      proc = ‘odbc1’

      args = ”

      result = ‘ cannnot find Driver keyword entry for data source MMC-SQL-TEST’

      errorInfo: ‘

      cannnot find Driver keyword entry for data source MMC-SQL-TEST

    • Creator
      Topic
    Viewing 5 reply threads
    • Author
      Replies
      • June 16, 2009 at 5:40 pm #68253
        Jim Kosloskey
        Participant

          Rick,

          Check your odbc.ini file and make sure you have a dsn enty for the driver and that the driver location for the dsn is correct.

          I don’t use the odbc.ini file for specific DBs. Instad I use the dsn entries that are provided for the supported DBs and use execution time connect strings to adjust the individual settings as needed.

          email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

        • June 16, 2009 at 5:43 pm #68254
          Ron Archambault
          Participant

            Check your odbc.ini file for the

            [ MMC-SQL-TEST ]

            driver=//driver..

            Make sure the path to the driver is correct.

            Here’s one for SQL Server using 5.7

            Driver=/hci/qdx5.7/integrator/lib/Connect5.3/lib/CVmsss23.sl

          • June 17, 2009 at 6:39 pm #68255
            Rick Pritchett
            Participant

              ok here is what i found.  

              do i just need to copy and rename it and fill in the blanks?

              [SQLServer Wire Protocol]

              Driver=/quovadx/qdx5.7/integrator/lib/Connect5.3/lib/CVmsss23.so

              Description=DataDirect 5.3 SQL Server Wire Protocol

              Address=

              AlternateServers=

              AnsiNPW=Yes

              ConnectionRetryCount=0

              ConnectionRetryDelay=3

              Database=

              LoadBalancing=0

              LogonID=

              Password=

              QuotedId=No

              SnapshotSerializable=0

            • June 17, 2009 at 6:55 pm #68256
              Jim Kosloskey
              Participant

                Rick,

                No – you also need to add a dsn reference in the [ODBC Data Sources]section at the beginning of the odbc.ini file I think.

                There is a full set of user documentation available from Data Direct on their web site (www.datadirect.com).

                Download a copy – almost all of the answers you need will be in there.

                It appeares if you foobare the odbc.ini not only will your stuff not work but it is possible other already working dsns may not function – so – make sure you backup.

                That is one of the primary reasons we do not update the odbc.ini file but rather use connect time connection strings.

                email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

              • June 17, 2009 at 7:41 pm #68257
                Ron Archambault
                Participant

                  I agree with Jim, but if your site is like ours, they want this in the odbc.ini.

                  So, all you need to do is cut, paste and rename the DSN in the

                • June 17, 2009 at 8:29 pm #68258
                  Rick Pritchett
                  Participant

                    Jim can you briefly explain how your option works?

                • Author
                  Replies
                Viewing 5 reply threads
                • The forum ‘Cloverleaf’ is closed to new topics and replies.