Report Builder protected cell or sheet error

[JIvo]

Hi, did anyone experience the below Report Builder error?
It's been happening since yesterday (3rd June 2024) on all Excel files and it's affecting all team members who are using Report Builder.
Many thanks

[fhusain]

Hey @JIvo, Unless there's a macro someone has accidentally triggered, protection doesn't just turn on as far as I know, but this can be checked with the client care with the help of a workbook which is throwing an error; you might also need to provide them with access such that they can try to reproduce and get the report builder logs. I also tested this in my test org as well just to see if this is some sort of generic error, but it works as expected. 

[IñakideBilbao]

Hi, I have the same problem. Since 3rd of June every time I try to refresh the report builder the same error occurs " The shell o shet is protected...". I have checked and I have everything correct...

[AWalsh1]

Just adding that I have the same problem. I uninstalled the Report Builder version I was using and installed the latest version (5.6.56.0) and the problem is still there. Other members of my team using the same version of Report Builder are not encountering the issue.

[Jennifer_Dungan]

I'm having the exact same problem... nothing is locked or protected, but it sure seems to think it is!

The issue seems to coincide with an update that was just pushed to Office 365 (I got the update on one computer and started getting problems, so I tried another computer with the same file... after rebooting I got the update and the second computer had the same issue....)

However, if you hit "okay" for every request error, it will actually run and update the cells.......

[Jennifer_Dungan]

I should have said "there was no issue on the second computer at first... only after office got the update"

[fhusain]

Hey @Jennifer_Dungan I'll try to see if I can find something on this internally.

[Jennifer_Dungan]

Thank you @fhusain I appreciate this.. and if this is tied to Office 365 update, we are likely to see more people hit by this as time goes on.

Also, I should mention that this only seems to impact existing reports... if I create a new file and new requests there's no error (I have not attempted to refresh data on a new file to see if the issue occurs there). The report that I got the issue on I've been using for 3 years, and I am the only person who access the "working file".

[nm_iquanti]

I am facing the same issue. To test out if it is happening with the existing sheets, I created a new simple query on a new excel sheet, it populated the data for the first refresh. But when I refresh the same query again it is throwing the same cell or sheet protection error.

[fhusain]

We are checking this internally. Will update this thread if I hear something back. 

[nm_iquanti]

Hey, could you please let us know if there is any update on this issue or if raising a ticket to adobe support would help?

[fhusain]

Hey @nm_iquanti, An issue is logged to the engineering team. You may also create a ticket from the Admin Console to client care. 

[fhusain]

Hey All, The issue has been fixed in the Report Builder version 5.6.57, which should be available for download by tomorrow.

[Jennifer_Dungan]

Yay, thank you so much for this update @fhusain! We appreciate your follow-up as always.

[JIvo]

Many thanks!

[nm_iquanti]

Hey, may we know the new update release time?

[fhusain]

The new version has been released and is available for download from Analytics -> Tools -> Report Builder.

[IanRemillard]

@fhusain Will this update be pushed or do we have to reinstall RB all together?  

[derekm99509748]

This is good news because I've been having the same problem. Why hasn't this been communicated more broadly? 

[Jennifer_Dungan]

I can't speak to the communication part of this... but I agree, it should be..

As for the "fix", @fhusain I updated my Report Builder last month, but I am still getting the issue....

[fhusain]

Hey @Jennifer_Dungan, That's strange. I haven't seen anything reported yet. We can check internally via customer care ticket.

Also, this fixed via AN-350691 which is mentioned in the release notes and is updated regularly:
https://experienceleague.adobe.com/en/docs/analytics/release-notes/previous/2024#:~:text=issues%3A%2...