Error using Direct Discovery on Access point

[punitpopli]

Hi,

We are using Direct discovery in one of the application using "Direct Query" syntax.

It functioning as expected on Desktop client but giving an error as :: ‘Database Connection Failed’ while accessing the same feature from access point.

Is their any specific setting that needs to be done on QMC?

Does anyone had face similar issue in the past

Could anyone please share their thoughts on the same?

Thanks,

Punit

[avinashelite]

Check this documetns

QlikView Direct Discovery FAQ 11.2_SR5.pdf

QlikView 11 2 SR5 Direct Discovery Technical Addendum.pdf

[Anonymous]

Which kind of connection do you use, OLEDB or ODBC?

Which QV version do you have?

Which kind of chart do you use, tablebox or diagramm?

[punitpopli]

Hi dimitri.obrant‌

Please find the details in below :

Connection = ODBC

QV Version : 11.2 SR 12

Only one table for testing purpose

let me know if any other information required.

Thanks,

Punit

[Anonymous]

Do you have the same ODBC connection on your QV server?

You can try it with OLEDB. In this case you don't need additionaly connection on the server. OLEDB connection will be saved in qvw file.

[punitpopli]

Hi dimitri.obrant‌,

yes, same connection is available on QV server.

sure, will check with OLEDB.

Thank,

Punit

[mukesh24]

Hi,

Have you check trace log for your ODBC connection?

Regards,

Mukesh

[Anonymous]

‘Database Connection Failed’ is the error message you get if you forget to use aggregation functions (i.e. max() ) when needed.

[punitpopli]

Hi barytonsaxen.se‌

Thanks for your response.

But, Aggregation functions are used in the script.

Thanks,

Punit

[Anonymous]

Yes, I was wrong... When missing the aggregation you'll get a "-".

Annoying... I got this message a lot too, but now I can't remember when/how or how I fixed it. It had something to do with the script. As I mentioned in another thread we bailed out and made a view in the database where data was already prepared.

It can have been when using joins in a wrong way or any other not allowed construction in the script. The error messages when using DD are unfortunately very vague... I'm sure it had _nothing_ to do with the db not being accessible. The problem was in the script, not the connection.

The connection is easy to test. Just remove the DD and load a table.