搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Microsoft Excel online (E1 License) suddenly broke down (became unusable)

  • 3 个回答
  • 1 人有此问题
  • 14 次查看
  • 最后回复者为 jonzn4SUSE

more options

I was using Firefox to use the Microsoft Office online E1 Licensed ever since I joined my company. It was working without any issues so far but suddenly yesterday in Excel online it showed an error that said we are still loading the workbook and it was not editable. Waiting for hours did not resolve the issue. I should also mention that Firefox is updated to the latest version, sync is on, other workbooks are showing the same error, and I am having no issues with Excel online (same account + same workbooks + new workbooks) in other browsers. Today I tried clearing the cache and online Excel completely broke (screenshot). Please help!

I was using Firefox to use the Microsoft Office online E1 Licensed ever since I joined my company. It was working without any issues so far but suddenly yesterday in Excel online it showed an error that said we are still loading the workbook and it was not editable. Waiting for hours did not resolve the issue. I should also mention that Firefox is updated to the latest version, sync is on, other workbooks are showing the same error, and I am having no issues with Excel online (same account + same workbooks + new workbooks) in other browsers. Today I tried clearing the cache and online Excel completely broke (screenshot). Please help!
已附加屏幕截图

被采纳的解决方案

@jonzn4SUSE Thank you for your reply. I think someone from the back-end worked on the issue. It has been completely resolved now. Thank you though. Thank you for taking the time to reply :)

定位到答案原位置 👍 1

所有回复 (3)

more options

That appears to be on Sharepoint and a work related doc right? There is no way for us to replicate the issue with a work related doc. What happens if you go to Excel online and open a sample workbook from Microsoft?

more options

选择的解决方案

@jonzn4SUSE Thank you for your reply. I think someone from the back-end worked on the issue. It has been completely resolved now. Thank you though. Thank you for taking the time to reply :)

more options

Glad to hear it. Please mark your comment as resolved. Thanks