Forum

[MikeAtkinson]

We've been asked several times why Console gives the following error on trying to make a connection to the Kognitio Analytics Platform:

08001 [kognito] [wx2 driver] unable to connect to database server. Connection Timed out

This is almost certainly not a Console issue, the error comes from the Kognitio ODBC driver.

[markc]

What sort of things normally give that error?

Setting up the connection details wrongly (either providing the wrong IP address/port when specifying address and port in the Console connection dialog, or using a DSN which is specified wrongly) would be one way.

The database being down would be another.

A communication issue between the client and database would be a third (e.g. firewall preventing access, or some network infrastructure issue).

Are there any other ways?

[MikeAtkinson]

In order to try and resolve the problem, we recommend the following steps:

1. Open the ODBC administration tool, select the DSN connection and then click on "Configure...". Check that the IP address is correct. Some customers use ports other than the default of 6550, if that is the case for you check the port is specified in the IP address like "172.0.0.1:1234" where 1234 is the port number. The "Connection timeout (seconds)" may be set to 3 by default, if you are making a connection over the internet (or a VPN) increase this to 30 seconds.
2. Check that the Kognitio Analytics Platform is running by using the WxAdmin tool
3. Check that you can reach the Kognitio Analytics Platform, e.g. by doing a ping and a traceroute ("tracert" on Windows). NOTE: some networks block ping and traceroute, check with your system administrators.
4. Check also for dropped packets, excessive numbers of dropped packets may cause connections to fail, especially with a connection timeout of 3 seconds (see above).
5. Contact Kognitio support by raising a SalesForce case or via your Kognitio contact.

[MikeAtkinson]

It is possible to do a ping or traceroute (tracert on Windows) directly from within Console using Kog scripts. Using a script like:

Code: Select all

shell("ping 172.1.2.3");
shell("tracert 172.1.2.3");

This may take some time to complete as tracert may be slow.

[markc]

...remembering that sometimes ping can get through but firewalls still prevent connectivity, so the ping test is not a guarantee that connecting to the server on the relevant port for ODBC is possible. You could try to telnet to an IP address/port combination to reduce the risk there.