Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
Hi Community!
I added an ODBC data source onto my Enterprise Gateway and when I go to refresh from Power BI Service I receive the following error:
When I try to use a personal gateway instead, the refresh works. Currently I'm using ODBC 64-bit (ODBC Driver 17 for SQL Server) installed on the System DSN and using the same DSN on the Gateway connection string as specified in the ODBC driver.
Could it be I'm using the wrong ODBC Driver (even though it works on my personal gateway)? I use SSMS 18. Or there's a data source permission issue?
Thanks in advance!
Christina
Depending on the information you provide, there are 2 common reasons why the above packet error may occur:
1.The first is that the driver is installed, however, it doesn't match the number of bits of the code being run. It is important that the ODBC driver's executable file and link format (ELF) are the same as those of the application. In other words, for a 32-bit application, you need a 32-bit driver, and for a 64-bit application, you need a 64-bit driver.
2.Second, there was an error typing the name of the driver. It is also important to ensure that the spelling of the DSN matches the spelling of the DSN configured in the ODBC Manager. A letter error is all there is to a DSN mismatch.
Regarding the issue you raised, my solution is as follows:
1.First, you can check the exact driver name in the ODBC Administrator Tools:
Press the Windows key + R, then:
If on a 32-bit system
C:\Windows\System32\odbcad32.exe
If on the system at 64 bits
C:\Windows\SysWOW64\odbcad32.exe
2.Secondly, if you find that the driver is installed but may be the wrong bits, we recommend that you adjust the number of bits the program runs on or install a driver with a different number of digits.
Most modern programming languages and environments run on 64-bit by default but allow you to switch to 32-bit. But if it's 32 bits, if you want to change to 64 bits, you probably can't.
3.Finally, if the driver name section may contain special characters, it needs to be separated by curly braces and needs to exactly match the installed driver name, as shown in the ODBC Data Source Manager, including spaces and typographical characters, but not capitalization. Here's an example of an ODBC connection string:
DRIVER={DriverName};ParameterName1=ParameterValue1;ParameterNameN=ParameterValueN;
4.The following documents are what we hope will help you:
C# - Data source name not found and no default driver specified Exception Error - Stack Overflow
If you have a new discovery, please share your ideas with us.
Best Regards,
Leroy Lu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi @Anonymous,
Thank you! I saw my SSMS is a 32 bit application. I added a 32 bit ODBC driver to the System DSN, but when I went to look for the newly added ODBC data source in Power BI, it was showing as an available source. Maybe because my Power BI is a 64 bit application?
I reconfirmed the DSN name to make sure it was entered properly and didn't see any issues there.
Thank you,
Christina
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
56 | |
27 | |
23 | |
21 | |
19 |
User | Count |
---|---|
51 | |
24 | |
20 | |
20 | |
17 |