Qlik Community

Qlik Sense Deployment & Management

Discussion board where members learn more about Qlik Sense Installation, Deployment and Management.

Announcements
BARC’s The BI Survey 19 makes it official. BI users love Qlik. GET REPORT
Highlighted
Partner
Partner

Consumer Node - no Reload (Database connection not available?)

hi again,

so, after fixing the Load Balancing, i have the next "problem".

on the central node we created some ODBC connections, working fine.

now i get the message that "no default driver installed". 

i guess this happens when iam connected to the consumer node. 

on the consumer note no odbc connections are installed.  

do i have to configure odbc connections on the consumer node like on the central node, or can i apply a rule in the qmc to get that access?

 

thanks again

1 Solution

Accepted Solutions
Partner
Partner

Re: Consumer Node - no Reload (Database connection not available?)

found the solution:

https://community.qlik.com/t5/Qlik-Sense-Deployment-Management/ODBC-and-OLE-Connections-not-working-...

Re: ODBC and OLE Connections not working in Qlik Sense September 2017

Figured this out thanks to the quick help from the Qlik Support team. This was happening because the ODBC and OLE Engines were only installed on the Central Node.

Load balancing was enabled and I was being routed to a RIM node that did not have the ODBC connection or OLE Engines installed.

The solution was to install the ODBC connection or OLE Engines on all nodes.

 

View solution in original post

1 Reply
Partner
Partner

Re: Consumer Node - no Reload (Database connection not available?)

found the solution:

https://community.qlik.com/t5/Qlik-Sense-Deployment-Management/ODBC-and-OLE-Connections-not-working-...

Re: ODBC and OLE Connections not working in Qlik Sense September 2017

Figured this out thanks to the quick help from the Qlik Support team. This was happening because the ODBC and OLE Engines were only installed on the Central Node.

Load balancing was enabled and I was being routed to a RIM node that did not have the ODBC connection or OLE Engines installed.

The solution was to install the ODBC connection or OLE Engines on all nodes.

 

View solution in original post