Sign in
 

none
Error opening some documents with Office Web App Server after March 2017 CU installation RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    after Installation of the march 2017 public updates for SharePoint 2013 we got the following error by opening some documents (not all) with Office Web App Server. The documents types are random, but if a document can't be opened once, this document can't be opened in the future (is reproducable). If a dcoument could be opened, it could be opened in the future as well (also reproducable). So we assume a relationship with the documents, checking out and in doesn't help. The Office Web App Server is used also by Exchange/Lync and is working correctly, so it should have do to primarily with SharePoint (and the updates).

    Excerpt from the OWA log file:

    03/20/2017 16:42:06.97 w3wp.exe (0x5EF8)                          0x5B94  Office Web Apps               WAC Hosting Interaction                       adhsg     Monitorable        WOPI: Could not deserialize file metadata [url:http://xxx.xxx/xxx/internet%2520dokumente/_vti_bin/wopi.ashx/files/af3abc2a03934a8684fe2979532de2a6, e:There was an error deserializing the object of type Microsoft.Office.OpenWebApplication.WopiCheckFileResponse. Encountered unexpected character '<'.]                af490c62-e8f2-4d6f-9a81-5e017196e259

    03/20/2017 16:42:06.97 w3wp.exe (0x5EF8)                          0x5B94  Office Web Apps               WAC Hosting Interaction                       adhsh     Monitorable        WOPI: Invalid file metadata [url:http:// xxx.xxx/xxx/internet%2520dokumente/_vti_bin/wopi.ashx/files/af3abc2a03934a8684fe2979532de2a6, triggers:(No Hash No Version No FileName No OwnerId), data:  <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">  <html xmlns:o="urn:schemas-microsoft-com:office:office" lang="en-us" dir="ltr">  <head><meta name="GENERATOR" content="Microsoft SharePoint" /><meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><meta http-equiv="Expires" content="0" /><meta http-equiv="X-UA-Compatible" content="IE=8"/><meta name="ROBOTS" content="NOHTMLINDEX" /><title>      Error    </title><link rel="stylesheet" type="text/css" href="/_layouts/15/1033/styles/corev15.css?rev=Enh7f%2BrXncl...  af490c62-e8f2-4d6f-9a81-5e017196e259

    03/20/2017 16:42:06.97*               w3wp.exe (0x5EF8)                          0x5B94  Office Web Apps               WAC Hosting Interaction                       adhsh     Monitorable        ...4CuQdAWs6MQ%3D%3D"/> <link rel="stylesheet" type="text/css" href="/_layouts/15/1033/styles/error.css?rev=nc1850SZNy60qTAeQIRxsA%3D%3D"/> <script type="text/javascript" src="/_layouts/15/init.js?rev=Cv9RhP3nrueoFDa3tkS6FQ%3D%3D"></script> <script type="text/javascript">RegisterSod("initstrings.js", "\u002f_layouts\u002f15\u002f1033\u002finitstrings.js?rev=rvK\u00252BOBkjPeQAF3rjImlgDQ\u00253D\u00253D");</script> <script type="text/javascript">RegisterSod("strings.js", "\u002f_layouts\u002f15\u002f1033\u002fstrings.js?

    Any hints?

    Thx,

    Hans

    Hans Herrgott

    Thursday, March 23, 2017 9:17 AM
    |

Answers

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    further Information. On the SharePoint Server application event log we found many errors with ID 1309 and source "ASP.NET 4.0.30319.0"

    Please note, that the URL contains a blank between "internet" and "dokumente", should read "internet dokumente", just hoping that this web editor doesn't make any own changes...

    Marked with bold some strange parts which came to my Attention.

    Details:

    Event code: 3005
    Event message: An unhandled exception has occurred.
    Event time: 23.03.2017 13:53:12
    Event time (UTC): 23.03.2017 12:53:12
    Event ID: f455b9bb8cba4a3099bc08b1764837c3
    Event sequence: 119276
    Event occurrence: 38
    Event detail code: 0
     
    Application information:
        Application domain: /LM/W3SVC/312569578/ROOT-1-131347033862187868
        Trust level: Full
        Application Virtual Path: /
        Application Path: C:\inetpub\wwwroot\wss\VirtualDirectories\SharePoint Intranet Prod2013-80\
        Machine name: XXXPS04
     
    Process information:
        Process ID: 11584
        Process name: w3wp.exe
        Account name: XXX\sp_iispool
     
    Exception information:
        Exception type: HttpException
        Exception message: A potentially dangerous Request.Path value was detected from the client (%).
       at System.Web.HttpRequest.ValidateInputIfRequiredByConfig()
       at System.Web.HttpApplication.PipelineStepManager.ValidateHelper(HttpContext context)


     
    Request information:
        Request URL: http://xxx.xxx.com/org/wm/dw/internet dokumente/_vti_bin/wopi.ashx/files/f6cc2fb58fa04fa79859ea2265d6a1ed?access_token=eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiIsIng1dCI6IkJRVVdvRlRsS0VVbDRwYlNScm8zYTVObElnSSJ9.eyJhdWQiOiJ3b3BpL2ludHJhbmV0LmF1bWEuY29tQDJhODNkMzdjLTFlNzItNGRjMi1iZWI0LWFiMjA2NTU5Y2ExYiIsImlzcyI6IjAwMDAwMDAzLTAwMDAtMGZmMS1jZTAwLTAwMDAwMDAwMDAwMEAyYTgzZDM3Yy0xZTcyLTRkYzItYmViNC1hYjIwNjU1OWNhMWIiLCJuYmYiOiIxNDkwMjczNTkyIiwiZXhwIjoiMTQ5MDMwOTU5MiIsIm5hbWVpZCI6IjAjLnd8ZnJhbmNlXFxqb3NzZXAiLCJuaWkiOiJtaWNyb3NvZnQuc2hhcmVwb2ludCIsImlzdXNlciI6InRydWUiLCJjYWNoZWtleSI6IjApLnd8cy0xLTUtMjEtMjMzNjA2MzkwMC0zNjE3NzU4MzU5LTEyNDcwNzAwMjMtMTE2NyIsImlzbG9vcGJhY2siOiJUcnVlIiwiYXBwY3R4IjoiZjZjYzJmYjU4ZmEwNGZhNzk4NTllYTIyNjVkNmExZWQ7enJWV09vWTVSSVZBUDVQZGJMUzBZQnpjeWI4PTtEZWZhdWx0OztCMDA4NDMxMDYxO1RydWUifQ.FZKHEm9-jvXHkY5nrzI2w7QvNPSm7--RJw7SbpXSqwtPBzDPt-0voLZsTEgqlKODgxtXtuglYr64MdPBn-tbmBjVfGyHgDZPMLWY5qBMGr7YHE_1AbCnnzVB9O1158iX9ESu-d3LfHx9ELsmcvRUSq4AkOhgkXHSxi7Ft9l5I7JyC7apWODKQkTYvjK5ubR7i3lvrqHGEgoKn8e7HdK3Sgc1tE897Zh5PAbfLbdwmoHyZ1Wc1IbxP7KMqJ46AieuFAPcPpaluJzGpO9DBfrD_YVQkEMshP2H5iXrF3nc5GKhvoIoZxuOlNLXw63lO9Thb6J2unjx-PzYhauZS06aZw&access_token_ttl=1490309592465
        Request path: /org/wm/dw/internethttp://xxx.xxx.com/org/wm/dw/internet dokumente/_vti_bin/wopi.ashx/files/f6cc2fb58fa04fa79859ea2265d6a1ed?access_token=eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiIsIng1dCI6IkJRVVdvRlRsS0VVbDRwYlNScm8zYTVObElnSSJ9.eyJhdWQiOiJ3b3BpL2ludHJhbmV0LmF1bWEuY29tQDJhODNkMzdjLTFlNzItNGRjMi1iZWI0LWFiMjA2NTU5Y2ExYiIsImlzcyI6IjAwMDAwMDAzLTAwMDAtMGZmMS1jZTAwLTAwMDAwMDAwMDAwMEAyYTgzZDM3Yy0xZTcyLTRkYzItYmViNC1hYjIwNjU1OWNhMWIiLCJuYmYiOiIxNDkwMjczNTkyIiwiZXhwIjoiMTQ5MDMwOTU5MiIsIm5hbWVpZCI6IjAjLnd8ZnJhbmNlXFxqb3NzZXAiLCJuaWkiOiJtaWNyb3NvZnQuc2hhcmVwb2ludCIsImlzdXNlciI6InRydWUiLCJjYWNoZWtleSI6IjApLnd8cy0xLTUtMjEtMjMzNjA2MzkwMC0zNjE3NzU4MzU5LTEyNDcwNzAwMjMtMTE2NyIsImlzbG9vcGJhY2siOiJUcnVlIiwiYXBwY3R4IjoiZjZjYzJmYjU4ZmEwNGZhNzk4NTllYTIyNjVkNmExZWQ7enJWV09vWTVSSVZBUDVQZGJMUzBZQnpjeWI4PTtEZWZhdWx0OztCMDA4NDMxMDYxO1RydWUifQ.FZKHEm9-jvXHkY5nrzI2w7QvNPSm7--RJw7SbpXSqwtPBzDPt-0voLZsTEgqlKODgxtXtuglYr64MdPBn-tbmBjVfGyHgDZPMLWY5qBMGr7YHE_1AbCnnzVB9O1158iX9ESu-d3LfHx9ELsmcvRUSq4AkOhgkXHSxi7Ft9l5I7JyC7apWODKQkTYvjK5ubR7i3lvrqHGEgoKn8e7HdK3Sgc1tE897Zh5PAbfLbdwmoHyZ1Wc1IbxP7KMqJ46AieuFAPcPpaluJzGpO9DBfrD_YVQkEMshP2H5iXrF3nc5GKhvoIoZxuOlNLXw63lO9Thb6J2unjx-PzYhauZS06aZw&access_token_ttl=1490309592465dokumente/_vti_bin/wopi.ashx/files/f6cc2fb58fa04fa79859ea2265d6a1ed
        User host address: 192.1.1.175
        User: 
        Is authenticated: False
        Authentication Type: 
        Thread account name: XXX\sp_iispool
     
    Thread information:
        Thread ID: 65
        Thread account name: XXX\sp_iispool
        Is impersonating: False
        Stack trace:    at System.Web.HttpRequest.ValidateInputIfRequiredByConfig()
       at System.Web.HttpApplication.PipelineStepManager.ValidateHelper(HttpContext context)

     
    Custom event Details:

    Hans Herrgott

    Thursday, March 23, 2017 3:20 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Hans,

    Please check the ULS logs, try to find more error message about this issue.

    The default path of ULS log files in SharePoint 2013 is: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS.

    Here is a similar issue for your reference:

    https://www.brightstarr.com/sharepoint-technology-and-application-insights/blog/troubleshooting-sharepoint-2013-document-rendering-through-office-web-apps

    Best Regards,

    Linda Zhang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Friday, March 24, 2017 5:15 AM
    |
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Linda,

    the ULS Logs didn't give much usefull Information. I knew the link you mentioned already, but thsi is very difficult to examine on customers site.

    What we have found out, it looks like that the error only appears in libraries which contain a SPACE char in the site /subsite collection path. When there is a SPACE char in the library name or the document name itself, everything is working fine. I assume, that there must be a relationship with the bold pieces of text in my earlier post. In my opinion there is a new error parsing the URL's for WOPI calls.

    Regards,

    Hans

    Hans Herrgott

    Monday, March 27, 2017 6:29 AM
    |
  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi Hans,

    The issue is caused by the site path with the space cannot be parsed correctly.

    Try Removing the space from the site path.

    Anyway, I will keep an eye on this issue. It would also be appreciated if you can keep updating this thread once there any finding about it.

    Best Regards,

    Linda Zhang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Wednesday, March 29, 2017 12:42 PM
    |
    Moderator
  • Question
    Sign in to vote
    3
    Sign in to vote

    Hallo Hans!

    I received information from an Escalation Engineer that this behaviour is caused by the March 2017 CU.
    A fix for this issue seems to be in preparation.

    I keep you updated.

    Kind regards,
    Christian

    • Marked as answer by H. Herrgott Monday, April 3, 2017 6:14 AM
    Friday, March 31, 2017 12:24 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Christian, i have the same issue. Is there a KB for this yet? Any idea when the fix will be available?
    Monday, April 10, 2017 8:33 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi 00Thatcher00,

    it sounds like that the error is fixed with the April 2017 CU for SharePoint 2013.

    https://blogs.technet.microsoft.com/stefan_gossner/2017/04/13/april-2017-cu-for-sharepoint-2013-product-family-is-available-for-download/

    Regards,

    Hans

    Hans Herrgott

    • Marked as answer by H. Herrgott Thursday, April 13, 2017 6:32 AM
    Thursday, April 13, 2017 5:56 AM
    |