Do you want to: Report a bug
Document Server version: 8.1
OS: Sonoma 14.4
Browser version: Chrome Version 129.0.6668.71
Additional information:
Getting the popup error: An error occurred during the work with the document. [Error] Use the ‘Download as’ option to save the file backup copy to a drive. Tried this document on the onlyoffice website as well.
Please provide the following additional information:
Does the issue occur with all documents or only with a specific one?
On which OS is the Document Server installed?
Which application are you integrating with Document Server? (e.g., Nextcloud, Alfresco, or your own one)
Is the issue reproduced in the integrated Example? (To access it, first go to your_documentserver_url/welcome page, run the provided command, and then visit your_documentserver_url/example page)
Does the issue occur with all documents or only with a specific one?
This issue only occurs with a specific document. I have uploaded it to the OO demo site, and you can see the error here: https://madeleinetan.onlyoffice.com/s/tSRzLT8n6jqNthK
if you right click on this deleted text on page 1 and click “Accept Change”:
“Specified Indebtedness” will have the meaning specified in Section 14 but it will not include (i) indebtedness in respect of deposits received in the ordinary course of a party’s banking business or (ii) any payment not made because of an intervening change in law making such payment illegal, a force majeure or an act of state, provided that the party had available sufficient funds to make such payment at the time of non-payment.
The error pops up. The same goes for other parts of the doc, for example teh deleted text on page 3.
On which OS is the Document Server installed?
My personal OS is Sonoma but seeing this error on different versions
Which application are you integrating with Document Server? (e.g., Nextcloud, Alfresco, or your own one)
Our own
Is the issue reproduced in the integrated Example? (To access it, first go to your_documentserver_url/welcome page, run the provided command, and then visit your_documentserver_url/example page)
Yes
Thanks for laying out all those details so clearly — that makes it much easier to understand what’s going on.
It definitely looks like the problem is tied to the specific document content (the tracked changes in particular). Since it’s reproducible on the OO demo site and also happens in the standalone example, it’s probably not related to your integration code or your own environment.
Given that, it might be best to open an issue (or support ticket if you have a subscription) and attach that document. They’ll be able to run it through their internal debuggers to pinpoint exactly why accepting the change fails. In the meantime, you could also try saving the document in a slightly different format (like re-saving as DOCX or ODT from another word processor) to see if that cleans up any corrupt markup.
Hope this gets resolved quickly for you — sounds like you’re already on top of it!