Hello,

in this thread I will give my best to make a list of common error messages, warnings and some log information. This list will be updated and extended as time goes on. Suggestions on which other errors should be added to this list are welcome.

Index:
  • Failed to connect to server
  • Unable to find valid license key, falling back to limited functionality
  • bind failed on IP:PORT (often: bind failed on 0.0.0.0:PORT)
  • server running elsewhere
  • too many slots hosted, shutting down!
  • detected incorrectly running system clock (>) or detected incorrectly running system clock (<)
  • virtualserver started too many times in a certain time period
  • accounting.teamspeak.com errors:
    TS3ANetwork::Connect failed error: 110
    Unable to connect to primary address, trying secondary
    TS3ANetwork::ResolveHostName failed error: -5 (No address associated with hostname) 110
    TS3ANetwork::Send failed error: 1
    Could not connect to accounting server after multiple attempts, shutting down server
  • insufficient permission modify power OR insufficient client permissions (failed on <name of permission>)





Error: Failed to connect to server
Description: For some reason you are unable to connect to a server. This can have several causes - both client side and server side.
Solution:
If you are trying to connect to someone elses server and get this error, please read this: http://forum.teamspeak.com/showthrea...-amp-Solutions
If you are hosting your own TeamSpeak 3 server and other clients are getting this error, please read this: http://forum.teamspeak.com/showthrea...annot-connect)


Error: Unable to find valid license key, falling back to limited functionality
Description: This is not an error, but a warning. It is displayed in the server instance log (ends in _0.log) when the TeamSpeak 3 server is unable to find or to access a valid license key file.
Solution: If you do not own a license, then there is nothing to do. If you do have a license though, be it a non-profit or a commercial license, please make sure that...
- you uploaded your license to the root directory of your TeamSpeak 3 server (unless you are using the "licensepath" parameter)
- the user running the TeamSpeak server has both read and write access to the file
- the file is called "licensekey.dat"
- the file has been decrypted properly when you downloaded the email attachment. Some mail clients do not do that! Please see here: http://forum.teamspeak.com/showthread.php/77456


Error: bind failed on IP:PORT
Description: The port the TeamSpeak server is trying to bind to is already in use.
Solution: The most common mistake is that people are trying to launch several server instances and all instances try to bind to the same port. Please make sure no other instance of TeamSpeak is running. On most Linux distributions you can check this by executing
Code:
ps aux | grep ts3 -i
Also please make sure no other program is using those ports.


Error: server running elsewhere
Description: This error message is displayed in your servers log and the virtual server in question shuts down. The reason for this is that every server has a unique ID much like a finger print. If the database is copied or a snapshot of a server is being deployed, this key is copied. Only one server on the whole world may use the same unique ID.
Solution: Only run one copy of a server at a time.


Error: too many slots hosted, shutting down!
Description: The total limit of slots for your license has been exceeded and your server will not start or has been stopped.
Solution: The most common errors are the following:
1) Bad permission setup that allows customers to change the slots of the server.
2) You stopped some virtual servers (e.g. server not needed anymore or if you are a commercial hoster maybe one of your customers did not pay their bills) but neglected to prevent them from starting automatically when the instance starts up and restarted an instance which contained several of these servers.
3) You terminated a running instance forcefully (e.g. kill -9) and started other instances that were not previously running which had enough slots to raise you above your slot limit.

The solutions are:
1) Read this FAQ and follow the instructions: https://support.teamspeakusa.com/ind...e/View/318/13/
2) Make sure to set servers you don't want to run to not start automatically by setting their 'virtualserver_autostart' property to 0. This can be done using the serveredit command on the query interface (e.g. serveredit virtualserver_autostart=0). Please note that you should NOT forget to set it back to 1 when you want the server to be running again. All virtual servers that are supposed to be running or that are only stopped briefly should have this property set to 1.
3) Start the instance you forcefully terminated and perform a proper shutdown of that instance before starting any additional instances.



Error: detected incorrectly running system clock (>) OR
detected incorrectly running system clock (<)
Description and solution can be found here: http://forum.teamspeak.com/showthrea...ot-log-message


Error: virtualserver started too many times in a certain time period
Description: You start a server instance and then this same instance stops within 5 seconds of it being started. This happened more than 3 times in a 41 minute window.
Solution: You should first investigate how you managed to trigger this error and change your scripts to avoid triggering the conditions above. Then you must not start any server instance for the 12 minute grace period mentioned above. After this wait, you should be able to start your instance normally.


Error: accounting.teamspeak.com errors:
  • TS3ANetwork::Connect failed error: 110
  • Unable to connect to primary address, trying secondary
  • TS3ANetwork::ResolveHostName failed error: -5 (No address associated with hostname) 110
  • TS3ANetwork::Send failed error: 1
  • TS3ANetwork::ResolveHostName failed error: -5 (No address associated with hostname) 110
  • Could not connect to accounting server after multiple attempts, shutting down server

Description: Not explaining every single error in detail, your server has trouble communicating with our accounting server. Not all of the errors mentioned above are critical though.
Solution: Please make sure no packets sent from accounting.teamspeak.com:2008 (TCP) or sent to that address are being blocked. A list of ports which the TeamSpeak 3 server uses and which connections must not be blocked can be found in this FAQ entry: https://support.teamspeakusa.com/ind...k-3-server-use


Error: insufficient permission modify power OR
insufficient client permissions (failed on <name of permission>)
Description: You are not allowed to change a permission or perform an action because you do not have the required permissions to do so.
Solution and a more detailed description can be found here: http://forum.teamspeak.com/showthrea...t-aid-quot-kit