Forum Discussion

Dearc's avatar
Dearc
Icon for Helper II rankHelper II
6 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
    6 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
    6 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. 🙂

Anonymous's avatar
Anonymous
Not applicable
5 years ago

Hello,

 

We had the same issue with a table "Enter Data". As other mentioned it refreshes fine in Desktop but when we refresh it on the Report Server we got:

"COM error: System.Core, Sequence contains no elements.

 

We removed the "Enter Data" and changed it with an Excel file, that changed the error to:

SessionID: 661334b7-6578-48a0-b28f-0861b7ef2873
[0] -1055784932: Information is needed in order to combine data;Information about a data source is required.. The exception was raised by the IDbCommand interface.
[1] -1055784932: The command has been canceled.. The exception was raised by the IDbCommand interface.
[2] -1055784934: 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.
[3] -1055784932: The command has been canceled.. The exception was raised by the IDbCommand interface.
[4] -1055784932: The command has been canceled.. The exception was raised by the IDbCommand interface.
[5] -1055784932: The command has been canceled.. The exception was raised by the IDbCommand interface.
[6] -1055784932: The command has been canceled.. The exception was raised by the IDbCommand interface.
[7] -1055784932: The command has been canceled.. The exception was raised by the IDbCommand interface.

 

Thanksfully we only have this issue with a single report but we're still hoping for a quick fix or a workaround. Downgrading to May 2020 is not really an option for this report since a lot of development was added using October 2020 before we realised the issue.