Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Reply
haroldvandekamp
New Member

ODBC DataSource.Error when expanding a table

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

 

Power BI errror navigating UNIT4 Multivers Online tables using ODBC

1 ACCEPTED 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

Community Support Team _ Qiuyun Yu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

10 REPLIES 10
v-qiuyu-msft
Community Support
Community Support

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

 

Community Support Team _ Qiuyun Yu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Hi Qiuyun Yu,

 

Thank you for the reply.

 

  1. Yes, it happens for each table shown in the screenshot
  2. Retrieving the data using ODBC in Excel works
  3. We are using the latest Power BI Desktop version, we updated it yesterday to the latest version

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

Community Support Team _ Qiuyun Yu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

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:

  • "InfoType":"SQL_CONVERT_WCHAR","Exception":"Exception:\r\nExceptionType: Microsoft.Mashup.Engine1.Library.Odbc.Interop.OdbcException, Microsoft.MashupEngine, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35\r\nMessage: ERROR [UNIT4] SQLGetInfoW: unknown information type specified.
  • DataMashup.Trace Error: 24579 : {"Start":"2017-07-21T11:18:33.0825944Z","Action":"Engine/IO/Odbc/Command/GetPrimaryKeys","HostProcessId":"131972","CatalogName":null,"SchemaName":"SYSADM","TableName":"DEBITEUR","Exception":"Exception:\r\nExceptionType: Microsoft.Mashup.Engine1.Library.Odbc.Interop.OdbcException, Microsoft.MashupEngine, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35\r\nMessage: ERROR [UNIT4] Er is een fout opgetreden op de server.\r\nStackTrace:\n at Microsoft.Mashup.Engine1.Library.Odbc.Interop.OdbcUtils.HandleError(OdbcHandle hrHandle, RetCode retcode)\r\n 

 

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

Community Support Team _ Qiuyun Yu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

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

Community Support Team _ Qiuyun Yu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

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

Community Support Team _ Qiuyun Yu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Helpful resources

Announcements
Microsoft Fabric Learn Together

Microsoft Fabric Learn Together

Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

Find out what's new and trending in the Fabric Community.

Top Solution Authors
Top Kudoed Authors