COD:WW Dedicated Server stopped working

[Sprite]

I had the server up and running. The server crashed a few random times over a few weeks and then just stopped working. I thought it might be my map rotation causing the crashes.... it was a mixed rotation. So, I double checked server config/map rotation and no issue's, so I uploaded one from a server I KNOW works with only a TDM rotation and still no go.

Checked my target on the desktop shortcut which originally was

C:\Call_of_Duty-World_at_War\CoDWaWmp.exe +set dedicated 2
+set sv_punkbuster "1" +exec server.cfg +map_rotate

Tried adding in the ip stuff, etc and still no go.....

C:\Call_of_Duty-World_at_War\CoDWaWmp.exe +set dedicated 2
+set net_ip 72.37.224.166 +set net_port 28960 +set sv_maxclients 32
+set sv_punkbuster "1" +exec server.cfg +map_rotate

I use FireDaemon to start all servers on this box.... the startup parameters seem to be ok

+set dedicated 2 +set net_ip 72.37.224.166 +set net_port 28960 +set
sv_maxclients 32 +set sv_punkbuster "1" +exec server.cfg
+map_rotate

Anyone have any idea's?

Should I post the server config? The one I ended up using is much more simplified then what I was originally using (the one bulletworm posted for the beta) and it does work on a completely different box, just not this one.

I even went so far as to disable the crashed server and install a new server with new ip, etc and still no go. What am I missing or doing wrong? Help.

[OldDog]

What do you mean by "stopped working"? Are there error messages? Or, can you just not connect to the server? Anything in the FireDaemon log? Or, the event logs? I take it that you can get to the server's console since you had access to the startup CL. Other things running ok on the server? What else do you have running?

Unless you made changes just prior the server "stopped working", I don't think posting your config will be of any benefit yet.

[Sprite]

What do you mean by "stopped working"? Are there error messages? Or, can you just not connect to the server? Anything in the FireDaemon log? Or, the event logs? I take it that you can get to the server's console since you had access to the startup CL. Other things running ok on the server? What else do you have running?

Unless you made changes just prior the server "stopped working", I don't think posting your config will be of any benefit yet.

By "stopped working" I mean it will no longer start up. FireDaemon says it's running but when you load game it's listing as the ip with no ping.

I checked all of the logs, nothing unusual.... both server logs and Fire Daemon.

Only thing that happened was Windows updated itself and restarted the server.

Other games running on server are still ok (cod4 server's, swbf2, ts, etc....).

When I click the shortcut on desktop it will start the COD:WW server, show's in the server listing and you can join so there's no reason why it shouldn't be starting when I launch with Fire Daemon as before. I'm assuming since it starts with the shortcut the problem lays somewhere with either FireDaemon (which all looks right) or something to do with the windows update.

Any idea's on what else I should check with FireDaemon? or what else could be wrong?

[SiCDude4Him]

I run the same setup. What I found to stop the crashes was installing the latest DX Runtimes from Microsoft. No more crashes. It is also useful if your console game will not start from Fire Daemon.

http://www.microsoft.com/downloads/details.aspx?familyid=2da43d38-db71-4c1b-bc6a-9b6652cd92a3&displaylang=en

[OldDog]

By "stopped working" I mean it will no longer start up. FireDaemon says it's running but when you load game it's listing as the ip with no ping.

I checked all of the logs, nothing unusual.... both server logs and Fire Daemon.

Only thing that happened was Windows updated itself and restarted the server.

Other games running on server are still ok (cod4 server's, swbf2, ts, etc....).

When I click the shortcut on desktop it will start the COD:WW server, show's in the server listing and you can join so there's no reason why it shouldn't be starting when I launch with Fire Daemon as before. I'm assuming since it starts with the shortcut the problem lays somewhere with either FireDaemon (which all looks right) or something to do with the windows update.

Any idea's on what else I should check with FireDaemon? or what else could be wrong?
So, the game starts ok without FireDaemon? If so, I'd try first, what SiCDude4Him recommended, and I'd also blow away the FireDaemon setup and re-do it. Are you running Trinity or the standard FireDaemon. A new version just came out, and, if you have the auto update turned on, it may have screwed up your profile. This is Trinity only, though.

[Sprite]

So, the game starts ok without FireDaemon? If so, I'd try first, what SiCDude4Him recommended, and I'd also blow away the FireDaemon setup and re-do it. Are you running Trinity or the standard FireDaemon. A new version just came out, and, if you have the auto update turned on, it may have screwed up your profile. This is Trinity only, though.

Yep, the server starts fine with the desktop shortcut, just not in FireDaemon.

I did the directx websetup and deleted old instance in FireDaemon Pro 1.9GA and created a new one and still no go. The server itself is Windows Server 2003 Standard. I'm completely baffled on this one, because it did initially work, as did the beta.

[OldDog]

Yep, the server starts fine with the desktop shortcut, just not in FireDaemon.

I did the directx websetup and deleted old instance in FireDaemon Pro 1.9GA and created a new one and still no go. The server itself is Windows Server 2003 Standard. I'm completely baffled on this one, because it did initially work, as did the beta.
Yas, I'm pretty baffled, too. I'm running Trinity on Win2K3, and there's been no problem. I had CoD4 running with 1.9GA, also with no problem. Sounds like it might be a call, or e-mail, to FireDaemon. They're pretty good guys, I've found (in the past, anyway).

[SiCDude4Him]

Could you please post your command line from FireDaemon? I use the same version and have no problems.

[Sprite]

Could you please post your command line from FireDaemon? I use the same version and have no problems.

+set dedicated 2 +set net_ip 72.37.224.166 +set net_port 28960 +set
sv_maxclients 32 +set sv_punkbuster "1" +exec server.cfg
+map_rotate

[SiCDude4Him]

Well, not sure if it will help but here's my Fire Daemon setup for CoDWW. You command line looks good so maybe double check your daemon parameters?

http://i57.photobucket.com/albums/g226/dude4him/firedaemon_codww.jpg

[Sprite]

Maybe it's because I don't have the +set ui_maxclients 32 along with the +set sv_maxclients 32 in my parameters. That looks like the only difference between what you posted and my startup parameters. I'll give it a try and post back, but it worked fine for weeks before without that command. Still you never know. I'll try it.

[SiCDude4Him]

That should not matter. 32 slots are hard coded into the game and if you want more than the default 32 slots this is the command you place in your command line. If you have updated your DX runtimes and double checked your startup and made sure the executable & working directory are correct I have to say I'm at a loss too. It's not really hard but sure can be if something like this comes up.

[Sprite]

That should not matter. 32 slots are hard coded into the game and if you want more than the default 32 slots this is the command you place in your command line. If you have updated your DX runtimes and double checked your startup and made sure the executable & working directory are correct I have to say I'm at a loss too. It's not really hard but sure can be if something like this comes up.

I'll post if I ever do figure it out. I'm think I'm going to try a fresh install again after I uninstall the old stuff and hope that works. I had tried to do a new install under a different folder name etc, but it didn't work..... so I'm hoping if I get rid of everything and start from scratch it will work again. That's the real kicker here..... it DID work and for several weeks. Oh well I will deal with that tomorrow. Thanks for all your help so far guys, it's really appreciatied.

Merry Christmas everyone!!!

[w4jchosen]

I would be very interested to hear the outcome of this as I am having the same problem.

Installed instance on Firedaemon. It works fine if you just hit the "run" button, but I have it set up to do a restart every morning and it always generates an error. It shows running in the Firedaemon panel, but the server itself will show offline. You have to stop and restart it and it is fine, but this kind of defeats the purpose of doing an auto restart.