搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

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

  • 3 回覆
  • 1 有這個問題
  • 1 次檢視
  • 最近回覆由 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