topic Re: Refresh error, only on Onpremise Power BI Report server. Not on Desktop and not on PowerBI servi in Report Server

Refresh error, only on Onpremise Power BI Report server. Not on Desktop and not on PowerBI service

jacccodezwart — Wed, 08 Jan 2025 11:46:20 GMT

Hi all,

I have a problem I'm not able to solve myself. Hope you can help me.

My dashboard uses two datasources. One is an OData source, the other is a direct database connection.

SessionID: abb0eb89-bfd0-4fd0-8aa0-596c47fcf8b0
[0] -1055784932: DataFormat.Error: We couldn't parse the input provided as a DateTime value.. 12/31/2019 11:59:59 PM. ;We couldn't parse the input provided as a DateTime value.. The exception was raised by the IDbCommand interface.
[1] -1055784932: The command has been canceled.. The exception was raised by the IDbCommand interface.
[2] -1055129594: The current operation was cancelled because another operation in the transaction failed.
[3] -1055784932: The command has been canceled.. The exception was raised by the IDbCommand interface.
[4] -1055784932: The command has been canceled.. The exception was raised by the IDbCommand interface.
[5] -1055784932: The command has been canceled.. The exception was raised by the IDbCommand interface.
[6] -1055784932: The command has been canceled.. The exception was raised by the IDbCommand interface.

When I excute the auto refresh on the OnPremise Power BI Report server (latest version), I get the following error message :

No where I can find where this date comes from. Not in logs, not in the error message.

This problem does not occur when I publish the same report on the Power BI Service. When I refresh the data in Power BI Desktop there is allso no problem.

What can this be ? How do I get more information about this error message ? Trace files show nothing, log file allso show no more information than the message above.

Any help is welcome.

Re: Refresh error, only on Onpremise Power BI Report server. Not on Desktop and not on PowerBI servi

lbendlin — Wed, 08 Jan 2025 16:26:04 GMT

If you have a Pro license you can open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi
Otherwise you can raise an issue at https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues .

Re: Refresh error, only on Onpremise Power BI Report server. Not on Desktop and not on PowerBI servi

Vanchy_Liao — Thu, 09 Jan 2025 05:49:10 GMT

Hi @jacccodezwart ,

perhaps you can check the language settings for the PBIRS and Power BI Service.

Or you can change your data to string format and convert it into datetime format in Power Query.

Re: Refresh error, only on Onpremise Power BI Report server. Not on Desktop and not on PowerBI servi

jacccodezwart — Thu, 09 Jan 2025 08:34:35 GMT

@Vanchy_Liao thanks for your suggestion to change the datetime format in Power Query.

Not only I needed to change the datetime format for my variable, but allso of all the columns which I check using my variable.

That seemed to solve the refresh on the Power BI on-premise report server.

Still remains the question why is this not needed on the Power BI Service (app.powerbi.com) and not needed in Power BI Desktop.

Re: Refresh error, only on Onpremise Power BI Report server. Not on Desktop and not on PowerBI servi

Vanchy_Liao — Thu, 09 Jan 2025 08:39:32 GMT

@jacccodezwart ,

i guess the locale matters. you can check out the locale setting of PBIRS, Power BI Service and PBI Desktop.

Re: Refresh error, only on Onpremise Power BI Report server. Not on Desktop and not on PowerBI servi

chrisbrigg — Mon, 10 Feb 2025 15:11:28 GMT

I'm having the same issue here. Was there ever a solution identified?

Re: Refresh error, only on Onpremise Power BI Report server. Not on Desktop and not on PowerBI servi

jacccodezwart — Tue, 11 Feb 2025 07:01:27 GMT

Hey Chris,

The solution was to check types of both my variables and columns that were used in a formula. The variable was of date-time format and the column which I used is a formula was of time-stamp-with-timezone format. For some reason, the server (or workstation) regional settings resulted in the fact that it would work on my laptop, but not on the report server.

By explicitly making all the field types the same, the problem was solved.