Forum Discussion

Dearc's avatar
Dearc
Helper II
5 years ago
Solved

PBRS Oct 2020 encounter errors in scheduled refresh

Hello, 

After updated to latest PBRS,  some report show errors after data refresh (MSSQL server)

 

2020-11-03 14:38:44.6959|INFO|49|Model Refresh: isRefreshActive=False, incoming databaseName=2f73dc1d-1d10-4623-ba13-c5d32a1140ba_-518857867, databaseId=1874950878, activeModel.DatabaseName=2f73dc1d-1d10-4623-ba13-c5d32a1140ba_-518857867
2020-11-03 14:38:44.6959|ERROR|49|Error Processing Data Model Refresh: SessionId: 728ccb82-3e25-4259-9f9f-89c9ce10ec7c, Status: Error Failed to refresh the model, Exception Microsoft.AnalysisServices.OperationException: Failed to save modifications to the server. Error returned: 'COM error: System.Core, 序列不包含任何元素.
The current operation was cancelled because another operation in the transaction failed.
'.
在 Microsoft.AnalysisServices.Tabular.Model.SaveChangesImpl(SaveOptions options)
在 Microsoft.PowerBI.ReportServer.AsServer.TOMWrapper.RefreshModel(Database database)
在 Microsoft.PowerBI.ReportServer.AsServer.AnalysisServicesServer.RefreshDatabase(String databaseName, IEnumerable`1 dataSources, IEnumerable`1 parameters, String clientSessionId)
在 Microsoft.PowerBI.ReportServer.WebHost.EventHandler.AnalysisServicesDataRefresh.RefreshDatabase(AsDatabaseInfo asDatabaseInfo)
在 Microsoft.PowerBI.ReportServer.WebHost.EventHandler.DataRefreshScope.<>c__DisplayClass34_0.<ExecuteActionWithLogging>b__0()
在 Microsoft.PowerBI.ReportServer.WebHost.EventHandler.DataRefreshScope.<ExecuteFuncWithLogging>d__33`1.MoveNext()
2020-11-03 14:38:44.8086|ERROR|49|Error Processing Data Model Refresh: SessionId: 728ccb82-3e25-4259-9f9f-89c9ce10ec7c, Status: Error Failed Data Refresh, Exception Microsoft.AnalysisServices.OperationException: Failed to save modifications to the server. Error returned: 'COM error: System.Core, 序列不包含任何元素.
The current operation was cancelled because another operation in the transaction failed.
'.
在 Microsoft.PowerBI.ReportServer.WebHost.EventHandler.DataRefreshScope.ExecuteActionWithLogging(Action methodToExecute, String description, String localizedDescription, String messageInFailure, RefreshInfo refreshInfo, DataAccessors dataAccessors, ReportEventType operation, Boolean isDataRetrieval, Boolean showInExecutionLog, Boolean sendToTelemetry)
在 Microsoft.PowerBI.ReportServer.WebHost.EventHandler.AnalysisServicesDataRefresh.RefreshData(RefreshInfo refreshInfo)
在 Microsoft.PowerBI.ReportServer.WebHost.EventHandler.DataRefreshScope.<>c__DisplayClass34_0.<ExecuteActionWithLogging>b__0()
在 Microsoft.PowerBI.ReportServer.WebHost.EventHandler.DataRefreshScope.<ExecuteFuncWithLogging>d__33`1.MoveNext()

 

Which refreshed OK on desktop version. Any possible solutions to help me find why? 

 

Thanks

 

 

  • Dearc's avatar
    Dearc
    5 years ago

    Hello @Petebro ,

    I think i found the problem. In my hybrid models, I have 3 datasource

    1. Xlsx files

    2. SQL server

    3. Some table create by entered data

     

    I replace the entered data table with xlsx files, the refresh problem solved

  • Anonymous's avatar
    Anonymous
    5 years ago

    Issue confirmed here as well.

     

    Recreated by:

    1. Added data source sql server table for import. Tested schedule in PBIRS -> successful refresh

    2. Added small table by "Enter Data" (unrelated to table 1 from sql server). Tested schedule in PBIRS -> error

    3. Tried a combo of SQL Server import source and excel file -> Works fine.

     

    Issue seem to be related to tables generated from "Enter data". Refreshing in PBIRS encounters error, both in manual triggering of schedule and "on-clock" schduled runs. Error message returned is:

     

     

    SessionID: 864f8ded-276d-4fb2-a5f5-8af41c243372
    [0] -1056505856: COM error: System.Core, Sequence contains no elements.
    [1] -1055784828: The database operation was cancelled because of an earlier failure.

     

     

    This is a very critical issue that is quite hard to find. No upgrader for us unitl this is fixed... 😞

    Crossing our fingers for a buggfix in a relase coming soon. 🙂

19 Replies