Forum Discussion
An unexpected error occurred (file '', line , function '')
- 1 year ago
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.
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_Santos1 year agoAdvocate I
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,B1845,3306791845,3306791845,3306791845,3306791845,3306791845,3306791845,3306791845,330679the 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.
- Anonymous1 year agoNot applicable
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_Santos1 year agoAdvocate I
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.