Forum Discussion
Authentication to ODBC data source
Hi,
I am having issues adding an ODBC data source to my online gateway. The data connection works like a charm in Desktop, but I am not able to authenticate through the same "anonymous" option online, where I receive the error message "Failed to update data source credentials: ODBC: ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified".
By researching previous related posts, I have tried to change up the security levels, tested all the three authentication options, using basic authentication when uploading to the service etc, but so far no results. Other sources from the same ODBC admin tool works succesfully in the same gateway.
By tracing the ODBC Administration Tool, it does not seem like PowerBI is even trying to connect, as no trace is generated.
Any suggestions would be greatly appreciated.
Thanks.
Hi ETA ,
Which data sources the report are connected to? Please check whether the gateway was installed in the same machine with the one which ODBC DSN exists. In addition, please review the following similar threads, hope they can resolve your problem.
Why am I getting “Data source name not found and no default driver specified” and how do I fix it?
Best Regards
7 Replies
I found this for you that might help
Thanks, but I don't believe that is relevant to our case, as we don't have access to the data lake directly. The data lake is part of our multitenant cloud ERP-solution, where we need to extract data through a jdbc driver
Hi ETA ,
Which data sources the report are connected to? Please check whether the gateway was installed in the same machine with the one which ODBC DSN exists. In addition, please review the following similar threads, hope they can resolve your problem.
Why am I getting “Data source name not found and no default driver specified” and how do I fix it?
Best Regards
Anonymous thanks for your reply, I will go through your suggested threads and give you feedback on whether or not I found a solution within the next couple of days.
Thanks again Anonymous , I found a solution based on inspiration from the links you provided. The issue was a minor difference in the ODBC-setup on the two different machines I was using.
