Error message on refresh- An unexpected error occurred (file 'tmdatasourceregistry.cpp'

[djurecicK2]

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). 

[gunjan8421]

Same error allthe dashboards are failing.

hope team resolve this soon

[gunjan8421]

I am having two files coming from the Python script rest all are JSON from the system 
Visualizations are also quite a basic ones nothing complex

Have tried restarting the personal gateway still issue is not resolved.

[lathan]

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').

[rk_aga]

We're experiencing the same problem here, not using any python scripts on our end.

I've tried republishing into a different workspace and seems to solve this issue in the meantime, however really hope if they could solve this issue soon.

[ECR]

Same problem here. Power BI reports containing python scripts are throwing this error and not refershing. I hope they get it fixed soon as this will affect our business.

[Anonymous]

Same here for the Python scripts on the power BI. Is there any acknowledgement from Microsoft? or how do we push the issue?

[MPRGray]

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...

[Anonymous]

We are experiencing the same issue. Report doesn't use Python script but uses Smart Narrative. This started once the Smart Narrative issue was fixed.

[kadams8844]

It might be worth removing the Smart Narrative visuals and publish back to your workspace.  We are in the process of trying that.

[Anonymous]

It is now failing for all our reports - even the ones without Smart Narratives 😕

[Anonymous]

Update (6/23/2021):

Microsoft is currently working on a solution and it should be in place in 2 days (Friday 6/25/2021). I'll keep in contact with them and let you know if that date is moved up or out.

[Anonymous]

Update (6/24/2021):

From Microsoft:

"received an update and it looks like you will see it on Monday 6/28. So you should be able to see this by the end of the day at 3pm PDT or earlier."

[kadams8844]

Thanks for the update!

[aspesot]

Is There an issue ticket for this?

[kadams8844]

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.

[MinimalEffect]

Haha-The analogy of: When a car breaks due to a manufacturing issue. Just buy a new one.

[djurecicK2]

Thanks for letting us know!

[meade8079]

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

[meade8079]

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.

[BlobBlobHopHop]

We are having the same issue. About 50 environments cannot be updated until there is a fix.

[lirik]

Same issue - happens only in models that contain Python scripts. Problem disappears when I republish, but comes back in several hours.