EDIT WORD DOCUMENT MISSING PC
Press “Edit” and you will be asked whether you want to open the doc in MS Word on your PC or in MS Word Online. It is standard MS Word, installed on their server, that shows us this picture. MS Word Online opens documents perfectly using own Viewer. And here’s the result of our little research: the list of things you actually can do using ONLYOFFICE, but can’t using Google Docs or MS Word Online: We compared ONLYOFFICE online editors to our main rivals – Google Docs and MS Word Online. “Sorry, your session has expired! Please refresh the page to continue ”ģ) Can we switch off auto-saving? Is there a way to save the document explicitly i.e.We’re frequently asked the same question: what benefits does ONLYOFFICE have in comparison with other document editors? So, it’s high time we gave all of you detailed answer. What is the reason for this and how can we stop this from happening? The “Refresh” button allow users to open/save the file outside of the browser? Can we disable this message?Ģ) How do we control the session timeout? The following message is displayed within minutes from editing a document. To continue editing this document, please copy your changes and refresh the page " What could be the reason for that?Īlso, we have following questions with regards to editing word documents online? Could you please advice?ġ) We seem to get this error quite often.
EDIT WORD DOCUMENT MISSING CODE
The code works fine on OOS but not on the OWA server. One installed with OWA server and another one with OO Server. We have now changed it to the URL of the host page and everything seems to work fine. You are right, the “HostEditUrl” was set to true. "Sorry this document cant be opened for editing."
"UserCanWrite" was already set to true previously. i.e.,Īs suggested we have added the following two properties to the CheckFileInfo response. I have also emailed you the fiddler response for the complete URL. HBjZjbglWsM+Ko8SFke2chilz+xTAGp6dAf2OlTCncQ= "Sorry, this document can't be opened for editing" It displays the following error when we load the word file in editorframe. The WOPI host code is build using the sample provided here in the link below:Īs I mentioned previously, we are able to view/edit excel and powerpoint documents but ONLY able to view docx files. Just to let you know that we have installed a single-server Office Web Apps Server farm that uses HTTP for internal testing purposes. Storage Manifest query request with token 1 failed with error code InvalidSerialization dd7f56af-8cda-495f-9bab-77150972d7b8 Cell storage request with token 1 has failed, error = InvalidSerialization, error description: "InvalidSerialization" dd7f56af-8cda-495f-9bab-77150972d7b8 The file name is "WopiEditDocxTest1.docx" and the error is as follows which does not make much sense to us? Would be great if you could give us some advice on this. We have done a quick test after enabling the verbose logging and emailed you the log file which contains the error and other verbose information. Thanks for your response and instructions. ULS.SendTraceTag(0x0048e0e3 /* tag_asod9 */, ULSCat.msoulscat_WAC_WordViewer, ULSTraceLevel.Warning, "Unexpected ActionBehavior for switching to edit mode", behavior) ULS.ShipAssertTag(0x0048e0e1 /* tag_asod7 */, ULSCat.msoulscat_MSOSP_Error, appFrame != null) There is a log viewer available for downloadĪlthough, they are just text files and you can search for tags found in source. The logs are located in C:\ProgramData\Microsoft\OfficeWebApps\Data\Logs\ULS on the WAC server, just use the last or next to last dated log after repro. If the error you receive in the Office web app online has a correlation id, you can search for that. You can also search on the file name if it appears in the URL or if you know the ID in the URL. Then repro and look at the logs on the server and that might show the what the problem is. Set-officewebappsfarm -logverbosity "Verbose" On the server, open a powershell admin console and do these: Office Web Apps server (on-prem) logs information to a text file that is fairly easy to read. If you follow these and send the resulting logs to referencing the URL for this thread and my name, I will review them and get back to you. Also, please send me the problem document and the correlation id (if you see it when the error occurs). Below are instructions to gather these logs and view them. We need to look at the ULS logs from the OWA 2013 server.
0 kommentar(er)
