Forum Discussion
DMTS
- 9 years ago
Anonymous BIXL I get the feedback internally, the is a known issue with ODBC data source types. The PG implemented a change that should fix this issue. The fix is scheduled to hit Prod last Thursday and should be available sometime this week. They suggested to work around the issue follow below steps currently:
1. Go to manage gateways page and remove all ODBC data sources under their Enterprise Gateway
2. Publish / Import the affected workbook
3. Add back the ODBC data source under their Enterprise GatewayBest Regards,
Qiuyun Yu
Hi Qiuyun,
Thanks so much for your reply.
Do I have to publish it from a different machine? It will be hard to work in the future.
Our on-promise gateway is installed on a server and using a service account.
I am using an ODBC driver to connect to the data source under that gateway.
Right now, data source name under gateway is the same as my ODBC connection string. Do you think that's causing the problem?
Many thanks,
JS
Hi Anonymous,
I have the same problem right now working with odbc driver (over intersystem cache).
did you manage to resolve this ?
what kind of DB are you using with odbc ?
thanks.
- Anonymous9 years agoNot applicable
HI BIXL
unfortunately, no.
So far I found that, if i include two ODBC data sources (one under on-promise gateway, one does not), then i can publish.
But in power bi service, the data source cannot detect on-promise gateway.
we r using Apache Hive as warehouse and connect to power bi via odbc.
thanks and good luck ya!