Forum Discussion
ODBC DataSource.Error when expanding a table
- 9 years ago
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
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
- haroldvandekamp9 years agoNew Member
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
- v-qiuyu-msft9 years agoCommunity Support
- haroldvandekamp9 years agoNew Member
No progress at the moment because of the holiday. Can take up until September.