We met an issue on Office Web App with SharePoint 2013.
Error message on the page:
Sorry, there was a problem and we can't open this document. If this happens again, try opening the Microsoft Word.
There is no related log in Windows Event viewer.
In SharePoint ULS log, related message as below:
08/12/2014 06:42:45.49 w3wp.exe (0x2C90) 0x2FE0 SharePoint Foundation Claims Authentication ahds8 Unexpected SPJsonWebSecurityBaseTokenHandler: Issuer name in token '00000003-0000-0ff1-ce00-000000000000@testrealm' doesn't match any of the registered issuer names for trusted sts 'collaboration metadata'. 7ba9aedb-4658-4a32-aaaa-20bcd0d52be6 08/12/2014 06:42:45.49 w3wp.exe (0x2C90) 0x2FE0 SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (Application Authentication Pipeline). Execution Time=7,5254676222816 7ba9aedb-4658-4a32-aaaa-20bcd0d52be6 08/12/2014 06:42:45.49 w3wp.exe (0x2C90) 0x2FE0 SharePoint Foundation Application Authentication ajezu Unexpected SPApplicationAuthenticationModule: Failed to authenticate request, unknown error. Exception details: System.IdentityModel.Tokens.SecurityTokenException: Issuer name is not registered at Microsoft.SharePoint.IdentityModel.SPJsonWebSecurityBaseTokenHandler.ValidateTokenIssuer(X509SecurityToken signingKey, String tokenIssuer) at Microsoft.SharePoint.IdentityModel.SPJsonWebSecurityBaseTokenHandler.ValidateToken(SecurityToken token) at Microsoft.SharePoint.IdentityModel.SPJsonWebSecurityTokenHandler.ValidateToken(SecurityToken token) at Microsoft.SharePoint.IdentityModel.SPApplicationAuthenticationModule.TryExtractAndValidateToken(HttpContext httpContext, SPIncomingTokenContext& tokenContext) at Microsoft.SharePoint.IdentityModel.SPApplicationAuthenticationModule.ConstructIC... 7ba9aedb-4658-4a32-aaaa-20bcd0d52be6 08/12/2014 06:42:45.49* w3wp.exe (0x2C90) 0x2FE0 SharePoint Foundation Application Authentication ajezu Unexpected ...laimsPrincipalAndSetThreadIdentity(HttpApplication httpApplication, HttpContext httpContext, SPFederationAuthenticationModule fam) at Microsoft.SharePoint.IdentityModel.SPApplicationAuthenticationModule.AuthenticateRequest(Object sender, EventArgs e) 7ba9aedb-4658-4a32-aaaa-20bcd0d52be6 08/12/2014 06:42:45.49 w3wp.exe (0x2C90) 0x2FE0 SharePoint Foundation General 8nca Medium Application error when access /sites/111/_vti_bin/wopi.ashx, Error=Issuer name is not registered at Microsoft.SharePoint.IdentityModel.SPJsonWebSecurityBaseTokenHandler.ValidateTokenIssuer(X509SecurityToken signingKey, String tokenIssuer) at Microsoft.SharePoint.IdentityModel.SPJsonWebSecurityBaseTokenHandler.ValidateToken(SecurityToken token) at Microsoft.SharePoint.IdentityModel.SPJsonWebSecurityTokenHandler.ValidateToken(SecurityToken token) at Microsoft.SharePoint.IdentityModel.SPApplicationAuthenticationModule.TryExtractAndValidateToken(HttpContext httpContext, SPIncomingTokenContext& tokenContext) at Microsoft.SharePoint.IdentityModel.SPApplicationAuthenticationModule.ConstructIClaimsPrincipalAndSetThreadIdentity(HttpApplication httpApplication, HttpContext httpCont... 7ba9aedb-4658-4a32-aaaa-20bcd0d52be6
The farm is having 2 WFE. There is NLB setting up for them.
AAM has been set to Default.
OWA binding set to -AllowHttp, zone set to internal-http. AllowOAuthOverHttp set to true.
The strange thing is when days ago we finish the installation, we try the link http://{server_name}/somefolder/document.docx to do the test, it works fine.
But today we try the link http://{NLB_link}/somefolder/documnet.docx, above error occur.
We are not sure whether AAM setting cause this issue or some other reaone. But even we remove the AAM to use the Server Name in link, still above issue.
Any idea/comments would be appriciated.