Windows 2003 Server

[GASCRLModernAge]

...or .net Server depending on how much you have heard about it.

Basically I upgraded a Windows 2000 Server, running a single TeamSpeak 2.0 server to Windows 2003 Server RC2 and TeamSpeak blows up after running for a minute. It of course provides a nice "greek" explanation. Will the product run on this platform yet? At the beginning of the upgrade, it did not indicate there would be a problem with TeamSpeak.

If I reinstall, will I lose my registration database?

During the minute or so it does run, I can connect to it remotely.

Any assistance will be greatly appreciated. We love your product and will continue to use it...hope the SB issues get stomped out but out of about 30 users, I have had very minimal problems out of my users.

[GASCRLModernAge]

oops...forgot to mention I can provide that "greek" output for a developer and/or run the program in debug mode if necessary.

[GASCRLModernAge]

Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 2/15/2003
Time: 8:47:33 AM
User: N/A
Computer: MA-EXCHCONF
Description:
Faulting application server_windows.exe, version 2.0.18.234, faulting module kernel32.dll, version 5.2.3718.0, fault address 0x000338ca.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 73 65 72 ure ser
0018: 76 65 72 5f 77 69 6e 64 ver_wind
0020: 6f 77 73 2e 65 78 65 20 ows.exe
0028: 32 2e 30 2e 31 38 2e 32 2.0.18.2
0030: 33 34 20 69 6e 20 6b 65 34 in ke
0038: 72 6e 65 6c 33 32 2e 64 rnel32.d
0040: 6c 6c 20 35 2e 32 2e 33 ll 5.2.3
0048: 37 31 38 2e 30 20 61 74 718.0 at
0050: 20 6f 66 66 73 65 74 20 offset
0058: 30 30 30 33 33 38 63 61 000338ca

[nwerensteijn]

Well, nope it does not realy help

The kernel32.dll is the interface to windows. it seems there is a bug in it in windows2003. Keep in mind that platform is not released

This is not our issue, but microsofts. (they should provide backward compatibility)

[GASCRLModernAge]

There is an application compatibility program available from Microsoft for developers to test their application compatibility with Windows Server 2003. They are not obligated to provide backwards compatibility...software providers should consider it a "gift" when it does work that way.

I code as well and it is just the way the ball bounces sometimes.

[PsiNyde]

I am also running Windows 2003 Server, and I just got TS2Server installed. It's been running for about 10 minutes now with no problems. When I had it running on Windows 2000 Adv Server, I had nothing but problems . But all seems to be ok for me at least on .NET Server. Where did you get your copy of .NET Server? If you got it from iMesh, Kazaa, or something like that, then that might be the problem...I actually registered with MS as a beta tester, and am running a licensed copy of .NET Server. If that is also the case with you, I don't know what to say, that really sucks because like I said, mine works.
I hope that my TS2 continues to work...I will provide an update by monday [I hope it's all good].

PEACE

[disaacks]

I also have it running on .NET Server Beta 2. It does crash now and then, but I have firedaemon running so it restarts.

[Cstar_maxim]

I have been running WinServer2003RC2 for a while and have had no problems with TS. I did not do an upgrade I did a fresh install to a dual boot, so I had to download and install DX9.0. I am not sure that DX8x will work with WinServer2003 but if you don't have DX9 thats where I would start if I were you.

I also have it from MS (part of the RC program)

[GASCRLModernAge]

Yes...I'm a registered Beta tester for the Win2003Server, Office11, Exchange2003 and SMS products and I did forget to mention that these failures have been happening on the Enterprise Edition of the server (formerly 'Advanced Server') so that likely explains your successes and my failure.

[PsiNyde]

yeah, i'm runnin EE also...so still go figure. but i would like to check out the others...thanks for mentioning them.
anywho, it did crash once [i wouldn't really call it a crash], but I should also tell a little more about the server:

733/384M
Win2K3 RC2
Counterstrike Server v1.5
PsychoStats v1.9.1
IIS Running [obviously]

with the CS server running, I had something like 11 peeps playing, visitors to the stats site, and a pair of members logged into TS2. The program only stopped responding when i tried to shut down the server without ending all the the stuff that was running [peeps were still conneected]. so i think that was the prob i had...but only once.

i'm not going to preach about "how did you install it" etc., etc. because if you are beta testing all that stuff [ESPECIALLY Exchange - urgh!] then you must know what you are doing. all i can offer up is: DON'T overlook the obvious or seemingly insignificant - it's usually the problem. that's from my own experiences...hope you get it working soon!

PEACE

[GASCRLModernAge]

the other thing that likely had an effect on the situation is my install was an upgrade to a Win2K server though I did uninstall and reinstall TeamSpeak after the OS upgrade...fortunately Exchange is not running on this particular machine.

[Rizo]

A few thinks to note to get your copy of Teamspeak 2.0 working with Windows Server 2003: First, you have to let it interact with the desktop - if you start it as a service you need to me logged on and have the 'interact with desktop" check box check in the service properties. Second, if you do remote desktop access of the server expect the Teamspeak application to crash after a couple of switches from local video to remote video - this is the same issue as with running in XP and doing remote desktop.

Given the limitations, I have only had sucess running it as an application after I have logged on to the system. Running it as a service seems to be useless since it will try to start before you log in and when it cannot interact with the desktop it crashes shortly there after.

I am hoping that the fix implemented for XP' remote desktop issue (and to be included in the next release) will also fix the problem with remote desktop in 2003 and allow it to start without having to interact with the desktop.

Hope this helps.

Rizo

[Rizo]

RC2 has fixed all the issues that I had with Windows Server 2003. You can now start it as a service using SRVANY.EXE and you don't have to set it to interact with the desktop. I have my set to start automaticly and it does not crash when I switch desktops or Logon to another account.

If you are running Server 2003, run and get the update - it works much better now

Rizo