Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello Community,
We have a series of QV models connected remotely to different Jade databases. Till now these databases were all 32bits but we have just upgraded to Jade 64 bit. Our QlikView is 64bit so we previously had to 'force 32 bit' in my database connection screen.
I have now installed the ODBC driver in JADE , then opened QlikView and in the "ODBC Administrator 64 bit" I have set up a System DNS to connect to the jade database.
When I run a script though, I get the following error message:
SQL##f - SqlState: IM014, ErrorCode: 0, ErrorMsg: [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application
ODBC CONNECT64 TO [Client-Thin] (XUserId is [..], XPassword is [...])
What am I missing?
Regards,
fcrysss
Hi,
Try selecting Force 32 Bit option in Expression Editor below the ODBC list box.
Check below thread
http://community.qlik.com/blogs/qlikviewdesignblog/2014/02/10/odbc-confusion
Hope it helps you.
Regards,
Jagan.
Non dimentichi nulla, penso che sia il driver ODBC non compatibile, prova ad installare altre versioni di driver (Magari più vecchie)
Ok Alessandro. Thanks, I'll try...
Ciao
Cristina
Hi,
Try selecting Force 32 Bit option in Expression Editor below the ODBC list box.
Check below thread
http://community.qlik.com/blogs/qlikviewdesignblog/2014/02/10/odbc-confusion
Hope it helps you.
Regards,
Jagan.
That is a great thread! Thank you very much Jagan.
So your trick has fixed some of the models, but there is a small percentage of models that are run on a different server to where the database reside.
I have copied the jadodbc.dll files also where QlikView runs from, but I can't still see the jade driver on the list when I open the ODBC Administrator 64 bit from QlikView.
Getting there...
Thank you Jagan.
Hi Cristina,
Connect to database normally how you did earlier and enable Force 32 Bit option and check whether it works.
Regards,
Jagan.
Hello Jagan,
I actually realised I had not set up the DSN properly. All good now!
Thank you very much for the help.
C.