• Hey Guest, we're evolving the future of TeaSpeak.
    You're invited to join the discussion here!

Difficulties in updating the client to 1.4.2-6

Vafin

TeaFanatic
When upgrading the client to version 1.4.2-6, I encountered the following errors.

1575906483279.png
Code:
[6C69][2] ----------- log started at 2019-12-09.17:58:46 -----------
[6C69][2] App executed as admin: no
[6C69][2] Requesting administrator rights
[6C69][2] Admin right granted. New updater instance executes the update now.
[6C69][2] ----------- log ended at 2019-12-09.17:58:49 -----------
[14FD][2] ----------- log started at 2019-12-09.17:58:49 -----------
[14FD][2] App executed as admin: yes
[14FD][2] loading config from file C:\Users\Admin\AppData\Local\Temp\teaclient_update_j7uzvk\update_install.json
[14FD][1] Loaded 1 locking actions and 79 moving actions
[14FD][2] Awaiting the unlocking of all files
[14FD][5] Failed to lock file C:\Program Files (x86)\TeaSpeak\TeaClient.exe. Timeout: 5000, Time tried: 5026
[14FD][2] Rollbacking 0 moved files
[14FD][2] Rollbacking 0 deleted files
[14FD][2] Rollback done
[14FD][2] executing callback file C:\Program Files (x86)\TeaSpeak\TeaClient.exe with fail command line C:\Program Files

(x86)\TeaSpeak\TeaClient.exe --no-single-instance --update-failed-

new=bG9nX2ZpbGU6UXpwY1ZYTmxjbk5jUVdSdGFXNWNRWEJ3UkdGMFlWeE1iMk5oYkZ4VVpXMXdYSFJsWVdOc2FXVnVkRjkxY0dSaGRHVmZhamQxZW5aclhI

VndaR0YwWlMxc2IyY3VkSGgwO2Vycm9yX2lkOmJXRnBiaTFsZUdVdGJHOWphdz09O2Vycm9yX21lc3NhZ2U6Ykc5amF5QjBhVzFsYjNWMElDZzFNREF3S1E9

PQ==
[14FD][2] ----------- log ended at 2019-12-09.17:58:54 -----------
---- Automatically Merged Double Post ----

After that, I removed everything related to the client and repeated the installation in the usual way. But even so, there were errors during installation. On the third time the client as not strange was established.

---- Automatically Merged Double Post ----

Perhaps difficulties in updating were only for me. Need more feedback.
 

Attachments

Last edited:

WolverinDEV

TeaSpeak Team
Staff member
Administrator
Ensure you've only on process running.
This issue mainly results in the issue that sometimes the TeaClient does not terminates his process quick enought.
Usually killing the processes within the task manager resolved this issue :)
 

Vafin

TeaFanatic
Ensure you've only on process running.
This issue mainly results in the issue that sometimes the TeaClient does not terminates his process quick enought.
Usually killing the processes within the task manager resolved this issue :)
It is necessary to register in the update code the forced termination of processes that prevent the update.
 

REDOSS

TeaSpeak Team
Staff member
TeaTeam
But I may could show a message that all instanced of the TeaClient should be stopped.
That is a good solution I guess.
As far as I know, this is the only way to solve the problem in most Windows applications :)