Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
1 year ago
Solved

Loadfailure in services

 

Hi all

 

We got a loadfailure for a semantic model in the Service. Error mes below.

Load works in dev and test. datasources in test and prd are identical but load fails in prd.

It´s just one view that fails load.

Normal load time is +-5min

additional problem is that we only have .bim file for the semantic model 😭. Changes are done using tabular editor 2
I´ve recreated .pbix in desktop with using same views. Load for same table also fails when refreshing data vs prd in Desktop but if I change Command timeout to 60 min load dosen´t fail.

so I have 2 questions:

1, Does anyone understand whats going wrong.

2, Is there a way to change the Command timeout on .bim file?

 

Error

 
Data source error: DataSource.Error: Microsoft SQL: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. 111202;Query QID34371 has been cancelled. Operation cancelled by user.. Microsoft.Data.Mashup.ErrorCode = 10478. DataSourceKind = SQL. DataSourcePath = xxxxxxxxxxxxxxx.azuresynapse.net;syndp_machineryanalytics. Message = Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. 111202;Query QID34371 has been cancelled. Operation cancelled by user.. ErrorCode = -2146232060. Number = -2. Class = 11. State = 0. ConnectionId = xxxxxxxxxxxxxxxxxxxxx. . The exception was raised by the IDbCommand interface. Table: xxxx xxxx
  •  

    Anonymous, Thanks for reaching MS fabric community support.

     

    • If the query is slow this could be due to more data in prod or you need to optimize the view, Different indexing or execution plans
    • check Resource contention (other workloads affecting performance), If the view times out, this could be the root cause.
    • Can you try below and let me if this works for you?
      Open Tabular Editor 2 and load the .BIM file, Expand Data Sources → Click on the data source used in the failing query. In the Properties pane, locate Command Timeout and Increase the value to optimal value. Save and deploy the model and Try refreshing the semantic model in PRD again.

     

     

     

     

    Thanks,

    Prashanth Are

    MS fabric community support

     

     

     

1 Reply

  • v-prasare's avatar
    v-prasare
    Community Support

     

    Anonymous, Thanks for reaching MS fabric community support.

     

    • If the query is slow this could be due to more data in prod or you need to optimize the view, Different indexing or execution plans
    • check Resource contention (other workloads affecting performance), If the view times out, this could be the root cause.
    • Can you try below and let me if this works for you?
      Open Tabular Editor 2 and load the .BIM file, Expand Data Sources → Click on the data source used in the failing query. In the Properties pane, locate Command Timeout and Increase the value to optimal value. Save and deploy the model and Try refreshing the semantic model in PRD again.

     

     

     

     

    Thanks,

    Prashanth Are

    MS fabric community support