[egenix-users] Initial Install - Error 'vars not set'

Nick Albright nick.albright at v-space.org
Fri Jun 9 14:06:34 CEST 2006


On Fri, 9 Jun 2006, M.-A. Lemburg wrote:

> The ODBC trace won't help much here, since mxODBC is reporting
> an internal error.

  First off, thanks for all the helpful responses!

> Please compile mxODBC with debugging enabled and send us
> the generated mxODBC.log. This will have more interesting
> details :-) ...

  Excellent pointer!  The results follow.  = )

> Which versions of mxODBC, FreeTDS and iODBC are you using ? Have you
> setup FreeTDS correctly ? (e.g. it is possible that the TDS version is
> not correctly set)

  Pretty much the latest of them all, installing on a new server.  Which
is:

mxODBC: 2.0.7
FreeTDS: 0.63
iODBC: 3.52.4

  I was thinking that it was setup correctly, since my isql command
returned successfully, but I don't know how isql interfaces vs mxODBC.
Here is the output of the mxODBC.log:


-----Begin mxODBC.log-----
--- New Log Session --- Fri Jun  9 12:58:23 2006

Importing the mx.DateTime C API...
 mx.DateTime package found
 API object mxDateTimeAPI found
 API object loaded and initialized.
initmxODBC: Initializing ODBC API environment
initmxODBC:  henv=0x522f00
mxODBC_New: server='MSSQL', uid='USER', passwd='PASS', clearAC=1
mxODBC_InitConnection(0x2a955dd760):  bindmethod=2,
have_SQLDescribeParam=0, get
data_extensions=0x2a00000004, txn_capable=2
mxODBC_New: created new connection at 0x2a955dd760hdbc=0x5720a0
mxODBCursor_New: created new cursor '<no name>' at 0x2a955d0fa8,
hstmt=0x51e860
mxODBCursor_FreeVars: called for cursor at 0x2a955d0fa8
mxODBCursor_FreeVars: nothing to do
mxODBCursor_Execute: using direct execute for statement 'SELECT COUNT(*)
AS c FR
OM items'
mxODBCursor_Execute: number of params in statement: 0
mxODBCursor_Execute: executing command without parameters
mxODBCursor_FreeVars: called for cursor at 0x2a955d0fa8
mxODBCursor_FreeVars: nothing to do
mxODBCursor_PrepareOutput: colcount=-1 rowcount=-1
mxODBCursor_Free: called for cursor at 0x2a955d0fa8
mxODBCursor_FreeVars: called for cursor at 0x2a955d0fa8
mxODBCursor_FreeVars: nothing to do
mxODBCursor_FreeParameters: called for cursor at 0x2a955d0fa8
mxODBCursor_Close: called for cursor at 0x2a955d0fa8, hstmt=0x51e860
mxODBCursor_Close:   stmt cancelled
mxODBCursor_Close:   stmt freed
mxODBC_Free: called for connection at 0x2a955dd760
mxODBC_Close: called for connection at 0x2a955dd760, closed=0
mxODBC_Close:  disconnect
mxODBC_Close:  free connection
-----End mxODBC.log-----

  Once again thanks for all the help!  I had tested on this on a beta
setup on an old machine and it worked fine.  The only difference I can see
is that this is a 64 bit OS/arch?

  Thanks,
   -Nick

> >>
> >> -----Begin isql-----
> >> $ isql  -v MSSQL USER PASS
> >> +---------------------------------------+
> >> | Connected!                            |
> >> |                                       |
> >> | sql-statement                         |
> >> | help [tablename]                      |
> >> | quit                                  |
> >> |                                       |
> >> +---------------------------------------+
> >> SQL> SELECT COUNT(*) AS c FROM items;
> >> +------------+
> >> | c          |
> >> +------------+
> >> | 3897       |
> >> +------------+
> >> SQLRowCount returns 1
> >> 1 rows fetched
> >> SQL>
> >> -----End isql-----

---
"And a line of code not written is a 100% guaranteed correct line of code."
	-- Alan Kay





More information about the egenix-users mailing list