Forum Discussion

djurecic's avatar
djurecic
Icon for Super User rankSuper User
5 years ago
Solved

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 (fi...
Need Help
  • Anonymous's avatar
    Anonymous
    5 years ago

    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 .

meade8079's avatar
meade8079
Frequent Visitor
5 years ago

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
  • BlobBlobHopHop's avatar
    BlobBlobHopHop
    Icon for Helper I rankHelper I
    5 years ago

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

  • meade8079's avatar
    meade8079
    Frequent Visitor
    5 years ago

    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.