Intermittant errors opening office documents in the browser - Office Online Server and Sharepoint Subscription Edition

clarky000 60 Reputation points
2023-02-17T01:54:51.7133333+00:00

Intermittently our users are getting the error:

Sorry, there was a problem and we can't open this document. If this happens again, try opening the document in Microsoft Word.

Session ID xxxxxxxxxxx

User's image

This occurs when opening office documents in the browser. Either directly from sharepoint or via a "Share" link.

We have 3 other sharepoint environments (1 x Sharepoint SE and 2x Sharepoint 2016) integrated with this OOS farm and none of them have the same issue.

Documents open ok in desktop application (rather than the browser)

Closing the browser, clearing the cache and trying again often resolves the issue but not in all cases

SharePoint server has January 2023 CU

Sharepoint farm is running Kerberos authentication

Logs from the OOS server show:

WOPI CheckFile: Catch-All Failure [exception:Microsoft.Office.Web.Common.EnvironmentAdapters.WopiUserUnauthorizedException: WOPI 401 ---> System.Web.HttpException: Unauthorized -

-- End of inner exception stack trace ---

at Microsoft.Office.Web.Apps.Common.WopiTalky.AddHostResponseDataAndThrow(Exception exception, HttpRequestAsyncResult result)

at Microsoft.Office.Web.Apps.Common.WopiTalky.LogAndThrowWireException(HttpRequestAsyncResult result, HttpRequestAsyncException delayedException)

at Microsoft.Office.Web.Apps.Common.WopiDocument.LogAndThrowWireException(HttpRequestAsyncResult result, HttpRequestAsyncException delayedException)

at Microsoft.Office.Web.Common.HttpRequestAsync.End()

at Microsoft.Office.Web.Apps.Common.WopiDocument.CheckWopiFile()]

FileUnknownException with InnerException from CheckBaseDocument, InnerException: Microsoft.Office.Web.Common.EnvironmentAdapters.WopiUserUnauthorizedException: WOPI 401 ---> System.Web.HttpException: Unauthorized -

-- End of inner exception stack trace ---

at Microsoft.Office.Web.Apps.Common.WopiTalky.AddHostResponseDataAndThrow(Exception exception, HttpRequestAsyncResult result)

at Microsoft.Office.Web.Apps.Common.WopiTalky.LogAndThrowWireException(HttpRequestAsyncResult result, HttpRequestAsyncException delayedException)

at Microsoft.Office.Web.Apps.Common.WopiDocument.LogAndThrowWireException(HttpRequestAsyncResult result, HttpRequestAsyncException delayedException)

at Microsoft.Office.Web.Common.HttpRequestAsync.End()

at Microsoft.Office.Web.Apps.Common.WopiDocument.CheckWopiFile()

FileUnknownException while loading the app. [FileSourceId: -1088102096] [ClusterId: 0] [ExtraErrorInfo: ]


On SharePoint server we are seeing regular 8306 errors only on the WFEs regularly but unsure if it is related:

There is no actor claim so no actor token.

SPApplicationAuthenticationModuleV2: Incoming token does not contain an actor.

Error trying to search in the UPA. The exception message is 'System.ArgumentException: Exception of type 'System.ArgumentException' was thrown. Parameter name: value

The set of claims could not be mapped to a single user identity. Exception Exception of type 'System.ArgumentException' was thrown. Parameter name: value has occured.

The registered mappered failed to resolve to one identity claim. Exception: System.InvalidOperationException: Exception of type 'System.ArgumentException' was thrown. Parameter name: value ---> System.ArgumentException: Exception of type 'System.ArgumentException' was thrown. Parameter name: value

STS Call Claims Saml: Problem getting output claims identity. Exception: 'System.InvalidOperationException: Exception of type 'System.ArgumentException' was thrown. Parameter name: value ---> System.ArgumentException: Exception of type 'System.ArgumentException' was thrown. Parameter name: value

STS Call: Failed to issue new security token. Exception: 'System.InvalidOperationException: Exception of type 'System.ArgumentException' was thrown. Parameter name: value ---> System.ArgumentException: Exception of type 'System.ArgumentException' was thrown. Parameter name: value

An exception occurred when trying to issue security token: The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework SDK documentation and inspect the server trace logs..


Troubleshooting steps already taken:

  1. Rebuld Sharepoint farm distributed cache service
  2. Confirmed the host header site collection is in the default zone
  3. Confirmed the security token service is running and healthy
  4. Cleared cache on OOS server farm and restarted IIS
SharePoint Server
SharePoint Server
A family of Microsoft on-premises document management and storage systems.
2,346 questions
Microsoft Office Online Server
Microsoft Office Online Server
Microsoft on-premises server product that runs Office Online. Previously known as Office Web Apps Server.
641 questions
0 comments No comments
{count} votes

6 answers

Sort by: Most helpful
  1. Stefan Goßner 656 Reputation points Microsoft Employee
    2023-03-21T16:54:01.38+00:00

    This is a known issue which is currently being investigated by the product group.

    A fix is in development.

    3 people found this answer helpful.

  2. clarky000 60 Reputation points
    2023-02-22T08:29:09.3633333+00:00

    There are no host entries on the OOS farm and name sesolution is happening via DNS.

    Get-OfficeWebAppsMachine returns healthy for both machines/

    Get-SPWOPIZone returns internal-https and changing it to http does not resolve the issue.

    I can resolve the OOS discovery URL anywhere on the network and there are no browser SSL errors reported so I think we are ok there.

    Any other advice would be appreciated. Seriously considering spinning up a new OOS farm to see if SPSE has issues connecting to that also...

    1 person found this answer helpful.

  3. AllenXu-MSFT 20,366 Reputation points Microsoft Vendor
    2023-02-17T07:16:45.26+00:00

    Hi @clarky000 ,

    Chech the followings for troubleshooting please:


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


  4. GULLBERG Tom 25 Reputation points
    2023-05-08T08:55:37.73+00:00

    Exactly same error on our test solution - using Windows Srv 2019 and SharePoint 2016 in a MinRole 3-tier solution (SQL 2019). OOS server patched with March-CU and SP2016 patched with April-CU. Also have SharePoint Workflow Manager 1.0 running on a separate server (works OK). All communication etc works fine between OOS and SP. Tried both HTTP setup and HTTPS setup. Same error on both tests. Hope for a quick resolution on this problem/bug! Where should we keep a lookout for any updates/bugfixes (besides this post)?

    0 comments No comments

  5. Sandro S 0 Reputation points
    2023-05-10T08:29:26.0933333+00:00

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.