Have any of you admins ran into this one yet? Seems to be a bug that after we went ****in round with RTR maps and BF original maps with a server manager, somewhere along the lines it hosed our configs. We are now running bf as a service and at map change it kicks a full server and tells everyone that the server is full and won't allow anyone back in until the new map is fully loaded. We went through the event viewer and the service isn't crashing nor is the server, only the players get kicked. We reinstalled everything possible except of coarse our OS. We are of coarse looking for another way out, but it seems fdisk and format is our only hope for this shitty bug. Anyone delt with this before?
which server manager are you using? Does the server manager log file have anything in it...High ping kick set too low? does it happen on EVERY map change?
We have actually fixed the problem. It seems to be a problem between Desert Combat maps and BF original maps. DC seems to may change the config file when the BF .exe is executed. DC uses the BF original .exe even if they are in separate directories. Thus why the server didn't crash nor did the service restart. The program and the server still registers that the server has people playing in it, which in fact they do not. Where the error "Cannot connect server is full" comes from we haven't the slightest idea. We took DC completely out of the machine and the problem was fixed.
interesting....I'm gonna have to play with this one...I was hosting Desert Combat while my dedicated server was down with no problem...I'll have to run DC tonight on it and see if I can reproduce this.