Access Web App error "403 Forbidden"

A number of existing Access Web Apps are reporting an error "403 Forbidden" when you attempt to view them from an Internet browser and "Server was unable to process request ---> Only users who can View Pages can list Apps." when used from the Access client.

This issue was resolved Saturday, June 7th at approximately 11:00PM UTC.

Details from the Office 365 Service Status:

Closure Summary: On Monday, June 2, 2014 at approximately 11:00 PM UTC, engineers identified an issue in which some customers were unable to open SharePoint Online Access Web Apps that were created prior to May 23, 2014. Investigation determined that a database misconfiguration in the capacity which stores Access Web App data caused the issue. Engineers implemented a fix across the affected capacity which remediated impact. The issue was successfully fixed on Saturday, June 7, 2014 at approximately 11:00 PM UTC. A post-incident report will be available on the Service Health Dashboard within five business days.

Comments (3)
  1. Hi Dean,

    This is showing up within my service status. From SharePoint Online I select Admin > Track service health and maintenance > Office Web Apps (Today) and then I’m able to see incident SP7050.

    Here’s a link on correlation ID’s, but in short there’s not much an end user is able to do with them.

    SharePoint 2010 Correlation ID in error messages: what it is and how to use it


  2. Dean Gross says:

    Thanks for letting us know about this. could you also post messages like this in the Office 365 Message center? this would help to ensure that everyone is informed.

    On a related topic, I have been getting errors that generate correlation id values but these don’t tell me very much about what has gone wrong. What is the best way to investigate these types of errors?

  3. Dan says:

    Hi, I’ve been receiving this exact error message for the past few hours. Is it a recurring or temporary issue? Slightly confused by the time stamps on th comments below. Thanks.

Comments are closed.

Skip to main content