Licensekey.dat appears to crash or block connections to my server

[Slakkenspoor]

Good day,

I have recently installed a fresh instance of ts3 server for windows x64 due to changing which online community I was in and was therefor allowing main access to my server.

Now, however, my licensekey.dat no longer works. When I place it in the server's root and I restart the server, no error messages get displayed but connection from within my own network to the server's external IP no longer work (they had worked before) and using 127.0.0.1 from the local machine doesn't work either.

On one occasion the ts3 client connected for a fraction of a second, displaying the welcome message then announcing a servershutdown immediately. (Server has been shut down: Server Shutdown!
<21:27:51> Disconnected from server)

After reading my way through FAQ's aimlessly I decided to contact Sales support (they seem to be the go-to for most licenseproblems) and they told me to look for an answer here. So here I am.

Stuff from the licensekey.dat:
type : Nonprofit
start date : Sun Mar 18 00:00:00 2012
end date : Tue Sep 18 00:00:00 2012
max. virtual servers: 10
max. slots : 512
description : TeamSpeak 3 Non-Profit License

Runs on win 7 ultimate x64
Crashes when started with the licensekey, works fine without the key in its root. (just doesn;t have enough slots like that)
I'd gladly supply any other needed info.

Best regards.

[SilentStorm]

Serverlogs would be the first step to check...

[dante696]

I guess your licen key is running on 2 different ip's but yes, please provide a server log first.
This log file will show you, what is going on with your server.

[Slakkenspoor]

And how would it preferably be provided?
.txt files?

I have looked through them after recreating the problem. It gives me a 'too many slots hosted!, shutting down!' error in there, even though the running server without key runs on 32 slots. The second log created simulaneosly only states that it starts listening and is stopped the same second.

[SilentStorm]

As we already thought: You are running too many Slots on your License, most likely because you are still running a Server (or multiple) on the same License on some other Machine...
Shutdown the other Server before trying to run the new one.

[dante696]

Maybe his license is blocked already, maybe it was abused, this is nothing i can answer here.

A full log would be helpfull.

[Slakkenspoor]

With all the disconnecting and reconnecting without license it's a whole bunch of little logfiles, as opposed to one nice little file.
How would I find out if it is blocked? It would make the most sense as I only run this one server.

Are these blocks permanent?

Attached are two logs created simultaneously when starting the server through a shortcut wich changes the serveradmin password (in target), this makes the client connect for a half second before disconnecting instead of not connecting at all. (not that that sounds relevant to anything though)

[dante696]

Ok it's simple and nothing seems to be blocked here.
Your license file is used somewhere else or the old server was killed and not stopped. you have to wait ~2 hours without using the license file.

[Slakkenspoor]

Will check this out. Can I run the corrent server without license though?
Thanks in advance, and great to see this stuff answered so quickly

[dante696]

You can not start the server as long it does use more then 32 slots.
You have to edit the server per query.

This is for server with id1

login serveradmin password
use sid=1 -virtual
serveredit virtualserver_maxclients=32
use sid=0
serverstart sid=1

[Slakkenspoor]

The query you posted gave me two errors (error id=2816 msg=virtualserver\slimit\sreached and one about the server has an invalid status), but after the two hours it would boot again with the licensekey.dat in the root, now let's see if it will stay up. I'll reply or edit this post later to hopefully resolve this thread.

Thanks in advance, your quick responses are greatly appreciated.

-- EDIT 20-08-2012: It's been a nice while and I haven't had further problems with the licensekey.dat.
Problem solved, thanks to everyone involved and this thread can be closed.