Issue with Registered Channels

[Cometcom1]

Currently testing the software.

Using: 2.0.18.31 Win32 - running on Windows 2000 server with latest SP.

Creating channels with the Registered flag set.

I do remember to restart the server either from the webinterface with a change of server params, or through the Exit function of the server taskbar icon.

But somehow not all of the registered channels survive.

Havent been able to determine a system in which channels survive or not.

Issue # 1:

However, I did find that a windows reboot does the most damage to the database/channel lists.

Even though I did not change anything in the channels or the server that had to be saved. i.e. I had a setups working, and shutting down/restarting the TS server did nothing to corrupt the channel list. But after I restarted the Windows server, I lost more than half the registered channels, including the default channel.

The only way I could then get the server back was joining one of the existing channels at logon, and then create a default channel. If I tried to logon with no channel preference, the default was not found and I was left in a limbo state where I was unable to perform any commands.

Issue #2:

I have also tried to create massive amounts of registered channels, then restarting the TS server - but I found that I could only maintain approximately 45 channels.

However there was a difference in how I restarted and what channels survived.

If I restarted through the Web administration interface, I could maintain channels without problems. I.e. the exe file was not unloaded from Windows memory.

If I restarted through unload/Exit of the server and reloading the exe file, I was not allowed to have much more than 45 channels.

---------

Currently I am trying to work around these quirks by configuring several servers, each having no more than 45 channels.

---------

Note:
I use several differently named registered "master" channels with subchannels. Each registered channel has 4 subchannels. My subchannels are named the same for each "master" channel.

i.e.
- Channel 1
--- Sub1
--- Sub2
--- Sub3
--- Sub4
- Channel 2
--- Sub1
--- Sub2
--- Sub3
--- Sub4

------------

So any ideas what might cause this ?

Anyone else noticing this on the windows build ?

[Cometcom1]

Right, found out that multiple servers running on different ports from same executable load, will fix it partly.

I configured 6 TS servers. All 6 TS server start up no problem.

TSServer1 = 46 channel (10 master channels, of which 9 have 4 sub channels)
TSServer2 = 46 channel (10 master channels, of which 9 have 4 sub channels)
TSServer3 = 46 channel (10 master channels, of which 9 have 4 sub channels)
TSServer4 = 26 channel (6 master channels, of which 5 have 4 sub channels
TSServer5 = 1 channel
TSServer6 = 1 channel

Restarting the servers through the web interface seem to work quite allright.

Now, I exited the server through the task bar. I even monitored the active processes to wait until the Teamspeak application was unloaded. - This can take quite some time.

After restarting the TS Server - I was missing 7 subchannels in TSServer4, however all other TSServers where running just fine.

I haven't tried to restart the server yet, I'm a little afraid it would remove more channels.

[stuart124]

i dont now my channle does the same

[Cometcom1]

Please see:

http://www.teamspeak.org/forums/showthread.php?s=&threadid=3022

For an explanation.