Forum Discussion
Scheduled Refresh error "There is no data in the database for @CatalogItemId"
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.
nop ,were not the backups
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.
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.
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.
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.