For reference, this problem occurred because the customer's uploaded files for the mod included a "players" folder (which is normally auto-generated by the CoD2 server), which in turn contained an "active.txt" that set the profile to "tcadmin", as opposed to the standard value of "default". When it starts up, the CoD2 server loads the config_mp.txt file saved to the active profile folder while checking for hardware changes, throwing up a dialog box if it finds differences. Our system is set up to delete "players/default/config_mp.cfg" during its repair operations in order to ensure that this check can't fail, but it does not look for "players/tcadmin/config_mp.cfg", so the dialog box was appearing every time the server tried to start, preventing it from running.
The fix was to change the "players/active.txt" file to contain "default" instead of "tcadmin". The server then started normally.
This was an artifact of transplanting an entire mod's folder and files from an existing server on another machine with a custom profile defined. We've never seen this before because most customers upload their mods from standard distributions.
Users browsing this forum: No registered users and 0 guests
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot post attachments in this forum