MetaShare’s current health status

On this page we list the current issues that you might experience with MetaShare, as well as a log of the issues that previously have been addressed and have been resolved.

If you want to check the health status of your Microsoft services, please visit Microsoft 365 Service health status page.

Ongoing problems

We are currently not experiencing any operational disturbances in MetaShare or in any connected Microsoft services (Microsoft Office 365 and Microsoft Azure).

Previous resolved issues

  • MetaShare was not accessible for a few minutes
    • Reported: 2021-11-25 13:06 (CET), Resolved: 2021-11-25 13:18 (CET)
    • Issue:
      • While deploying a hotfix with workarounds for bugs in SharePoint Online’s search engine, MetaShare was unfortunately not accessible for a few minutes.
    • Status:
      • The restart of Azure App Service after the deployment took longer than usual. After about 15 minutes it was up and running normally. We apologize for this unfortunate incident.
  • Search did not show draft documents
    • Reported: 2021-06-04, Resolved: 2021-07-09
    • Issue:
      • By design SharePoint indexes minor versions (0.1, 0.2, 0.3 etc.), if “Draft Item Security” = “Any user who can read items”, is applied (default setting in MetaShare).
      • In some tenants, SharePoint search did however not index minor versions of documents, resulting in only showing published versions of documents (1.0, 2.0, 3.0, etc.) when searching for documents and a library reindexing was not fixing the problem. Approximately 30% of our clients reported this issue.
  • Intermittent disturbances in MetaShare
    • Reported: 2021-06-23, Resolved: 2021-06-25
    • Issue:
      • We were experiencing some operational disturbances in MetaShare, where MetaShare intermittently was being timed out and redirected to this page, where you were prompted to click on the “Try again” button to reload the page:
        Unknown error
    • Status:
      • The disturbances were related to connected Microsoft services (the Azure/Office 365-environment), where we intermittently were having issue in getting the logged in users’ access token from SharePoint. The issue is now resolved.