Forum Discussion

Dearc's avatar
Dearc
Icon for Helper II rankHelper 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=...
data refresh
Oct 2020
  • 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. πŸ™‚

Petebro's avatar
Petebro
Icon for Microsoft Employee rankMicrosoft Employee
5 years ago

Would it be possible to stop and restart the ReportServer and see if refresh is successful after? I am investigating the underlying issue, but this might unblock you in the meantime.

Dearc's avatar
Dearc
Icon for Helper II rankHelper II
5 years ago

Hello Petebro 

 

I tried 

- restart RS or computer ---- not work

- removed all 3rd-party visuals ---- not work 
- create new schedule refresh plan ---- not work
- removed local file data source ---- not work
- closed setting "Parallel load table" ---- not work



Here's the log

 

2020-11-04 09:38:45.2839|INFO|26|Handling event with data: TimeEntered: 11/4/2020 1:38:40 AM, Type: Event, SessionId: e6bbe324-d922-4463-9ed7-cb9db87ccaae, EventType: DataModelRefresh
2020-11-04 09:38:45.4401|INFO|26|Processing Data Model Refresh: SessionId: e6bbe324-d922-4463-9ed7-cb9db87ccaae, Status: Starting Data Refresh.
2020-11-04 09:38:45.4869|INFO|26|Processing Data Model Refresh: SessionId: e6bbe324-d922-4463-9ed7-cb9db87ccaae, Status: Starting Retrieving PBIX AsDatabaseInfo.
2020-11-04 09:38:45.6900|INFO|35|Finding model for refresh with catalogId=c700e2be-6d1b-46d3-a5aa-ed4f7511009c, lastCatalogItemUpdate =11/3/2020 8:11:15 PM, lastModelUpdateinCatalog=11/3/2020 8:11:21 PM, resolved to database name=c700e2be-6d1b-46d3-a5aa-ed4f7511009c_-1429373596, wasInMemory=True
2020-11-04 09:38:45.7681|TRACE|35|Processing Data Model Refresh: SessionId: e6bbe324-d922-4463-9ed7-cb9db87ccaae, Status: Finished Retrieving PBIX AsDatabaseInfo.
2020-11-04 09:38:45.7681|INFO|26|Processing Data Model Refresh: SessionId: e6bbe324-d922-4463-9ed7-cb9db87ccaae, Status: Starting Verifying all the data sources are embedded.
2020-11-04 09:38:45.8462|TRACE|26|Processing Data Model Refresh: SessionId: e6bbe324-d922-4463-9ed7-cb9db87ccaae, Status: Finished Verifying all the data sources are embedded.
2020-11-04 09:38:45.8462|INFO|26|Processing Data Model Refresh: SessionId: e6bbe324-d922-4463-9ed7-cb9db87ccaae, Status: Starting Verifying connection strings are valid.
2020-11-04 09:38:45.9087|TRACE|26|Processing Data Model Refresh: SessionId: e6bbe324-d922-4463-9ed7-cb9db87ccaae, Status: Finished Verifying connection strings are valid.
2020-11-04 09:38:45.9087|INFO|26|Processing Data Model Refresh: SessionId: e6bbe324-d922-4463-9ed7-cb9db87ccaae, Status: Starting Streaming model to Analysis Server.
2020-11-04 09:38:46.0337|TRACE|32|New clientSessionId generated: clientSessionId=e6bbe324-d922-4463-9ed7-cb9db87ccaae
2020-11-04 09:38:46.0493|INFO|32|LoadDatabaseAsync: Successfully EnsureDbLoaded clientSessionId=e6bbe324-d922-4463-9ed7-cb9db87ccaae, databaseName=c700e2be-6d1b-46d3-a5aa-ed4f7511009c_-1429373596, modelId=1714036118, alreadyLoaded=True
2020-11-04 09:38:46.6429|TRACE|26|Processing Data Model Refresh: SessionId: e6bbe324-d922-4463-9ed7-cb9db87ccaae, Status: Finished Streaming model to Analysis Server.
2020-11-04 09:38:46.6429|INFO|26|Processing Data Model Refresh: SessionId: e6bbe324-d922-4463-9ed7-cb9db87ccaae, Status: Starting Refreshing the model.
2020-11-04 09:38:47.0647|INFO|26|GetDataSourcesCollection: databaseName=c700e2be-6d1b-46d3-a5aa-ed4f7511009c_-1429373596, PowerBIDataSourceVersion=PowerBI_V3
2020-11-04 09:38:47.0803|TRACE|26|Datasource *********************** parsed
2020-11-04 09:38:47.0803|TRACE|26|Datasource *********************** parsed
2020-11-04 09:38:47.0803|TRACE|26|Datasource ***************************************************************.xlsx parsed
2020-11-04 09:38:47.0803|TRACE|26|Datasource ***************************************************************.xlsx parsed
2020-11-04 09:38:47.0803|INFO|26|Model Refresh: isRefreshActive=True, incoming databaseName=c700e2be-6d1b-46d3-a5aa-ed4f7511009c_-1429373596, databaseId=1714036118, activeModel.DatabaseName=c700e2be-6d1b-46d3-a5aa-ed4f7511009c_-1429373596
2020-11-04 09:38:55.7970|INFO|26|Model Refresh: isRefreshActive=False, incoming databaseName=c700e2be-6d1b-46d3-a5aa-ed4f7511009c_-1429373596, databaseId=1714036118, activeModel.DatabaseName=c700e2be-6d1b-46d3-a5aa-ed4f7511009c_-1429373596
2020-11-04 09:38:55.7970|ERROR|26|Error Processing Data Model Refresh: SessionId: e6bbe324-d922-4463-9ed7-cb9db87ccaae, 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 command has been canceled.. The exception was raised by the IDataReader interface. Please review the error message and provider documentation for further information and corrective action.
The command has been canceled.. The exception was raised by the IDbCommand interface.
The command has been canceled.. The exception was raised by the IDbCommand interface.
The current operation was cancelled because another operation in the transaction failed.
The command has been canceled.. The exception was raised by the IDbCommand interface.
The command has been canceled.. The exception was raised by the IDbCommand interface.
The command has been canceled.. The exception was raised by the IDbCommand interface.
The command has been canceled.. The exception was raised by the IDbCommand interface.
The command has been canceled.. The exception was raised by the IDbCommand interface.
The command has been canceled.. The exception was raised by the IDbCommand interface.
The command has been canceled.. The exception was raised by the IDbCommand interface.
The command has been canceled.. The exception was raised by the IDbCommand interface.
The command has been canceled.. The exception was raised by the IDbCommand interface.
'.
在 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-04 09:38:55.8751|TRACE|26|Processing Data Model Refresh: SessionId: e6bbe324-d922-4463-9ed7-cb9db87ccaae, Status: Finished Refreshing the model.

 SQL Server Profile log

 

exec AddExecutionLogEntryByReportId @InstanceName=N'*****',@ReportID='C700E2BE-6D1B-46D3-A5AA-ED4F7511009C',@UserName=N'NT AUTHORITY\NETWORK SERVICE',@AuthType=0,@RequestType=2,@Format=N'DataModel',@Parameters=NULL,@TimeStart='2020-11-04 09:38:46.6429542 +08:00',@TimeEnd='2020-11-04 09:38:55.7970299 +08:00',@TimeDataRetrieval=154,@TimeProcessing=0,@TimeRendering=0,@Source=1,@Status=N'rsInternalError',@ByteCount=0,@RowCount=0,@ExecutionId=N'e6bbe324-d922-4463-9ed7-cb9db87ccaae',@ReportAction=19,@AdditionalInfo=NULL
exec UpdateSubscriptionHistoryEntry @SubscriptionHistoryID=57655,@EndTime='2020-11-04 09:38:55.983',@Status=2,@Message=N'Several errors occured during data refresh. Please try again later or contact your 
administrator.',@Details=N'{"SessionID":"e6bbe324-d922-4463-9ed7-cb9db87ccaae","Errors":[{"ErrorCode":-1056505856,"Message":"COM error: System.Core, 
εΊεˆ—δΈεŒ…ε«δ»»δ½•ε…ƒη΄ .","CallStack":null},{"ErrorCode":-1055784934,"Message":"The command has been canceled.. The exception was raised by the IDataReader interface. Please review the error message and provider documentation for further information and corrective action.","CallStack":null},{"ErrorCode":-1055784932,"Message":"The command has been canceled.. The exception was raised by the IDbCommand interface.","CallStack":null},{"ErrorCode":-1055784932,"Message":"The command has been canceled.. The exception was raised by the IDbCommand interface.","CallStack":null},{"ErrorCode":-1055129594,"Message":"The current operation was cancelled because another operation in the transaction failed.","CallStack":null},{"ErrorCode":-1055784932,"Message":"The command has been canceled.. The exception was raised by the IDbCommand interface.","CallStack":null},{"ErrorCode":-1055784932,"Message":"The command has been canceled.. The exception was raised by the IDbCommand interface.","CallStack":null},{"ErrorCode":-1055784932,"Message":"The command has been canceled.. The exception was raised by the IDbCommand interface.","CallStack":null},{"ErrorCode":-1055784932,"Message":"The command has been canceled.. The exception was raised by the IDbCommand interface.","CallStack":null},{"ErrorCode":-1055784932,"Message":"The command has been canceled.. The exception was raised by the IDbCommand interface.","CallStack":null},{"ErrorCode":-1055784932,"Message":"The command has been canceled.. The exception was raised by the IDbCommand interface.","CallStack":null},{"ErrorCode":-1055784932,"Message":"The command has been canceled.. The exception was raised by the IDbCommand interface.","CallStack":null},{"ErrorCode":-1055784932,"Message":"The command has been canceled.. The exception was raised by the IDbCommand interface.","CallStack":null},{"ErrorCode":-1055784932,"Message":"The command has been canceled.. The exception was raised by the IDbCommand interface.","CallStack":null}]}'