Forum Discussion
scheduled morning refresh failed
HI, can anyone help me understand this error message:
Something went wrong
There was an error when processing the data in the dataset.
- Processing errorThe start date in Calendar function can not be later than the end date.
- Cluster URIWABI-NORTH-EUROPE-J-PRIMARY-redirect.analysis.windows.net
- Activity ID49265113-749c-4521-83fb-6d4eed654bea
- Request ID714b504b-cf76-47c2-9649-d07aea591f8f
- Time2023-01-05 10:14:57ZCopy==============================================in all my tables, there is only one table where we manually enter in dates, and it's surprising that after 10,000 rows, this is the first time we hit this problem. I had a quick look and I can't see any issues to do with end dates being before start datesany help is appreciated
Hi , Anonymous
According to my query in the background database with the error details you provided, you can see the following error details:
Microsoft.AnalysisServices.Azure.Common.ProcessDatabaseFailedException: Processing for 76c43c7d-9314-4f0e-8b75-933e77409c3d failed due to Failure in processing XMLA command by the server, fault: '<soap:Fault xmlns="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<faultcode>XMLAnalysisError_Generated</faultcode>
<faultstring>Generated FaultString for Batch commands with multiple errors</faultstring>
<detail>
It seems that your dataset refresh failure is caused by an error when running some XMLA command by the server, so you can reveal which data sources your dataset is connected to? Is there a PBI dataset included as a data source?
Another point is that I see a warning in your desktop screenshot that there is a query that is not loaded into the PBI, which is a potential cause of your error, if it is convenient, you also need to go to Power Query to see if the enabled query can be refreshed and previewed successfully, and the desktop refresh can also be successful, after ensuring the following things, publish the dataset to the service to reconfigure the credentials and try to refresh.
Thank you for your time and sharing, and thank you for your support and understanding of PowerBI!
Best Regards,
Aniya Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly
Anonymous
3 Replies
- AnonymousNot applicable
the dates in my calendar function are fine and do not match the refresh error message, yet the whole thing fails to load (manual load & auto load)
- v-yueyunzh-msft
Community Support
Hi , Anonymous
According to my query in the background database with the error details you provided, you can see the following error details:
Microsoft.AnalysisServices.Azure.Common.ProcessDatabaseFailedException: Processing for 76c43c7d-9314-4f0e-8b75-933e77409c3d failed due to Failure in processing XMLA command by the server, fault: '<soap:Fault xmlns="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<faultcode>XMLAnalysisError_Generated</faultcode>
<faultstring>Generated FaultString for Batch commands with multiple errors</faultstring>
<detail>
It seems that your dataset refresh failure is caused by an error when running some XMLA command by the server, so you can reveal which data sources your dataset is connected to? Is there a PBI dataset included as a data source?
Another point is that I see a warning in your desktop screenshot that there is a query that is not loaded into the PBI, which is a potential cause of your error, if it is convenient, you also need to go to Power Query to see if the enabled query can be refreshed and previewed successfully, and the desktop refresh can also be successful, after ensuring the following things, publish the dataset to the service to reconfigure the credentials and try to refresh.
Thank you for your time and sharing, and thank you for your support and understanding of PowerBI!
Best Regards,
Aniya Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly
Anonymous
- AnonymousNot applicable
thank-you. The error, it turns out, was a missing date (a blank cell) in our Sharepoint Excel spreadsheet.
This spreadsheet is one of the tables in our model.