Sup@hKing

I must say im sadden by some of the reactions to Nux's decition to take down the free4all Bec service. IMO this shows that this once great community is about to shift into the realm of children. Remember the fun times we had, free of microtransactions. Cherish and lock away this memory for posterity.

Hey ballou I might be able to answer this, What comes to mind is that in Admins.xml the name of admin mod3 might be happy.

Make sure you have all prerequisite requirements.

You add the difficulty settings to your server.armaprofile

Task kill ends the process immediately with no regards to what the program does. #shutdown gracefully ends the process. @ Inch Im curious as to what server enviroment you are running, virual host or root server? Are you using any custom tools to start up Arma and BEC as services?

@ ltiisidii Sent issue on to developer for debugging.

@Shona You should always use the Bec.lib that follows the latest Bec version, not doing this could cause incompability if there has been changes done. The psutil has been updated in latest version (Bec 1.55) from 0.3.0 to 1.0.1

@Watarimono Glad you figured it out :) @cortez471 Can you try and see if you also have any spaces in your BEserver.cfg on the Rcon line. @ballou #390 Maybe BattlEye on the server is trying to update, if there is a BattlEye update, BattlEye will not update while there are players on the server, it will try and update when the server is empty. Maby this has changed but as far as I know this was how BattlEye behaved in Arma2.

@ ltiisidii Try to manually update your BE client & server files from Battleye.com Also try to compare hash; MD5 or SHA1 to check that your BEC download arent corrupted. Maby also try to get Microsoft Visual C++ 2008 x86 Redistributable Package. Though 2010 should be backwards compatible.

@cortez471 @Watarimono Only thing I can think is that this is not BEC related, it could be something with your startup parameters. Check out post #55 trough #58 and see if you get any closer to a solution. If error persist, post here or email us (support@ibattle.org) your parameters and configs so we can try to reproduce it for future reference.

I suggest you try to log on with BERcon and se if u can connect, then try and get BEC started up from cmd and look for errors. The install and configure guide have a how-to for it.

BEC is a server application not a Rcon. From http://ibattle.org/; All you need to make it connect is in the [bec] block of the Config.cfg

When updating always copy the Bec.exe and Bec.lib files.

Your bepath in your .bat script is commented out, remove the :: and check the path.

From changelog in v1.47.1. When the --dsc switch is enabled, BEC will ignore all config values except the ones in the [bec] block, unless the IP is set to 127.0.0.1, meaning the BEC is running on the server. As far as i know this is done in case two or more BEC's are connected to the same server with different config values, witch would cause problems. If you run BEC remotely, it will mostly have logging capabilities. The best way is to get BEC installed on your server.