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.
We want to analyze data from UNIT4 Multivers Online system using ODBC using the UNIT4 Multivers Online ODBC-driver. Using the Power BI ODBC connector we want to import the UNIT4 data. After setting up the connection we see tables inside the system, but when we click on a table to expand it we get an ODBC error. What is the best step to do to resolve this issue?
Error message:
DataSource.Error: ODBC: ERROR [UNIT4] An error occurred on the server
Details:
DataSourceKind=Odbc
DataSourcePath=dsn=UNIT4 Multivers Online
OdbcErrors=Table
Solved! Go to Solution.
Hi @haroldvandekamp,
I got below information internally:
We do quite a few operations against the driver which Excel does not do. In this case, we’re trying to get the primary keys for schema: SYSADM, table: DEBITEUR and the server is returning an error. This may indicate a bug in the driver or that the user is missing certain permissions on the server which are necessary to get the primary keys of the table.
Best Regards,
Qiuyun Yu
Hi @haroldvandekamp,
1. Please check if the error occurs when you expand data from this specific table or any other tables.
2. Check if the issue related to Power BI desktop. You can get data use ODBC data source in Excel to see if data can be retrieved.
3. Please update the Power BI desktop to the latest version.
Best Regards,
Qiuyun Yu
Hi Qiuyun Yu,
Thank you for the reply.
Best regards,
Harold van de Kamp
Hi @haroldvandekamp,
Please enable the desktop trace log, then repeat steps to reproduce the issue. Share trace log here.
Best Regards,
Qiuyun Yu
I've just created the trace logs using Power BI Desktop, you can find the log files in a zip file in Unit4 Multivers Online in Power BI trace log.zip.
Some things I've seen in the logs:
Any tips?
Hi @haroldvandekamp,
I got below information internally:
We do quite a few operations against the driver which Excel does not do. In this case, we’re trying to get the primary keys for schema: SYSADM, table: DEBITEUR and the server is returning an error. This may indicate a bug in the driver or that the user is missing certain permissions on the server which are necessary to get the primary keys of the table.
Best Regards,
Qiuyun Yu
Hi @v-qiuyu-msft,
Thanks for the research of the internal team and response.
Ok, I will investigate this with my customer and check whether the user is missing certain permissions or we can contact the provider of the ODBC Driver.
Best regards,
Harold van de Kamp
Hi @haroldvandekamp,
What's the progress about this issue?
Best Regards,
Qiuyun Yu
No progress at the moment because of the holiday. Can take up until September.
I have almost the same error;
DataSource.Error: ODBC: ERROR [HY000] SQLPrepare: Driver not capable--ORDER BY is not supported
Is there already a solustion?
Thanks for your efforts
Boudewijn
Hi @haroldvandekamp,
I have sent the trace log to senior engineer to analyze the issue. Will let you know if I get any information.
Best Regards,
Qiuyun Yu
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 |
---|---|
15 | |
11 | |
8 | |
8 | |
7 |
User | Count |
---|---|
15 | |
13 | |
9 | |
7 | |
6 |