Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Saber mais

Sharepoint in Microsoft Office 365 will only launch in a private Firefox window

  • 1 resposta
  • 1 tem este problema
  • 55 visualizações
  • Última resposta por jamieson62

All the other apps in Office 365 work as normal but when I launch Sharepoint in a normal Firefox window I get the following error message:

  • Sorry, something went wrong
  • An error has occurred on the server.
  • Technical Details
  • Troubleshoot issues with Microsoft SharePoint Foundation.
  • Correlation ID: xxxxxxxxxxxxxxxxxxxxxxxxxxxx
  • Date and Time: xxxxxxxxxxxxxxxxx

Firefox is up to date (v81.0) and running on a modern up to date Win 10 Pro laptop, I've cleared all my browser history and rebooted but without success. The same web page works without problem in Edge and Chrome but in Firefox it will only work in a private window.

All the other apps in Office 365 work as normal but when I launch Sharepoint in a normal Firefox window I get the following error message: *Sorry, something went wrong *An error has occurred on the server. *Technical Details *Troubleshoot issues with Microsoft SharePoint Foundation. *Correlation ID: xxxxxxxxxxxxxxxxxxxxxxxxxxxx *Date and Time: xxxxxxxxxxxxxxxxx Firefox is up to date (v81.0) and running on a modern up to date Win 10 Pro laptop, I've cleared all my browser history and rebooted but without success. The same web page works without problem in Edge and Chrome but in Firefox it will only work in a private window.

Modificado por jamieson62 a

Solução escolhida

Solved - clearing all site data in the Privacy and Security panel has fixed the problem.

Ler esta resposta no contexto 👍 0

Todas as respostas (1)

Solução escolhida

Solved - clearing all site data in the Privacy and Security panel has fixed the problem.