Scheduled Refresh error "There is no data in the database for @CatalogItemId"

[Mike_Mellis]

Hi,

I've got a dozen reports scheduled to update every 30-60 minutes.  They all hit the same three data sources (DB2 database, AzureDevops WorkItem query using OData, and an on-prem SharePoint list using OData query).

Occasscially, usually once a day.. I get this error at different times, across all of the reports.  The next refresh, everything works correctly.  The catalogItemId changes each time.  Usually I just ignore it, since I know next time the report refreshes it will complete the refresh, however, I'd like to see if I can track it down so I can stop worrying about it.  It happens prior to October 2020 update (which I updated to on 11/6/2020).

I'm having trouble tracking down what the problem is.  Here is the log file entry from the last time it ran and erred. 

2020-11-09 09:30:17.9007|INFO|76|Processing Data Model Refresh: SessionId: 8b2c9c8c-557e-4b33-917c-6f62f530f092, Status: Starting Data Refresh.
2020-11-09 09:30:17.9943|INFO|76|Processing Data Model Refresh: SessionId: 8b2c9c8c-557e-4b33-917c-6f62f530f092, Status: Starting Retrieving PBIX AsDatabaseInfo.
2020-11-09 09:30:18.1194|INFO|63|Finding model for refresh with catalogId=a7e7ac7e-28f6-4d25-bdcd-b7dffa8bd188, lastCatalogItemUpdate =11/5/2020 1:33:50 PM, lastModelUpdateinCatalog=11/9/2020 9:00:51 AM, resolved to database name=a7e7ac7e-28f6-4d25-bdcd-b7dffa8bd188_-100668866, wasInMemory=True
2020-11-09 09:30:18.2287|INFO|76|Processing Data Model Refresh: SessionId: 8b2c9c8c-557e-4b33-917c-6f62f530f092, Status: Starting Verifying all the data sources are embedded.
2020-11-09 09:30:18.2444|INFO|76|Processing Data Model Refresh: SessionId: 8b2c9c8c-557e-4b33-917c-6f62f530f092, Status: Starting Verifying connection strings are valid.
2020-11-09 09:30:18.2444|INFO|76|Processing Data Model Refresh: SessionId: 8b2c9c8c-557e-4b33-917c-6f62f530f092, Status: Starting Streaming model to Analysis Server.
2020-11-09 09:30:18.3538|ERROR|76|Error Processing Data Model Refresh: SessionId: 8b2c9c8c-557e-4b33-917c-6f62f530f092, Status: Error Failed Streaming model to Analysis Server, Exception System.IO.IOException: There is no data in the database for @CatalogItemId=a7e7ac7e-28f6-4d25-bdcd-b7dffa8bd188;@ContentType=DataModel
   at Microsoft.ReportingServices.CatalogAccess.Streams.VarbinaryReadableStream.InitializeDatabaseAccess()
   at Microsoft.ReportingServices.CatalogAccess.Streams.VarbinaryReadableStreamFactory.CreateExtendedContentReadableStream(Guid catalogItemId, ExtendedContentType contentType)
   at Microsoft.ReportingServices.CatalogAccess.CatalogItemAccessor.GetExtendedContentReadable(Guid catalogItemId, ExtendedContentType contentType)
   at Microsoft.PowerBI.ReportServer.WebHost.EventHandler.AnalysisServicesDataRefresh.LoadModel(AsDatabaseInfo asDatabaseInfo)
   at Microsoft.PowerBI.ReportServer.WebHost.EventHandler.DataRefreshScope.<>c__DisplayClass34_0.<ExecuteActionWithLogging>b__0()
   at Microsoft.PowerBI.ReportServer.WebHost.EventHandler.DataRefreshScope.<ExecuteFuncWithLogging>d__33`1.MoveNext()
2020-11-09 09:30:18.5725|ERROR|76|Error Processing Data Model Refresh: SessionId: 8b2c9c8c-557e-4b33-917c-6f62f530f092, Status: Error Failed Data Refresh, Exception System.IO.IOException: There is no data in the database for @CatalogItemId=a7e7ac7e-28f6-4d25-bdcd-b7dffa8bd188;@ContentType=DataModel
   at 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)
   at Microsoft.PowerBI.ReportServer.WebHost.EventHandler.AnalysisServicesDataRefresh.RefreshData(RefreshInfo refreshInfo)
   at Microsoft.PowerBI.ReportServer.WebHost.EventHandler.DataRefreshScope.<>c__DisplayClass34_0.<ExecuteActionWithLogging>b__0()
   at Microsoft.PowerBI.ReportServer.WebHost.EventHandler.DataRefreshScope.<ExecuteFuncWithLogging>d__33`1.MoveNext()

[Anonymous]

Hi Mike,

same issue here, we have 16 Subscriptions which are beeing trigerred in the morning when the Mart finished processing.

Frequently 3 PBI Reports fail.

We have the October 2020 Version of PowerBI RS running.

I wonder if there maybe some limitations regarding the simoultaniosly cube processing in PBI RS which could lead to this kind of problem.

On the other hand, it i an IO Exception which points in the direction of the Data is not reachable.

Checking if it could be caused by Backups which make the source unavailable for beeing processed.

i will return when checked also that.

Regards

Roland

[Anonymous]

nop ,were not the backups

[Mike_Mellis]

The only thing I've been able to track down is the catalogitemid is the itemkey for each report.  It's located in the dbo.catalog table of the RS database.  Maybe it's losing connection or its a networking error and it doesn't know how to recover.  I was also thinking maybe it has to do with refreshing too many reports at once and there is some sort of collision.  I am going to try to offset my refreshes (i.e., set one for :05 after the hours, the next at :10, etc.).  Maybe by staggering them it gets a clean connect.

[Anonymous]

Hi Mike,

i'm pointing to a similar direction, assuming PowerBI can't handle to many simultaneously report refreshs.

so i setup a 2nd schedule which is beeing executed with a10min offset to the initial schedule.

currently trying to execute 12 instead of 16 Reports on schedule_1 and 4 in schedule_2 after the Rolap-Mart finished processing.

i will give an update about the status by tomorrow.

[Mike_Mellis · Accepted solution]

So far, no errors.. which is unusual.  I usually have a half dozen a day.  I offset the schedule for each report by 1 minute or so.  Some run at 1 min after the hour, some 1 minute prior.. or 2 minutes after, etc.  This is promising.  I'll update in a couple of days to see if any errors pop back up.

EDIT 11/23/2020 - No errors since I made the scheduling change.  Looks like off setting the schedules so they don't run at the same time worked to resolve the error.

[Anonymous]

Hi Mike,

sounds like you have found a work around.

I am still searching for a more handy / appropriate solution.

I have came across following Posts which also describe our issue except that in our case we are jus using SQL Server connections.

https://community.powerbi.com/t5/Report-Server/PBRS-Oct-2020-Release-update-causes-errors-in-Schedul...

https://community.powerbi.com/t5/Report-Server/Power-BI-Report-Server-October-2020-update-has-been-r...

[lbendlin]

Does that maybe coincide with the time when you write to your data source?

[Mike_Mellis]

I don't think so.  I got the same error on a report this morning that is only making a single query to a local DB2 database and I can confirm all records in that database are complete and there are no errors or null values.  I thought it had to do with the OData query to AzureDev Ops, but doesn't seem to be isolated to it.