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,
Have you tried the second way in my original post? In your .PBIX file, is only one ODBC data source exists, connect to Apache Hive?
Please enable desktop log trace to see if you can find the useful information during publish time.
Best Regards,
Qiuyun Yu
- Anonymous9 years agoNot applicable
HI v-qiuyu-msft
I did try the 2nd method you suggest. I can publish but cannot find on-promise gateway.
BIXLCurrently, the only way for me to publish from my machine and detect gateway is:in PB desktop, include 2 odbc data source: a) under on-promise gateway, b) some other odbc data source(X)
Publish the report, delete source (X), publish and replace, then I am able to find the right gateway.
- v-qiuyu-msft9 years agoCommunity Support
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- Anonymous9 years agoNot applicable
Hi v-qiuyu-msft many thanks for providing feedbacks on this.
Could you please let me know when this issues is solved? Appreciate it!