Forum Discussion

Rflad's avatar
Rflad
Icon for Advocate I rankAdvocate I
10 years ago
Solved

Error auto refresh SP Online lists (Canceled by user / FirstUniqueAncestorSecurableObject) ?

I got two reports that have been working for 6 months or so, no I am getting either "canceled by user" or the below error when trying to use the schedule update option for these reports.    "FirstU...
Need Help
  • Rflad's avatar
    Rflad
    10 years ago

    Seems to be working now.
    - Reentering credentials did not help
    - Renaming report, upload/republish and refresh worked

     

    Tried that as well yesterday but today at least it worked.

    Thanks :-)

     

    PS: a small minus is that you have to recreate all "links" in your dashboards since the old reports don't work anymore.

Eric_Zhang's avatar
Eric_Zhang
Icon for Microsoft Employee rankMicrosoft Employee
10 years ago

Rflad

The error disappears as of now in my side， can you try to re-enter the credential or just re-create a new report and try to refresh?

Rflad's avatar
Rflad
Icon for Advocate I rankAdvocate I
10 years ago

Seems to be working now.
- Reentering credentials did not help
- Renaming report, upload/republish and refresh worked

 

Tried that as well yesterday but today at least it worked.

Thanks :-)

 

PS: a small minus is that you have to recreate all "links" in your dashboards since the old reports don't work anymore.

  • fjgvillalon's avatar
    fjgvillalon
    Regular Visitor
    9 years ago

    I have the same problem...even though I did everything

    • TonyMcA's avatar
      TonyMcA
      Frequent Visitor
      9 years ago

      I'm also having the same error on a dataset using a SharePoint list that has been working for months:

      Data source error:The 'HasUniqueRoleAssignments' column does not exist in the rowset.
      Cluster URI:WABI-NORTH-EUROPE-redirect.analysis.windows.net
      Activity ID:af12d896-c66c-49a8-910c-9c3b37ecfc36
      Request ID:31ae2671-3e24-0e44-bfbe-c4776e9d11d8
      Time:2017-05-12 07:19:37Z

       

      I've not managed to work around it. I've recreated the dataset and republished, but get the error as soon as I republish.

       

      Regards, Tony