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

TeaClient 1.1.0 A critical error happened

Sakora

New member
Folgendes Problem, ich installierte ihn und bekamm dann irgendteine fehlermeldung von wegen Temp und ka was der von mir will schaut einfach mal selbst ;)
 

Attachments

Sakora

New member
so hab beides neu erstellen müssen und dachte mir ich füg sie gleich zu einem zusammen, aber sind nun schärfer :D
 

Attachments

Vafin

TeaFanatic
Could you extend the window i guess there must be a littlebit more :/
[Window Title]
A critical error happened!

[Content]
Failed to load native extensions: Error: The specified module could not be found.
\\?\C:\Users\Admin\AppData\Local\Temp\0e619f74-1c0b-443a-852b-8810a2249cbf.tmp.node

[exit]
 

WolverinDEV

TeaSpeak Team
Staff member
Administrator
Hmm lovely nothing.
There will be an update which allows to see the full error (hopefully it will be better then server v27 ':))
 

Vafin

TeaFanatic
http://clientapi.teaspeak.de/files/release/1.1.0-1/TeaClient-win32_x64.exe
There shall be a littlebit more error reporting within the terminal
C:\Windows\System32>cd C:\Program Files (x86)\TeaSpeak

C:\Program Files (x86)\TeaSpeak>start TeaClient.exe

C:\Program Files (x86)\TeaSpeak>
Main app executed!
Spawn loading screen
Spawn window!
request: http://clientapi.teaspeak.de//api.php?type=update-info
Loading ui package
Local cache: { local_index:
{ channel: 'release',
version: '1.0.1',
git_hash: 'a8ffc73',
timestamp: 1542651802 } }
Got ui info { channel: 'release',
version: '1.0.1',
git_hash: 'a8ffc73',
timestamp: 1542651802,
required_client: undefined }
Unpacking cached ui info
Unpacked. Target path: C:\Users\Admin\AppData\Roaming\TeaClient\tmp\ui\release_1
542651802
Successfully downloaded everything!
 

WolverinDEV

TeaSpeak Team
Staff member
Administrator
Okey sure thats the latest client?
May just download the folder, extract it and run it out of the box.
 

WolverinDEV

TeaSpeak Team
Staff member
Administrator
Hmm sh*t I'm using Win 10 or 7.
Thats may the reason why I haven't that error.

And you're really 100% sure?
That cant be actually possible... I've extra added a lot of stuff to detect exactly that.