Forum Discussion

TaylorN's avatar
TaylorN
Helper I
6 years ago
Solved

Paginated Reports not loading

I have a few paginated reports deployed to a premium workspace and have had no issues up until now.

 

This morning, I was supposed to receive a subscription, but did not, so I went to investigate and found that I cannot load any of the paginated reports. They all just show the loading screen with the message Loading report...

  • So it turns out it’s an issue connecting to the source DB. I’m running a serverless Azure SQL DB with auto pause enabled and it appears that the connection attempt isn’t waking up the server like it should.

    So Microsoft’s suggestion is to have another report run just before it, which will fail, then the next one should succeed 😕

    I don’t like this option, so I’m just going to change the time the report executes to a little bit later, as there is a data factory pipeline that runs and it starts the instance.

12 Replies

  • Hi there

    I would suggest looking at the Premium metrics app and see what is consuming all the memory which could be the cause of the issue?
    • TaylorN's avatar
      TaylorN
      Helper I

      Thanks GilbertQ. I am not a capacity admin, so I will have to get someone else to check. I am hoping it's just a simple memory allocation issue 🙂

      • GilbertQ's avatar
        GilbertQ
        Super User
        Yeah that would be my initial assumption, hopefully it is something that can be quickly resolved!
    • TaylorN's avatar
      TaylorN
      Helper I
      If it was disabled, all paginated reports would fail to run permanently, these are just intermittently not working.

      I checked the memory allocation and it’s at 20% so no issues there. I’ve raised a case with Microsoft to investigate.
      • GilbertQ's avatar
        GilbertQ
        Super User
        Hi there

        How much memory in total has been allocated?

        It could be that other datasets have consumed all the available memory?
  • So it turns out it’s an issue connecting to the source DB. I’m running a serverless Azure SQL DB with auto pause enabled and it appears that the connection attempt isn’t waking up the server like it should.

    So Microsoft’s suggestion is to have another report run just before it, which will fail, then the next one should succeed 😕

    I don’t like this option, so I’m just going to change the time the report executes to a little bit later, as there is a data factory pipeline that runs and it starts the instance.
    • GilbertQ's avatar
      GilbertQ
      Super User
      Ahh very interesting and I too also run Serverless DB and I have an Azure function which wakes it up before I actually query the DB.

      Thanks for letting us know.
      • TaylorN's avatar
        TaylorN
        Helper I

        GilbertQ yes it is interesting. This is the second time I have had an issue with unpausing the DB (the first was with ADF). Do you mind sharing the code you used for your function? I was going to create one that just attempts to create a connection with a timeout of 120 seconds or something.