This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(288, 15%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EC%3C/text%3E%3C/svg%3E)
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
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:
This is a known issue which is currently being investigated by the product group.
A fix is in development.
Hi Stefan, do you mean a fix also for the rest api url format (my comment above)? Thanks
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(166.4, 12%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESS%3C/text%3E%3C/svg%3E)
Hi Stefan
I'm facing the same issues with our SPSE environment.
Are there any news yet about a releasedate for this fix?
Or is there a known workaround?
I've solved with April CU (but I think it's the January CU included), solved one, issued another... now, after CU, I have strange behavior of web app with trusted provider configured: cannot open View all site content page (only that) directly. If opened any other pages, I can access there and go to all site content. Only web apps with trusted provider, if I go directly to viewlsts.aspx (subsites too), 403 error.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(137.6, 41%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EIM%3C/text%3E%3C/svg%3E)
Hello, should this problem be addressed by April CU? We are experiencing the same symptoms on our SharePoint SE environment, but April CU did not fix it.
sorry... couldn't be April, wrong ref... it was March, probably because had the January one included, and solved MY problem, the excel preview
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(185.6, 17%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EWT%3C/text%3E%3C/svg%3E)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(16, 53%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECZ%3C/text%3E%3C/svg%3E)
Was this issue solved for Sharepoin 2019? We are currently suffering this issue in our organization and (in theory) our servers are patched to the last version.
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...
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(124.80000000000001, 25%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECS%3C/text%3E%3C/svg%3E)
Did you find a solution for this?
Just an update on this. After opening a ticket with Microsoft and many hours of troubleshooting they have advised it is a bug on the distributed cache. There is no workaround that has worked for us and it has left the platform useless for document collaboration. Users report that the share links generated fail most of the time.
I was initially told the fix would be in the April CU but then they back tracked from that. Not sure when it will be fixed at this stage. Do not deploy this to production!
Hi @clarky000
we have exactly the same problem!!! We are glad, we are not alone :)
We were planning to migrate from Sharepoint 2016 to SharePoint SE very soon. But without the possibility of working with office documents, as you said, this is not really an option. It is one of the main, if not THE main feature.
We also run kerberos authentication.
We have currently also a microsoft ticket open and will also reference this page, so microsoft knows that multiple people have the same issue.
It's very sad to hear that it looks like there is currently no solution for this bug.
What we know right now is that this issue only occurs if you have more than one frontend. (which we need for load balancing and as a failover)
If we run only one frontend server and remove the second server from load balancing, the issue is gone.
Would really appreciate any updates, we will also keep you posted, if we hear or learn anything new.
Best regards, Martin
Similar too, with SP SE, same "File Author is null" as only clue but different, because we can create, open edit every files, just one issue: the preview for the excel files, the preview and, if present in a image library, only the excel thumbnail doesn't show. No problem with files, problem only with the rest api that should give us the files as images. It happens that the url in the rest api url we have in the code when tried the preview is right but cannot be opened if the range is with a pipe symbol between the cells (A1|E5). When I replace the | with colon (A5:E5), the url works. I think an update of SP or OOS should be produced.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(102.4, 65%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAM%3C/text%3E%3C/svg%3E)
Hi @clarky000 ,
Chech the followings for troubleshooting please:
Get-OfficeWebAppsMachine and see the output healthy/unhealthy. If it's healthy, you can see whether you allow HTTP or HTTPS requests to you OWA-farm by running Get-SPWOPIZone. If you require HTTPS you can still test HTTP and see if there may be the SSL that's causing your problem. Set HTTP by running Set-SPWOPIZone - zone "internal-http".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.
@clarky000 ,
Is there any progress on this thread? Please feel free to reply.
Thanks for your response Alan. I've confirmed there are no host file entries on the OOS servers. All name resolution is being performed by DNS.
Output for Get-OfficeWebAppsMachine is healthy
Get-SPWOPIZone returns internal-https. I did try changing it to HTTP but it did not resolve the issue. I can resolve the discovery URL from the sharepoint servers without any browser SSL issues so I believe that our issue isn't with the certificate.
Any other advice would be appreciated!
Considering spinning up a fresh OOS farm to see if our Sharepoint SE environment has problems with that...
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(233.6, 28.000000000000004%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGT%3C/text%3E%3C/svg%3E)
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)?
Hi there
The error seems to be fixed in May CU which released yesterday.
https://support.microsoft.com/de-de/topic/description-of-the-security-update-for-sharepoint-server-subscription-edition-may-9-2023-kb5002390-5d150cf3-e42d-4a0e-b015-0b4357b8e5ea
Is there a fix/CU that was release for SharePoint 2019 that also fixed this same issue? Have had 2 farms using different OOS farms as well. See similar issues. Works on one web application, but the others you get the same "there was a problem" message. Thx.