Warehouse Fabric GUI does not update

[Alexander_Faber]

Hi together, I am facing the problem that my fabric warehouse does not update the schemas and tables right. 

It throws following error: 

Leider ist ein Problem aufgetreten.

Fehler bei der SQL-Abfrage während der Ausführung. Message=[METADATA DB] <ccon>Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.</ccon>, Code=-2, State=0

When I open the warehouse for example in Azure Data Studio everything is fine. 

Does anyone have an idea how to solve it?

Kind regards, 

Alex

[smue_smue]

@Alexander_Faberand @trutz 
It's officially an known issue now: https://learn.microsoft.com/en-us/fabric/known-issues/known-issue-1039-sync-warehouse-sql-endpoint-f...

[trutz]

Hi Alex,
Thank you for the link.
The support engineer told us that a way to mitigate the issue was restarting (Pause/Resume) the Fabric capacity. We had a Premium capacity, in which case the support was able to do the restart for us.

[smue_smue]

I can't offer any help, just wanted to share that we are experiencing the same thing since yesterday afternoon.

[Alexander_Faber]

I have opened a ticket for that and support is still investigating the issue. 

[v-tsaipranay]

Hello @Alexander_Faber ,

We understand that you're facing an issue with SQL query execution in Microsoft Fabric Warehouse and thank you for your patience and understanding. This issue is currently a known ongoing issue affecting Warehouse SQL endpoint synchronization in the West Europe region as @smue_smue mentioned. Microsoft is aware of the problem, and the team is actively working on a resolution.

For more information and updates on this issue, please refer to the official Microsoft Fabric Known Issues page:

Known issue - Sync for data warehouse and SQL analytics endpoint fail in West Europe - Microsoft Fab...

If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.

Thank you. 

[trutz]

Using parts of this code I can find also batch jobs of type Monitor on the SQL endpoint
Workaround for delays in the automatically generated schema in the SQL analytics endpoint of the Lak...
These batch jobs also list the new tables. But there are other jobs with a refresh action from the UI that turns up with an error:

  {'batchId': 'aaaaaaa-adb1-4a34-8786-aaaaaaaaaaaaaa-03be-4582-b90b-e90fbb204dec$2025-02-27T16:19:35.5346803Z@f725a144-300c-4e90-bbd1-b31674256bee',
   'startTimeStamp': '2025-02-27T16:19:35.72',
   'endTimeStamp': '2025-02-27T16:32:55.66',
   'progressState': 'failure',
   'errorData': {'error': {'code': 'InternalError',
     'pbi.error': {'code': 'InternalError',
      'parameters': {'ErrorMessage': 'The SQL query failed while running. Message=[METADATA DB] <ccon>Execution Timeout Expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.</ccon>, Code=-2, State=0',
       'HttpStatusCode': '500'},
      'details': []}}},
   'batchType': 'metadataRefresh'}

[trutz]

We're getting the same issue. 
If you run the the following SQL command, new tables show up, but not in the UI, which gives us the same error, you've been showing:

SELECT *

FROM INFORMATION_SCHEMA.TABLES

where table_schema = 'dbo' and TABLE_NAME

[v-tsaipranay]

Hello @Alexander_Faber ,

Thank you for reaching out to the Microsoft Fabric community forum. The error you're seeing indicates a timeout issue in the Fabric UI, while Azure Data Studio is functioning correctly. Also thank you @nilendraFabric  for your inputs

To fix this, try manually refreshing the schema by going to Warehouse > Manage Tables > Refresh Schema. If your queries are large, they might be timing out before completion, so consider breaking them into smaller parts for better performance.

If you're using Power BI, increase the Command Timeout in File > Options & Settings > Options > Query Execution. Additionally, try pausing and resuming the warehouse from the Fabric UI or reconnecting the SQL Endpoint via Settings > Manage Connections > Reconnect SQL Endpoint.

Check your Fabric capacity and resource limits, as heavy workloads can cause timeouts. If the issue persists, verify the Fabric Service Health Dashboard for any outages.

I hope my suggestions give you good ideas, if you need any further assistance, feel free to reach out.

If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.

Thank you. 

[nilendraFabric]

Hello @Alexander_Faber 

Fabric Warehouse operations often fail due to transient connectivity or backend delays.

from MS Doc

"

Transient connection errors

A transient error, also known as a transient fault, has an underlying cause that soon resolves itself. If a connection to Warehouse used to work fine but starts to fail without changes in user permission, firewall policy, and network configuration, try these steps before contacting support:

1. Check the status of Warehouse and ensure it's not paused.
2. Don't immediately retry the failed command. Instead, wait for 5 to 10 minutes, establish a new connection, then retry the command. Occasionally Azure system quickly shifts hardware resources to better load-balance various workloads. Most of these reconfiguration events finish in less than 60 seconds. During this reconfiguration time span, you might have issues with connecting to your databases. Connection could also fail when the service is being automatically restarted to resolve certain issues.
3. Connect using a different application and/or from another machine."

https://learn.microsoft.com/en-us/fabric/data-warehouse/troubleshoot-fabric-data-warehouse

if issue persists worth raising a support ticket. 

if this is helpful please accept the answer 

[trutz]

For me the error appears in a lakehouse not a warehouse. The issue persists since 2 days.