My nmbrs connector for Power BI takes a long time to refresh in Power BI desktop but (usually) completes eventually. However, when publishing it to Power BI Service I often receive the below error during the scheduled refresh. Do you have any advice as to why this happens and how I can overcome this?
DataSource.Error:
OData:
Request failed:
The underlying connection was closed:
An unexpected error occurred on a receive…
DataSourceKind = OData.
DataSourcePath = https://bridge-online.cloud/acme-nmbrs/odata4/Nmbrs.Views.VariableHourComponents@nms.
The exception was raised by the IDataReader interface.
Please review the error message and provider documentation for further information and corrective action.
Table: Nmbrs_Hours_Components.
I read the article where it says “…only requests from the current user are visible”. When accessing the Bridge Online Monitoring it prompted me to log in; I logged in with my current details as the initial setup was done by me using this account. However I don’t see anything in the logs there, seemingly only my own activity in the portal.
The error occurs only in Power BI Service using the scheduled refresh functionality (once per day).
The connection in invantive is set up in my account, but the nmbrs credentials from a colleague as nmbrs needed to associate an authorization key etc to an account with enough access. Initially I thought that I should then try logging into the Bridge Online Monitoring using their credentials but, perhaps obviously, didn’t exist.
itgenboe161
De gegevensdownload werd geannuleerd na 5 minuten, 25 seconden, waarschijnlijk door de gebruiker.
Optimaliseer uw query zoals beschreven op …
(…/odata4/Nmbrs.Views.VariableHourComponents@nms)
I had already implemented the suggested improvement to change the default timeout but that wasn’t enough. There are also no null values in the table where I am getting the error so i assume the improvement to skip null values will not do much. I’ll see what other improvements I can try.
