An unexpected error occurred (file '', line , function '')

[Nuno_Santos]

After updating to the May 2025 Report Server, the error 'An unexpected error occurred (file '', line , function '')' is occurring in reports that had been deployed for a long time.

It appears that the issue might be related to date Slicers. Ig o delete the date slicer visual and redeploy, the error is gone.

[haputhanthree]

I encountered the same issue, but installing Insider Preview 27881.1000 resolved it for me.
Power BI Version: 2.144.1155.0 64-bit (June 2025)

[v-pagayam-msft]

Hi @Nuno_Santos ,
We are following up once again regarding your query. Could you please confirm if the issue has been resolved through the support ticket with Microsoft?
If the issue has been resolved, we kindly request you to share the resolution or key insights here to help others in the community. 

Thank you for your understanding and participation.

[Nuno_Santos]

Hi, still working on it.

I have run some tests and minimized the data to reproduce the error with a CSV file, created in a plain text file.

The text file contains only these lines:

A,B

1845,330679

1845,330679

1845,330679

1845,330679

1845,330679

1845,330679

1845,330679

1845,330679

the 3 steps applied to file load:

= Csv.Document(File.Contents("D:\work\TestFile.csv"),[Delimiter=",", Columns=2, Encoding=65001, QuoteStyle=QuoteStyle.None])

= Table.PromoteHeaders(Source, [PromoteAllScalars=true])

= Table.TransformColumnTypes(#"Promoted Headers",{{"A", type number}, {"B", Int64.Type}})

column A was set as a decimal and column B as a whole number.

I created the measure:

measure= CALCULATE(COUNT(TestFile[B]),TestFile[A]>0)

and a visual list with only one column containing the created measure and the error occurs.

the error disappears if I do one of the following:

• remove at least one line of the file (all lines are equal)
• change column A type from decimal to whole number
• change measure removing TestFile[A]>0, or changing to TestFile[A]=0 or TestFile[A]<0, but TestFile[A]>=0 the error remains (the '>'  operator is causing the error)

Thanks.

[v-pagayam-msft]

Hi @Nuno_Santos ,
Thank you for keeping us updated on the issue and confirming that it’s still unresolved. Once you hear back from the support team, please do share the response here, it will be helpful for others who may encounter a similar issue.
Thank you.

[Nuno_Santos · Accepted solution]

Hi,

After installing on several devices and noticing that some returned errors while others didn’t, I compared the system information of each one and found that the issue, in this case, is related to AVX CPU extension support. One of the VMs didn’t inherit this extension from the host, and once it was enabled, the error disappeared.

We can conclude that the error is related to CPUs lacking the AVX extension.
Best Regards.

[gpoelmans]

We have had the same issue. Enabling the AVX CPU extension support resolved it. 
Thanks Nuno_Santos for finding and reporting this. 

[SWADOOD]

this was the issue at our end the VM Machine , cpu was selected as core 2 duo...
which does not support avx extension....
when updated to when updated to xeon gold 6226R..
the visual started to showing again..

[v-pagayam-msft]

Hi @Nuno_Santos ,
Thank you for the update — glad to hear the issue has been resolved!
Please consider accepting your answer as the solution so others facing a similar issue can easily find it.

Regards,
Pallavi.

[LiadAlkobi]

@Nuno_Santos answer is not the resolution , it might be spotting what is the problem.
What am I supposed to do if I'm using Mac and my CPU doesn't support AVX ?
@v-pagayam-msft 

[v-pagayam-msft]

Hi @LiadAlkobi ,
Thanks for sharing your experience. As mentioned earlier, I had suggested raising a support ticket for this issue.

@Nuno_Santos ,could you please update us on the response you received from the Microsoft Support team? That insight might help others facing similar issues, especially since some users are still encountering the error despite enabling AVX.

Appreciate your help in keeping the community informed!
Thank you.

[wangpipi]

我们遇到了相同的问题，正在等待微软的回复

[v-pagayam-msft]

Hi @Nuno_Santos ,
Could you please confirm if the issue has been resolved after raising a support case? If a solution has been found, it would be greatly appreciated if you could share your insights with the community. This would be helpful for other members who may encounter similar issues.
Thank you for your understanding and assistance.

[Nuno_Santos]

Hi,

I raised a support case and i'm waiting for a solution.

I restored the database from the server that has the error onto the server that is working fine, and it worked well. So I assume the issue is not with the database. At this point, I haven’t made any progress and I’m waiting for updates from support or a patch from the May 2025 version of Power BI Report Server.

Thank you.

[jimmylin829]

@Nuno_Santos did you get a resolution from Microsoft on this?  Thank you!

[Nuno_Santos]

Not yet.

[v-pagayam-msft]

Hi @Nuno_Santos ,
We appreciate your patience and thank you for the update on the issue. A dedicated support team will be assigned to handle the scenarios efficiently. Please wait until the issue is resolved. Once resolved, kindly share the insights and mark them as "Accept as Solution" to assist others with similar issues.

Thank you.

[v-pagayam-msft]

Hi @Nuno_Santos ,

Please go through the mentioned steps and check step by step again ,if still faces the same issue then please consider raising a support ticket for further assistance.

To raise a support ticket for Fabric and Power BI, kindly follow the steps outlined in the following guide:

How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

If this post helps, please give us Kudos and consider marking it Accept as solution to assist other members in finding it more easily.
Thank you for being a part of Microsoft Fabric Community Forum!

Regards,
Pallavi G.

[Nuno_Santos]

each time error occurs one event is raised:
The description for Event ID 22 from source MSOLAP$PBIRS cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

[Nuno_Santos]

Hi,

All servers have the latest updates and patches. All Sql Serves are in 16.0.4195.2 (2025 may).
Log is in verbose mode but give no more details:
- 2025-06-09 14:14:43.8255|ERROR|114|An error occurred running the query.Details: ErrorCode=QuerySystemError, ProviderErrorCode=0xC1000000, ErrorSource=PowerBI, Message=Failed to execute the DAX query., HResult=0x80004005, Language=en-US, ProviderErrorMessage=[<ccon>An unexpected error occurred (file '', line , function '').</ccon>], ProviderGenericMessage=[Internal error: An unexpected error occurred (file '', line , function '').], ErrorSourceOrigin=MsolapWrapper, AS, OnPremErrorCode=, InnerErrorDetails=[Type=MsolapWrapper.MsolapWrapperException, Message=Failure encountered while executing the DAX query.]| RequestID = 7d5a340b-9999-3d1e-9999-3zzxxvvbbnn1 ClientSessionID = 7d5a340b-9999-3d1e-9999-3zzxxvvbbnn1
- 2025-06-09 14:14:43.8305|INFO|114|Writing error DSR| RequestID = 7d5a340b-9999-3d1e-9999-3zzxxvvbbnn1 ClientSessionID = 7d5a340b-9999-3d1e-9999-3zzxxvvbbnn1
I compared the configuration between the standalone and Always On solutions but didn’t find anything also.

[Nuno_Santos]

Hi,
thank you for your comments, but even after removing and rebuilding the slicer, the error persists. I’ve rebuilt the report from scratch using the latest available version of Power BI Desktop Report Server (2.143.954.0 64-bit ( 2025 may)), and the error still occurs.
What’s also strange in this situation is that I have a standalone server with SQL Server 2022 and the May version of Power BI RS where the error does not occur. But in a two-server Always On setup with SQL Server 2022 and the May version of Power BI RS, the error does occur...