Skip to main content
Announcements
See what Drew Clarke has to say about the Qlik Talend Cloud launch! READ THE BLOG
cancel
Showing results for 
Search instead for 
Did you mean: 
realpixel
Creator
Creator

Problem ODBC driver on QV server

Hello,

I have a problem with a QV report published on my QV server.

From my server, I create a ODBC driver, and the test of connection is completed successfully but the reload from QV console not work

21/10/2013 17:00:02: 0012  ODBC CONNECT*XUserId*XPassword*

21/10/2013 17:00:02:       Error: SQL##f - SqlState: IM002, ErrorCode: 0, ErrorMsg: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

21/10/2013 17:00:02:       General Script Error

21/10/2013 17:00:02:       Execution Failed

21/10/2013 17:00:02:      Execution finished.

Someone have an idea?

1 Solution

Accepted Solutions
Clever_Anjos
Employee
Employee

It´s important to create your ODBC entry as System, not User so all users can connect to your ODBC entry

View solution in original post

5 Replies
patricio
Contributor III
Contributor III

You can check if your ODBC is 32 bits in which case you can use connect32 instead of connect.

realpixel
Creator
Creator
Author

Hello thank you for your reply.

But I have the same problem that I use connect or connect32

21/10/2013 19:59:10:  Execution started.
21/10/2013 19:59:10:  QlikView Version:11.00.11282.0
21/10/2013 19:59:10:  CPU Target                x64
21/10/2013 19:59:10:  Operating System          Windows Server 2008 R2 Standard  (64 bit edition)
21/10/2013 19:59:10:  Wow64 mode                Not using Wow64
21/10/2013 19:59:10:  MDAC Version              6.1.7600.16385
21/10/2013 19:59:10:  MDAC Full Install Version 6.1.7600.16385
21/10/2013 19:59:10:  PreferredCompression      2
21/10/2013 19:59:10:  EnableParallelReload      1
21/10/2013 19:59:10:  ParallelizeQvdLoads       1
21/10/2013 19:59:10:  AutoSaveAfterReload       0
21/10/2013 19:59:10:  BackupBeforeReload        0
21/10/2013 19:59:10:  EnableFlushLog            0
21/10/2013 19:59:10:  SaveInfoWhenSavingFile    0
21/10/2013 19:59:10:  UserLogfileCharset        0
21/10/2013 19:59:10:  OdbcLoginTimeout          -1
21/10/2013 19:59:10:  OdbcConnectionTimeout     -1
21/10/2013 19:59:10:  ScriptWantsDbWrite        false
21/10/2013 19:59:10:  ScriptWantsExe            false
21/10/2013 19:59:10:  LogFile CodePage Used:    1252

21/10/2013 19:59:10: 0002  SET ThousandSep=' '

21/10/2013 19:59:10: 0003  SET DecimalSep=','

21/10/2013 19:59:10: 0004  SET MoneyThousandSep=' '

21/10/2013 19:59:10: 0005  SET MoneyDecimalSep=','

21/10/2013 19:59:10: 0006  SET MoneyFormat='# ##0,00 €;-# ##0,00 €'

21/10/2013 19:59:10: 0007  SET TimeFormat='hh:mm:ss'

21/10/2013 19:59:10: 0008  SET DateFormat='DD/MM/YYYY'

21/10/2013 19:59:10: 0009  SET TimestampFormat='DD/MM/YYYY hh:mm:ss[.fff]'

21/10/2013 19:59:10: 0010  SET MonthNames='janv.;févr.;mars;avr.;mai;juin;juil.;août;sept.;oct.;nov.;déc.'

21/10/2013 19:59:10: 0011  SET DayNames='lun.;mar.;mer.;jeu.;ven.;sam.;dim.'

21/10/2013 19:59:10: 0012  ODBC CONNECT32*XUserId*XPassword*

21/10/2013 19:59:10:   Error: SQL##f - SqlState: IM002, ErrorCode: 0, ErrorMsg: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
21/10/2013 19:59:10:   General Script Error
21/10/2013 19:59:10:   Execution Failed
21/10/2013 19:59:10:  Execution finished.
Clever_Anjos
Employee
Employee

It´s important to create your ODBC entry as System, not User so all users can connect to your ODBC entry

Not applicable

Hello Clever,

what do you mean with creating the ODBC entry as System? I have the same problem.

Clever_Anjos
Employee
Employee

System DSN as opposite of User DSN

Sem título.png