Forum Discussion
We couldn't get your SQL endpoint's updated schema
An internal error happened due to failed runtime assertion: Unsupported AS datatype:Unknown.
Activity ID: 44c3cd31-ff28-4bd8-b01b-32a2de0d76e7
Request ID: 15f75346-c1fa-40ad-ae21-854a1fb3de0f
Correlation ID: 759f3971-f0ec-6be9-cdaa-176c245869e8
Status code: 500
Time: Tue Jul 11 2023 17:53:26 GMT+0530 (India Standard Time)
Service version: 13.0.21054.54
Client version: 2307.1.14623-train
Cluster URI: https://wabi-west-us-e-primary-redirect.analysis.windows.net/
13 Replies
I have been in contact with Microsoft Support about this issue. The issue persisted several days. Since Monday morning (about 4 days since the start of the error) the error is gone and the expected tables show up in the Table view en the contents can be viewed. The support team assured me that they did not make any changes in that period, so the issue solved itself in some mysterious way.
Nice to know: allthough the tables did not show up in the Tables sections of Fabric, they did show up when I used used SQL Management Studio to connect to the environment.
As far as I am concerned this topic can be closed.
Hi PraveenkumarE Thanks for posting your question in Microsoft Fabric Community
I have seen similar behavior but finally, the table has appeared in the warehouse after almost 1+ hour,
Can you please retry or check if you are still facing the same issue?
Regards
Geetha
Hi Anonymous ,
It seems that PraveenkumarE is not replying any more. So perhaps I can takeover this thread because I have exactly the same error:
We couldn't get your SQL endpoint's updated schema
An internal error happened due to failed runtime assertion: Unsupported AS datatype:Unknown.
Activity ID: f42e7ce6-e43e-40b5-a904-13b43574ed3b
Request ID: 9771a505-1e1e-45b0-bcce-00c94bf40c14
Correlation ID: de4dc88a-d1f3-e65d-4699-4b5b32692959
Status code: 500
Time: Wed Jul 26 2023 15:33:44 GMT+0200 (Midden-Europese zomertijd)
Service version: 13.0.21171.58
Client version: 2307.3.14960-train
Cluster URI: https://wabi-europe-north-b-redirect.analysis.windows.net/
After more than 24 hours waiting still the error occurs.
Context: I was working my way through the MS Fabric tutorials:
https://learn.microsoft.com/en-us/fabric/data-engineering/tutorial-lakehouse-build-report (step 2).
Do you have any suggestions?
Kind regards,
Theo
Same problem here when walking through the tutorial https://learn.microsoft.com/en-us/fabric/data-engineering/tutorial-lakehouse-build-report (step 2). Let's see if waiting helps.
update 1: 6 hours later: same error.
update 2: 1 day later: same error.
Hi Anonymous ,
the support request has just been created by me with id 2307270050000771.
Regards, Theo.
- rodrigosan
Responsive Resident
I am getting same problem.
Has anyone found the solution yet?At. Rodrigo Santos
Hi rodrigosan,
in my case the issue disappeared in a miraculous way after several days. The support staff was not able to tell me why.
Gr,
Theo
- rodrigosan
Here the error still persists, I'll follow up, if it miraculously disappears, I'll let you know here.
Thank you very much for your comment Theovb .
wweghorstAdvocate I
Same problem, the second line of the error message is a bit different, from "An internal error happened due to failed runtime assertion: Unsupported AS datatype:Unknown." tot "Internal error PBIServiceException.". But this still isn't much of a help.
Lakehouse -> SQL analytics endpoint -> Refresh
We couldn't get your SQL analytics endpoint's updated schema
Internal error PBIServiceException.- wweghorst
Yesterday we created a new lakehouse and everything worked fine. Today whe got the same error message in the lakehouse we created yesterday.
Even after removing all the tables we still got the error message "We couldn't get your SQL analytics endpoint's updated schema", "Internal error PBIServiceException."
How can we futher investigate this problem? How can i fix the PBI service error or what do i have todo to work around this error / problem?
- wweghorst
The old lakehouse still has the problem, even after 17 day's. We are in the process of moving everyting to the new lakehouse en hoping that one will keep working.
lyjavierHelper I
look like we are having the same problem like this today, in north europe region.
Has anyone experience this so far?
