Creating default VirtualServer failed, error: port already in use

**Sanche** · May 16th, 2019, 06:57 PM

Good day! I have a problem with the new version of the TeamSpeak 3.7.1 server. The fact is that the server starts and closes immediately. I do not know how to fix it. I use the old version of the TeamSpeak server 3.0.10.3, it works well, but the new TeamSpeak 3.7.1 server does not start. The operating system is Windows 7 x64. Could you help solve the problem with the launch of the TeamSpeak 3.7.1 server.
Below are the logs and crashdump
thanks for the help

**dante696** · May 17th, 2019, 08:13 AM

By reading the log you would have seen that the server can not start because all ports are blocked / in use already.

Which ports does the TeamSpeak 3 server use?

**Sanche** · May 17th, 2019, 10:25 AM

Originally Posted by dante696

By reading the log you would have seen that the server can not start because all ports are blocked / in use already.

Which ports does the TeamSpeak 3 server use?

Yes, I read on the forum, I realized that they are used, the firewall is turned off, the ports are forwarded from the router. The new version 3.7.1 doesn’t want to run, and the old version 3.0.10.3 works without problems. I can't understand why the old one works and the new one doesn't, how to fix the problem? thank

**dante696** · May 17th, 2019, 12:33 PM

Please do not compare an ancient version (3.0.x) with latest one.
There are new services and ports needed (please read the link i did add).

**Scratch.** · May 17th, 2019, 01:18 PM

Originally Posted by dante696

Which ports does the TeamSpeak 3 server use?

Looks like you need to add 10022 to that list

**dante696** · May 17th, 2019, 02:29 PM

Done. F5 offers some magic on the FAQ entries.

**Sanche** · May 17th, 2019, 03:29 PM

Originally Posted by dante696

Please do not compare an ancient version (3.0.x) with latest one.
There are new services and ports needed (please read the link i did add).

I read this post, all ports that are listed in the post, were forwarded in the router, also turned off the firewall and in the policy created 2 rules for connecting to any ports. but it still doesn't launch the exact same error. I don’t know where else to look, so I asked for help.

Originally Posted by Scratch.

Looks like you need to add 10022 to that list

and he also added and forwarded

**dante696** · May 17th, 2019, 03:57 PM

And have you checked that the ports are not in use already?
The logs said they are in use (but can also mean something does not open them).

Edit
Could also mean that VOIP ports are blocked from ISP (but error should be something else).

**dante696** · May 17th, 2019, 04:16 PM

The whole discussion was moved out of the 3.7.x Release thread.

I didn't look for the operation system the first time i opened your log and but now i did and saw that you are using Windows Vista.
Your operation system is not supported to run the server.

**Sanche** · May 17th, 2019, 08:17 PM

Originally Posted by dante696

The whole discussion was moved out of the 3.7.x Release thread.

I didn't look for the operation system the first time i opened your log and but now i did and saw that you are using Windows Vista.
Your operation system is not supported to run the server.

checked the opening of ports through the program Port Forward Network Utilities all ports 9987 30033 10011 10022 41144 and 2008 443 2010 - the program answers that all of them are open
I also think that something is preventing the opening of ports.
I turned to the Internet provider, on their part there is no blocking of the ports.
sorry you can see when I uploaded the log files I confused them, since I experimented with the compatibility of the operating system I thought maybe because of this.
then I apply real logs taken from native windows 7

**Sanche** · May 19th, 2019, 06:07 PM

Dear dante696, I am writing again as I have been struggling with setting up a server for a day
steps taken by me:
1) completely reinstalled os windows 7 x64
2) updated windows on 05/19/2019
3) port forwarding 9987 30033 10011 10022 41144 and 2008 443 2010 were made
4) checked through Port Forward Network Utilities - all ports are open
5) the firewall is disabled (but for the sake of insurance, rules for programs on TCP and UPD are also added)
6) through the command netstat -an checked, ports 9987 30033 10011 10022 41144 and 2008 443 2010 are not used

Code:

 TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
 TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
 TCP    0.0.0.0:5357           0.0.0.0:0              LISTENING
 TCP    0.0.0.0:9937           0.0.0.0:0              LISTENING
 TCP    0.0.0.0:12372          0.0.0.0:0              LISTENING
 TCP    0.0.0.0:49152          0.0.0.0:0              LISTENING
 TCP    0.0.0.0:49153          0.0.0.0:0              LISTENING
 TCP    0.0.0.0:49154          0.0.0.0:0              LISTENING
 TCP    0.0.0.0:49158          0.0.0.0:0              LISTENING
 TCP    0.0.0.0:49164          0.0.0.0:0              LISTENING
 TCP    0.0.0.0:49166          0.0.0.0:0              LISTENING
 TCP    0.0.0.0:49169          0.0.0.0:0              LISTENING
 TCP    0.0.0.0:50300          0.0.0.0:0              LISTENING
 TCP    127.0.0.1:1001         0.0.0.0:0              LISTENING
 TCP    127.0.0.1:5939         0.0.0.0:0              LISTENING
 TCP    127.0.0.1:49155        0.0.0.0:0              LISTENING
 TCP    127.0.0.1:49155        127.0.0.1:49187        ESTABLISHED
 TCP    127.0.0.1:49164        127.0.0.1:49480        ESTABLISHED
 TCP    127.0.0.1:49176        127.0.0.1:49177        ESTABLISHED
 TCP    127.0.0.1:49177        127.0.0.1:49176        ESTABLISHED
 TCP    127.0.0.1:49183        127.0.0.1:49184        ESTABLISHED
 TCP    127.0.0.1:49184        127.0.0.1:49183        ESTABLISHED
 TCP    127.0.0.1:49187        127.0.0.1:49155        ESTABLISHED
 TCP    127.0.0.1:49359        127.0.0.1:49360        ESTABLISHED
 TCP    127.0.0.1:49360        127.0.0.1:49359        ESTABLISHED
 TCP    127.0.0.1:49415        127.0.0.1:49416        ESTABLISHED
 TCP    127.0.0.1:49416        127.0.0.1:49415        ESTABLISHED
 TCP    127.0.0.1:49480        127.0.0.1:49164        ESTABLISHED
 TCP    127.0.0.1:50031        127.0.0.1:50032        ESTABLISHED
 TCP    127.0.0.1:50032        127.0.0.1:50031        ESTABLISHED
 TCP    127.0.0.1:50210        127.0.0.1:50211        ESTABLISHED
 TCP    127.0.0.1:50211        127.0.0.1:50210        ESTABLISHED
 TCP    192.168.1.2:139        0.0.0.0:0              LISTENING
 TCP    [::]:135               [::]:0                 LISTENING
 TCP    [::]:445               [::]:0                 LISTENING
 TCP    [::]:5357              [::]:0                 LISTENING
 TCP    [::]:9937              [::]:0                 LISTENING
 TCP    [::]:12372             [::]:0                 LISTENING
 TCP    [::]:49152             [::]:0                 LISTENING
 TCP    [::]:49153             [::]:0                 LISTENING
 TCP    [::]:49154             [::]:0                 LISTENING
 TCP    [::]:49158             [::]:0                 LISTENING
 TCP    [::]:49166             [::]:0                 LISTENING
 TCP    [::]:49169             [::]:0                 LISTENING
 UDP    0.0.0.0:500            *:*
 UDP    0.0.0.0:3702           *:*
 UDP    0.0.0.0:3702           *:*
 UDP    0.0.0.0:3702           *:*
 UDP    0.0.0.0:3702           *:*
 UDP    0.0.0.0:4500           *:*
 UDP    0.0.0.0:53008          *:*
 UDP    0.0.0.0:58038          *:*
 UDP    0.0.0.0:62329          *:*
 UDP    127.0.0.1:1900         *:*
 UDP    127.0.0.1:58045        *:*
 UDP    192.168.1.2:137        *:*
 UDP    192.168.1.2:138        *:*
 UDP    192.168.1.2:1900       *:*
 UDP    192.168.1.2:5353       *:*
 UDP    192.168.1.2:58044      *:*
 UDP    [::]:500               *:*
 UDP    [::]:3702              *:*
 UDP    [::]:3702              *:*
 UDP    [::]:3702              *:*
 UDP    [::]:3702              *:*
 UDP    [::]:4500              *:*
 UDP    [::]:53009             *:*
 UDP    [::]:58039             *:*
 UDP    [::]:62330             *:*
 UDP    [::1]:1900             *:*
 UDP    [::1]:5353             *:*
 UDP    [::1]:58043            *:*
 UDP    [fe80::d056:5013:4e38:b819%11]:1900  *:*
 UDP    [fe80::d056:5013:4e38:b819%11]:58042  *:*

7) the provider does not block the ports I asked.

but the symptoms are the same, you start the server, accept the agreement and the server turns off. What else can I do I will not attach.

Code:

2019-05-19 15:57:00.479140|ERROR   |VirtualServer |1  |bind failed on 0.0.0.0:9987, :::9987
2019-05-19 15:57:00.481093|INFO    |VirtualServerBase|1  |stopped

Code:

2019-05-19 15:56:58.421523|INFO    |ServerLibPriv |   |TeamSpeak 3 Server 3.7.1 (2019-03-28 07:46:26)
2019-05-19 15:56:58.422500|INFO    |ServerLibPriv |   |SystemInformation: Windows 7 SP1 (7601) x64 (AMD or Intel) Binary: 64bit
2019-05-19 15:56:58.424453|INFO    |DatabaseQuery |   |dbPlugin name:    SQLite3 plugin, Version 3, (c)TeamSpeak Systems GmbH
2019-05-19 15:56:58.424453|INFO    |DatabaseQuery |   |dbPlugin version: 3.11.1
2019-05-19 15:56:58.425429|INFO    |DatabaseQuery |   |checking database integrity (may take a while)
2019-05-19 15:56:58.443007|INFO    |SQL           |   |db_CreateTables() tables created
2019-05-19 15:56:58.472304|WARNING |Accounting    |   |Unable to open licensekey.dat, falling back to limited functionality
2019-05-19 15:56:58.473281|INFO    |Accounting    |   |Licensing Information
2019-05-19 15:56:58.473281|INFO    |Accounting    |   |licensed to       : Anonymous
2019-05-19 15:56:58.473281|INFO    |Accounting    |   |type              : No License
2019-05-19 15:56:58.473281|INFO    |Accounting    |   |starting date     : Tue Jan  1 00:00:00 2019
2019-05-19 15:56:58.473281|INFO    |Accounting    |   |ending date       : Fri Jan 31 00:00:00 2020
2019-05-19 15:56:58.473281|INFO    |Accounting    |   |max virtualservers: 1
2019-05-19 15:56:58.473281|INFO    |Accounting    |   |max slots         : 32
2019-05-19 15:56:59.021132|INFO    |              |   |myTeamSpeak identifier revocation list was downloaded successfully - all related features are activated
2019-05-19 15:57:00.372695|INFO    |              |   |Puzzle precompute time: 1861
2019-05-19 15:57:00.377578|INFO    |FileManager   |   |listening on 0.0.0.0:30033, [::]:30033
2019-05-19 15:57:00.379531|INFO    |VirtualSvrMgr |   |executing monthly interval
2019-05-19 15:57:00.379531|INFO    |VirtualSvrMgr |   |reset virtualserver traffic statistics
2019-05-19 15:57:00.481093|ERROR   |VirtualSvrMgr |   |creating default VirtualServer failed, error: port already in use
2019-05-19 15:57:00.484023|CRITICAL|ServerLibPriv |   |Server() error while starting virtualservers, halted! error: port already in use

P / s for the first time I sent the wrong logs, since I experimented with compatibility but the result was successful
thank

**dante696** · May 20th, 2019, 08:53 AM

I have no clue left what could block the port or tell the server that the port is in use already.

What else you could try is following:

Make a shortcut of the ts3server.exe.
With a right click open the Properties of that shortcut.
In Target add " default_voice_port=9988" (should be like .....\ts3server.exe" default_voice_port=9988).
Delete the ts3server.sqlitedb if there is one and and only when you never had a server running or you will lose all data).
Use the shortcut to start the server.

If that does not work i suggest to rent a server.

Mod Note:
Please show some patience and give time to reply. This is a forum with free support. There is no 7 Day 24/7 support online.
Please be so kind and do not post in other threads where the issue not the same or does not belong to topic.

**Sanche** · May 20th, 2019, 04:14 PM

Originally Posted by dante696

I have no clue left what could block the port or tell the server that the port is in use already.

What else you could try is following:

Make a shortcut of the ts3server.exe.
With a right click open the Properties of that shortcut.
In Target add " default_voice_port=9988" (should be like .....\ts3server.exe" default_voice_port=9988).
Delete the ts3server.sqlitedb if there is one and and only when you never had a server running or you will lose all data).
Use the shortcut to start the server.

If that does not work i suggest to rent a server.

Mod Note:
Please show some patience and give time to reply. This is a forum with free support. There is no 7 Day 24/7 support online.
Please be so kind and do not post in other threads where the issue not the same or does not belong to topic.

did as you described, did not work. = (
I wanted to start my server, as we often play online, and the external Internet in our country is not unlimited (traffic is bought for use), but internal unlimited, and for this we wanted to start the server in order to save, although we live in the 21st century.
I apologize for this not a great understanding, as you brought to the topic with the name - Windows Vista is not supported, I thought that later in this section you can’t exchange information.
If someone from the members of the forum encountered this problem or knows how to defeat it, I will be glad to any tips and instructions. The topic is relevant, the problem is not solved.

**Sanche** · May 21st, 2019, 10:18 AM

Hello everyone, dear dante696, I conducted an experiment - I took several laptops with different operating systems from friends and the result is that on the windows 7 32bit and 64bit operating system errors are the same as mine that I sent logs, but on windows 10 server teamspeak 3 (3.7.1) started without any problems. and I had two assumptions:
1) I think that something in the program itself is not fully spelled out or not finalized for work on windows 7
2) or windows 7 support has been discontinued (but I did not find this confirmation)
The bottom line is that on Windows 7 32bit and 64bit it was not possible to start the server, but on Windows 10 it works without problems. dante696 if you have the opportunity to talk with developers / programmers about this problem
Thanks for attention

**dante696** · May 21st, 2019, 11:02 AM

The server works fine on Windows 7 (32 & 64 bit). Windows 7is still supported and has not been discontinued yet.

Click image for larger version.

Name: win 7 works.png
Views: 180
Size: 94.6 KB
ID: 17873

I still think something on your system does block the ports.

Forum

Notice to all users

Thread: Creating default VirtualServer failed, error: port already in use

Thread Tools

Rate This Thread

Display

Creating default VirtualServer failed, error: port already in use

Thread Information

Users Browsing this Thread

Similar Threads

VirtualServer(1) failed to start, error: invalid channelID

loading VirtualServer(1) failed to start, error: invalid group ID

Posting Permissions