Hello,
The latest update of OnlyOffice Desktop Editor (9.4.0.129) seems to remove the "ONLYOFFICE Update Service" during the update process on a number of machines, causing the update to time out.
Do you have any suggestions for a fix?
Thank you
, Rémy
tis-onlyoffice-desktop problem with ONLYOFFICE Update Service
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Hello,
We're mainly experiencing a runtime error when launching the setup.
Without acknowledging the error message, the installation doesn't continue.
We switched to the MSI file instead of the executable. There are no longer any problems with this version.
Regards,
We're mainly experiencing a runtime error when launching the setup.
Without acknowledging the error message, the installation doesn't continue.
We switched to the MSI file instead of the executable. There are no longer any problems with this version.
Regards,
-
dcardon
- WAPT Expert
- Messages: 1929
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hi Rémi and Mickaël,
we're trying to prioritize the .exe file over the .msi file, given the number of workstations having problems with their msiexec environment (the .msi format was supposed to solve the .exe installation problems, but it also came with its own set of issues).
We're disabling the service to prevent the software from updating itself without the sysadmin's approval. But if the autoupdate refuses to be disabled, things get complicated...
We'll see if we can resolve the issue by stopping the service. Otherwise, we'll switch to the .msi file.
Best regards,
Denis
we're trying to prioritize the .exe file over the .msi file, given the number of workstations having problems with their msiexec environment (the .msi format was supposed to solve the .exe installation problems, but it also came with its own set of issues).
We're disabling the service to prevent the software from updating itself without the sysadmin's approval. But if the autoupdate refuses to be disabled, things get complicated...
We'll see if we can resolve the issue by stopping the service. Otherwise, we'll switch to the .msi file.
Best regards,
Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Hello,
We have fixed the package; it is available in pre-production on our store here: https://wapt.tranquil.it/store/fr/detai ... EPROD.wapt
It should go into production on June 6, 2026.
Sincerely,
Gwenaël
We have fixed the package; it is available in pre-production on our store here: https://wapt.tranquil.it/store/fr/detai ... EPROD.wapt
It should go into production on June 6, 2026.
Sincerely,
Gwenaël
