BF2CC & Windows 2008

[mattb37]

Hello,

 

I have just switched back to tcadmin after a long time away from it and I am surprised to see I cannot get BF2 to start. I am using one of the BF2CC daemon configs from the forums to launch bf2cc and then try to get the server to auto start from the daemon. The server attempts to start but then immediately stops the process with an application error reading along the lines of "The process is not in a stopped state and cannot be started".

 

I have tried a full reboot of my server launching the bf2ccd from tcadmin manually with no joy. The daemon launches fine it is just a problem getting the bf2 dedicated process to run. The error message I get only comes up when I start the daemon with tcadmin and try to manually launch the server from the daemon.

 

The BF2 configs are in full working order and can be launched perfectly fine manually from within Windows.

 

I am running Windows Server 2008 R2 Standard. Could the problem I am getting with this be related to any permissions?

 

I have set the working dir to the daemon dir inside my bf2 servers and the game root to the bf2 dir, should these be set differently?

 

Any help would be much appreciated,

Matt.

[mattb37]

I have looked at various error logs and a trend of permission errors seems to be occurring with the event log showing the bf2 server process terminating due to "an illegal memory operation".

 

Can I configure TCadmin to run services as a specific user or does it run services from the logged on user by default? I am pretty sure this is a permission problem as the whole process works fine until TC admin is used to start the process.

 

Any suggestions would be great,

 

Matt.

[bullfrog3459]

Matt,

 

The only "permission" setup is from Dimitri:

http://clientforums.tcadmin.com/showthread.php?t=6428

 

i would have to look, but my bf2cc and bf2142cc servers run fine with actually non-ranked games running on them, so could be possibly a setup issue on your end maybe? There could be something i also might be looking over.

[ECF]

This usually fixes the memory error.

 

1. Locate the TCAdmin service which starts tthe CC in the windows services list.

2. Right click on it and choose "properties".

3. Click the Logon Tab.

4. Then check the radio button marked "This Account".

5. Fill in the administrator username and password and apply.

6. Start the service using the new logon info, it should start properly.

7. Go back to the Logon properties for that service and change it back to local system.

 

 

The program should then start properly from that point forward. Not sure why CC needs to be started as admin first, but this is a known issue since the CC came out.

[dimitrifrom31]

This usually fixes the memory error.

 

1. Locate the TCAdmin service which starts tthe CC in the windows services list.

2. Right click on it and choose "properties".

3. Click the Logon Tab.

4. Then check the radio button marked "This Account".

5. Fill in the administrator username and password and apply.

6. Start the service using the new logon info, it should start properly.

7. Go back to the Logon properties for that service and change it back to local system.

 

 

The program should then start properly from that point forward. Not sure why CC needs to be started as admin first, but this is a known issue since the CC came out.

 

not with win2003 at least not for me. my servers are setup automatically using the billing API and CE and I never had problems. They are started under an user account (not system) but without admin privileges.

[ECF]

It does not happen on every machine. It seems to be related to specific RAM chips or motherboards for some reason. We never looked further into it after we found the above workaround for it.

[mattb37]

Thanks for the replies.

 

Seems to work fine when I boot the CC with the administrator account entered into it in the service properties but fails the other times. I think I may have loaded all my files onto this machine from the admin account so it could be owner permissions that are the problem here.

 

It is not the most secure but works for me. I am not renting this machine out and only using it for my clan so it will do for now. I will load my next 2008 machine from a non-admin account in hope it doesn't have the same problems.

 

Thanks again for the suggestions,

 

Matt.