Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi everyone,
I am facing quite a strange issue with Qlik View 64 bits. I use it to connect to a database via an ODBC connection.
It worked for a while and suddenly, I started to get an error message when trying to reload a report. This message is:
SQL Error:Could not connect to the server;
Could not create Socket.
SQL State:08001
SQL SELECT id
FROM "db"."public".table
Nothing has changed from the ODBC connection and indeed, it is used successfully by other tools.
Would anyone know where this would be coming from?
Thank you.
Which database and driver are you using?
The database is Postgresql 8.4 and the driver was taken here:
http://code.google.com/p/visionmap/wiki/psqlODBC
I´m not a great Postgre user.
Have checked the itens below?
1) Windows firewall
2) Postgre security: the user you´re using has the right to select that table?
Yes, all these points have been checked.
I have one system ODBC connection defined and all the tools use the same.
The ODBC settings are so the same for all the tools and only Qlik View fails even if it has worked before.
Have you checked for antivirus ? I used to have dropped connections when Kaspersky was running.
There are no antivirus or firewalls on the way.
The application just randomly works for a while and then fire this error.
Nothing as moved in between. Didn't even reboot the computer.
I really don't understand.
Hello,
Did you try using this odbc driver instead? I'm using this in a Windows 7 x64 environment without problems for the time being.
Hope that helps
Hi, I have tried indeed.
this is a 32 driver. It is usable under 64 Bits operating systems, but not with a 64 bits of Qlik View... Or I couldn't get it to work.
Sorry for not specifying.
You can create a user DSN running
%WINDIR%\SysWOW64\odbcad32.exe
Once you have set all necessary parameters, you will be able to access it normally from your ODBC Connect dialog in QlikView.
Hope that helps.
EDIT: It needs to be a user dsn. After trying with the driver you specified, it works better for me that the driver I posted, which actually worked on a Win 7 ultimate edition laptop connecting to two different 7 and 8 postgres servers. So I leave the comment just for information.