Clovertech

ODBC Drivers: Connect5.2 SQL Server incomplete error msgs

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › ODBC Drivers: Connect5.2 SQL Server incomplete error msgs

  • Creator
    Topic
  • July 2, 2008 at 11:21 am #50149
    Jim Kosloskey
    Participant

      We are testing Cloverleaf(R) 5.6 ODBC drivers (Connect5.2).

      We have successfully connected to an Oracle DB.

      In trying to connect to an SQL Server DB we are getting an error. That is not a big surprise because we are not sure our connection parameters are correct or that the server is configured properly at this point.

      What is a big surprise is we are getting a shortened error message when doing a getdiagrec call.

      I have forced connection errors for the Oracle DB and we get full error messages.

      I checked the Data Direct Web Page Knowledge Base and this is a known problem with Connect5.2 when the LANG environment variable is not set to en_US. Our LANG environment variable is set to en_US.

      Has anyone else encountered this problem with SQL Server and the ODBC drivers (Connect5.2) and if so did you get the complete error messages to show?

      Also in the odbc.ini file generated as part of the Cloverleaf(R) 5.6 Connect5.2 install, the Drivers argument has a malformed directory path for every DSN and there is a weird DSN ‘hawaii3’ (or something like that).

      Anyone else noticed this in the odbc.ini file?

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

    • Creator
      Topic
    Viewing 0 reply threads
    • Author
      Replies
      • July 2, 2008 at 12:26 pm #65019
        John Hamilton
        Participant

          Jim, I have three differnet SQL server connections.

          Yes I do get a truncated error when I get the errors.  I really never got that resolved I had enough to figure out what the error was and resolved it.

          The host name is another story. Like I said we have three. I tried the DNS look up name it worked for one but not the other two. One I had to use the IP address the other I had to use the fully quilified host name (xyz.ksnet.com). Very strange because from the command line I could ping them based on any and all names.  Plus when make the DSN in my odbc on my PC I could use any of the names as well.   Just could not get them to resolve correctly or even the same way in that odbc.ini.  But they are working and sometimes that is all you have time to do.

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