The specified DSN contains an architecture mismatch between the Drvier
and Application.
what will solve this?
will it be buying ActiveTcl for 64 bit? and if yes will we need to
compile tclodbc or it will come with it?
Will compiled tclodbc for 64 bit work with tcl 32 bit? and if yes how
to do it?
Thanks
Are you running 32 bit TCL on the server running Windows Server 64 bit
and SqlServer 64 bit? If you are then you need to make sure that you
are using a 32 bit ODBC conenction. If you run Windows/system32/
odbcad32.exe you will get the setup screen for 32 bit ODBC - if you go
through the control panel you'll get a 64 bit version of odbc. So you
could try creating a DSN using odbcad32.exe and seeing if that then
works.
Jackson
I tried but after I sadly failed I check the link of the odbc
management in the control panel and I saw that also it pointed to the
32.exe:
%windir%\system32\odbcad32.exe
is there another trick that could "make the magic"?
It might help if we could see the code that you are using; could you
post a minimal program that reproduces the problem? I'll try running
it against my 64 bit SqlServer database. If you run odbcad32.exe and
create a connection to your database and then use the Test button does
the new connection work?
Jackson
hi
first of all the test buttom for the new connection works. we use the
odbc driver SQL SERVER 6.01.7100.00 SQLSERVER32.dll 22/04/2009
we do not get to a stage that we can even run our code! simply:
package require tclodbc
database db <db name> <user> <password>
gives:
IM014 0 {[Microsoft][ODBC Driver Manager] The specified DSN contains
an architecture mismatch between the Driver and Application}
Hello,
googling for the error message brought me to this site.
http://www.zidsoft.com/x64.html
But I hve no further insight into this problem.
Ruediger
Not that it's any comfort to you but this just works for me. I've got
Tcl 8.4.18 installed with tclodbc 2.3 under Server 2003 R2 Enterprise
x64 Edition and SqlServer 2005 64 Bit. I can create a DSN and connect
to it with no problems at all.
Try using the odbcad32.exe under the SysWOW64 directory and see if
that works. After that I'm afraid I'm all out of ideas.
Jackson
The last trick did the job! When I defined the dsn with the
odbcad32.exe which is under sysWoW64 it worked. thanks for the
pointer. By the way on server 2003 sqlserver 2005 64 bit it was not
like this as it worked without any problem. But in this case windows
2008 sqlserver 2008 things got tougher. I wonder why the default odbc
configuration in the menu points to the exe under system32 but I will
leave this for another time.
thanks again.
Similar issue here connecting from vb.net even after setting up the
DSN using the 32-bit util - I also had to set the target cpu to x86 in
the compile options. Seems like one would think of that, but I
overlooked it. =)