Forum Discussion
Error message on refresh- An unexpected error occurred (file 'tmdatasourceregistry.cpp'
Has anyone seen this error before? It happens on datasource refresh. The datasource is TIBCO data virtualization, which uses an ODBC connection.
Processing error: An unexpected error occurred (file 'tmdatasourceregistry.cpp', line 847, function 'TMDataSourceRegistry::ApplyDeferredStaticAnalysis').
Cluster URI: WABI-US-NORTH-CENTRAL-B-redirect.analysis.windows.net
Activity ID: e1052a09-4ae1-42ef-a6a0-364cae1b1807
Request ID: cd235687-3c21-f61b-15ce-29469adede99
Time: 2021-06-22 19:25:36Z
EDIT: For us the issue has been resolved (6/29/2021).
hello ,
this is a known issue for which there is a Fix expediately rolling out across production instances of Power BI , with an ETA of 06/29 EOD for reaching saturation , there has been CSS (customer service support awarness shared to our support teams to better assist any Customers reaching out ) and also we are continuing to post proactively Tenant level (Customer level) communications for the impacted tenants we have been identifying , and basing on the IDs of error you shared , we see that Comms were posted to your Tenant admins already with regard to this issue. Please let us know .
70 Replies
Thanks for the update!
Thanks for letting us know!
Is There an issue ticket for this?
The product team is actively working on this issue but the ETA is not definitive. They are saying that upgrading to premium capacity will alleviate the issue.
I am having this same error. The only two datasets that are showing this error have Python scripts. The file updates just fine in my computer but it shows this error if I try to refresh in the portal. It is worth noting that these files had been refreshing just fine before. There was no changes to the files when this error started showing.
Affecting our production reports that use Python, as well. Probably on the magnitude of 35-45 reports in total. Nothing so far has worked, as it seems like it's an architecture issue in Service. Same error message:
"An unexpected error occurred (file 'tmdatasourceregistry.cpp', line 847, function 'TMDataSourceRegistry::ApplyDeferredStaticAnalysis')."
What we've tried:
--Upgrading the personal gateway to version 3000.86.4 (2021-06-18)
--Uninstalling, restarting, and clean installation of personal gateway to version 3000.86.4 (2021-06-18)
--Repairing the current Power BI Desktop installation Version: 2.93.981.0 64-bit (May 2021)
--Uninstalling, restarting, and clean installation of Power BI Desktop Version: 2.93.981.0 64-bit (May 2021)
--Switching to a different personal gateway on another box version 3000.77.7 (2021-03-23)
--Using a personal workspace
*Edit*
--Pulling down each report, refreshing the Power Query preview for each table, doing a full desktop refresh, and re-publishing to service
--Pulling down each report, changing the Python query slightly, refreshing the Power Query preview for each table, doing a full desktop refresh, and re-publishing to service
*End Edit*
We've also tried a number of combinations of the above. This seems to be a universal issue, so I'm forwarding this to our Microsoft rep for escalation.
Great summary of what you've tried! Saves us some time trying to do the same!
But who did you contact? I also would like to share my error messages and would also like to be kept in the loop.
This is the message I am getting:
Last refresh failed: Mon Jun 28 2021 08:55:07 GMT+0200 (Central European Summer Time)
There was an error when processing the data in the dataset.Hide detailsProcessing error: An unexpected error occurred (file 'tmdatasourceregistry.cpp', line 847, function 'TMDataSourceRegistry::ApplyDeferredStaticAnalysis'). Cluster URI: WABI-WEST-EUROPE-D-PRIMARY-redirect.analysis.windows.net Activity ID: 089277b8-68c6-43d2-af4e-903b5b434d1c Request ID: 7cf8de67-cee0-29ec-14b9-a210beb18414 Time: 2021-06-28 06:55:07Z
Same issue - happens only in models that contain Python scripts. Problem disappears when I republish, but comes back in several hours.
Have got the same issue. Using Python Scripts in PowerBI. Hope they fix it soon. I have many reports that could be affected.
I have the same error here since yesterday. All reports with python scripts cannot be refreshed on the portal page. Operational activities have been disrupted. Hopefully Microsoft will fix it soon.
hello ,
this is a known issue for which there is a Fix expediately rolling out across production instances of Power BI , with an ETA of 06/29 EOD for reaching saturation , there has been CSS (customer service support awarness shared to our support teams to better assist any Customers reaching out ) and also we are continuing to post proactively Tenant level (Customer level) communications for the impacted tenants we have been identifying , and basing on the IDs of error you shared , we see that Comms were posted to your Tenant admins already with regard to this issue. Please let us know .
Thank you for the update.
I'm hoping the error I'm now getting, replacing the tmdatasourceregistry.cpp error I was getting last week, on the same python script, is just an interim error while the fix propagates across all instances. Any guidance otherwise would be appreciated! I've tried deleting & re-publishing to the service and re-editing the credentials.
Needless to say the script works without error in Desktop and worked fine in the service before this issue arose. Thanks, Henry.
Last refresh failed: Mon Jun 28 2021 16:04:12 GMT-0400 (Eastern Daylight Time)
Unable to connect to the data source undefined.Hide details
Underlying error code: -2147467259
Underlying error message: ADO.NET: Python script error. NameError: name 'RunReportResp' is not defined
DM_ErrorDetailNameCode_UnderlyingHResult: -2147467259
Microsoft.Data.Mashup.ValueError.DataSourceKind: Python
Microsoft.Data.Mashup.ValueError.DataSourcePath: Python
Microsoft.Data.Mashup.ValueError.ErrorCode: -2147467259
Microsoft.Data.Mashup.ValueError.ExceptionType: Microsoft.PowerBI.Scripting.Python.Exceptions.PythonScriptRuntimeException
Microsoft.Data.Mashup.ValueError.Message: Python script error. NameError: name 'RunReportResp' is not defined
Microsoft.Data.Mashup.ValueError.Reason: DataSource.Error
Cluster URI: WABI-US-NORTH-CENTRAL-B-redirect.analysis.windows.net
Activity ID: 12bef926-2acf-44c2-a5ee-ce29a39240cf
Request ID: bd66adf7-a5fb-f955-2c69-ebf206647d69
Time: 2021-06-28 20:04:12Z
Had the same error. refreshing the PBIX file in powerBI desktop and then reuploading the file worked for me.. dashboards are refreshing in PowerBI service again.
*EDIT*
Did not work for long. Issues came back 2 days later.
* END OF EDIT*
Had the same error, and republishing the PBIX from desktop worked for me too.
Thanks for sharing.
perfect! republishing the PBIX from desktop worked for me - also without the need to upgrade to premium.
Didn't work for long. Next day everything failed again.
we are experiencing the same issue here as well - no python scripts or smart narrative in these reports
- Processing errorAn unexpected error occurred (file 'tmdatasourceregistry.cpp', line 847, function 'TMDataSourceRegistry::ApplyDeferredStaticAnalysis').
Same here, been refreshing fine for months and suddenly yesterday morning PBI Online refresh fails with the error. Also using a data gateway with an ODBC connection. Updated the data gateway, didn't resolve.
Processing error: An unexpected error occurred (file 'tmdatasourceregistry.cpp', line 847, function 'TMDataSourceRegistry::ApplyDeferredStaticAnalysis'). Cluster URI: WABI-US-NORTH-CENTRAL-redirect.analysis.windows.net Activity ID: 1ae32c94-8856-41f6-966c-9f451fa3a1ea Request ID: a19fb143-fe5c-83d9-0237-fb6f9e9908cf Time: 2021-06-23 14:26:32Z We are having the same issue. About 50 environments cannot be updated until there is a fix.
From Microsoft Support:
I hope you are doing well.
It is currently a known issue. Our Product team has identified a bug for this issue.
We have received the ETA for this bug fix and it will be deployed between today and the end of next week.
Upon deployment, you will receive an update from us, and you can verify whether your issue will be resolved.
If not, then we can continue working on this case.
It might be worth removing the Smart Narrative visuals and publish back to your workspace. We are in the process of trying that.
We are having the same issue with our reports not refreshing in the service either. We aren't using any Python scripts in our reports, but the reports do have data from multiple different sources and connectors contained within.
really hoping they get this fixed ASAP...
