Jump to content
Sign in to follow this  
$able

BattlEye problems

Recommended Posts

Anyone explain this please.....we will call the player=player

player kicked off by BattlEye: Corrupted Memory #2

not seen that in the logs before.... thnx   crazy_o.gif

i got that once myself never saw it before or after ...

no idea what it was ...

saw some in like 2 months ago too

Share this post


Link to post
Share on other sites

"Corrupted Memory" is what it says. It can be caused by anything - e.g. corrupted RAM, viruses, and also hacks of course.

Share this post


Link to post
Share on other sites

What is the difference between #1 and #2. I noticed #1 happened a lot with people playing locally? But #2 seems to be a rare one.

We (GOL Clan) also get a few people getting client not responding while joining, both members and public players. The server is high spec (Quad core, 4GB RAM etc, Fast down/up) and the FPS of the server remains high during these moments.

Do they get client not responding because the game is loading longer than the 30 seconds you allow? Since the game is loading, it doesn't have time to give BattleEye the ok that everything is fine, making BattleEye assume something is fishy.

I think the 30 seconds time out should be a config option in ArmA, so servers that run heavy missions can increase the limit. What harm would it do increasing the limit? It will just take longer for the check to fail if there is still no response, but gives players time to connect and get the game going before BattleEye kicks in.

I appreciate your active support on the Forum here.

Share this post


Link to post
Share on other sites
What is the difference between #1 and #2. I noticed #1 happened a lot with people playing locally? But #2 seems to be a rare one.

Different memory ranges.

Regarding "Client not responding", read my explanations a few posts above.

Share this post


Link to post
Share on other sites

Not sure if this is a problem or not, but when I click MULTPLAYER in ArmA the server list window comes up and I get an error stating

<table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">No entry 'bin\config.bin/RscDisplayMultiplayer.showNoBattlEye'.

How can I get rid of this error?

Share this post


Link to post
Share on other sites
Not sure if this is a problem or not, but when I click MULTPLAYER in ArmA the server list window comes up and I get an error stating

<table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">No entry 'bin\config.bin/RscDisplayMultiplayer.showNoBattlEye'.

How can I get rid of this error?

Maybe try to reinstall game/patch.

Share this post


Link to post
Share on other sites

When the Master Server going to be back up?

it has been down for almost 24 hours now.

Quote[/b] ]

23:29:43 BattlEye Server: Could not connect to BE Master

23:29:43 BattlEye Server: Update attempt failed

Share this post


Link to post
Share on other sites
When the Master Server going to be back up?

it has been down for almost 24 hours now.

Quote[/b] ]

23:29:43 BattlEye Server: Could not connect to BE Master

23:29:43 BattlEye Server: Update attempt failed

Should be back online now.

Share this post


Link to post
Share on other sites

I have a problem running BattleEye on a Windows Server 2008 Enterprise 64Bit (8GB RAM).

In server.cfg I set BattlEye=1;.

When I start the server the console shows

<table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">Dezidierten Host erstellt.

BattlEye initialization failed

I have copied the files BEServer.dll and BEClient.dll from www.battleeye.com to the folder C:\Users\[username]\AppData\Local\ArmA\BattlEye.

This is the path where server_console.log and the arma_server.RPT are stored.

Is there something I have forgotten?

Edit: After starting the server (with 'initialization failed' message) the BEServer.dll is deleted.

Share this post


Link to post
Share on other sites
I have a problem running BattleEye on a Windows Server 2008 Enterprise 64Bit (8GB RAM).

In server.cfg I set BattlEye=1;.

When I start the server the console shows

<table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">Dezidierten Host erstellt.

BattlEye initialization failed

I have copied the files BEServer.dll and BEClient.dll from www.battleeye.com to the folder C:\Users\[username]\AppData\Local\ArmA\BattlEye.

This is the path where server_console.log and the arma_server.RPT are stored.

Is there something I have forgotten?

Edit: After starting the server (with 'initialization failed' message) the BEServer.dll is deleted.

Make sure BE is installed in the ArmA install folder as well.

Otherwise ArmA thinks you uninstalled BE and won't try to load it.

Share this post


Link to post
Share on other sites

Thanks. That was the problem. I have copied the BattlEye folder in the ArmA folder and now it runs.

Share this post


Link to post
Share on other sites

Why would i get constant kicks from one server and not others mad_o.gif ive tested with, without addons to no avail.

My connection is sound Australian pings of 10+.

Share this post


Link to post
Share on other sites
Why would i get constant kicks from one server and not others mad_o.gif ive tested with, without addons to no avail.

My connection is sound Australian pings of 10+.

That is related to ArmA's netcode and should be fixed in the next version. Read here: http://www.flashpoint1985.com/cgi-bin....=74051.

Share this post


Link to post
Share on other sites

BattlEye server has been down for days now, when is it going to be fixed?

Quote[/b] ]11:22:02 BattlEye Server: Could not connect to BE Master

11:22:02 BattlEye Server: Update attempt failed

11:24:00 BattlEye Server: Could not connect to BE Master

11:24:00 BattlEye Server: Update attempt failed

11:25:58 BattlEye Server: Could not connect to BE Master

11:25:58 BattlEye Server: Update attempt failed

11:27:56 BattlEye Server: Could not connect to BE Master

11:27:56 BattlEye Server: Update attempt failed

11:29:54 BattlEye Server: Could not connect to BE Master

11:29:54 BattlEye Server: Update attempt failed

11:31:52 BattlEye Server: Could not connect to BE Master

11:31:52 BattlEye Server: Update attempt failed

Share this post


Link to post
Share on other sites

I am seeing this as well on my server. Thanks for posting that Aussie Dave. Now I know its not isolated to my servers.

Share this post


Link to post
Share on other sites

Seeing that same error over and over in my server for the past couple of days.

Share this post


Link to post
Share on other sites
Seeing that same error over and over in my server for the past couple of days.

Fixed now.

Share this post


Link to post
Share on other sites

Bastian, as a short Feedback on the new 1.16b included version:

BE is now simply amazing. Not one random kick anymore i ever saw at all, if the clients PC was not suddenly hanging or crashing (the guys later confirmed it).

Even for persons in our community from like Russia which tend to have rather "problematic" connections are now "random-kick" free.

So to say it with some german words:

"Was lange währt wird endlich gut!"

(is a idiom and in EN like: "What lasts long already, is finally going to be good")

Share this post


Link to post
Share on other sites

Thank you, but it really should have been like that from the beginning. Unfortunately though, as you know, my hands were tied and I couldn't do anything about those kicks prior to 1.16.

Anyway, good to hear positive feedback after all. Besides, I will post some new updates soon.

Share this post


Link to post
Share on other sites

Hi bastian, i have my whole console Window today full with those:

13:03:00 BattlEye Server: Update successfully completed. Restarting...
13:03:01 BattlEye Server: Initialized
13:04:35 BattlEye Server: Update successfully completed. Restarting...
13:04:35 BattlEye Server: Initialized
13:06:09 BattlEye Server: Update successfully completed. Restarting...
13:06:09 BattlEye Server: Initialized
13:07:43 BattlEye Server: Update successfully completed. Restarting...
13:07:43 BattlEye Server: Initialized
13:09:17 BattlEye Server: Update successfully completed. Restarting...
13:09:17 BattlEye Server: Initialized
13:10:51 BattlEye Server: Update successfully completed. Restarting...
13:10:51 BattlEye Server: Initialized
13:12:25 BattlEye Server: Update successfully completed. Restarting...
13:12:25 BattlEye Server: Initialized
13:13:59 BattlEye Server: Update successfully completed. Restarting...
13:13:59 BattlEye Server: Initialized
13:15:33 BattlEye Server: Update successfully completed. Restarting...
13:15:33 BattlEye Server: Initialized
13:17:08 BattlEye Server: Update successfully completed. Restarting...
13:17:08 BattlEye Server: Initialized
13:18:42 BattlEye Server: Update successfully completed. Restarting...
13:18:42 BattlEye Server: Initialized
13:20:16 BattlEye Server: Update successfully completed. Restarting...
13:20:16 BattlEye Server: Initialized
13:21:53 BattlEye Server: Update successfully completed. Restarting...
13:21:53 BattlEye Server: Initialized
13:23:28 BattlEye Server: Update successfully completed. Restarting...
13:23:28 BattlEye Server: Initialized
13:25:05 BattlEye Server: Update successfully completed. Restarting...
13:25:05 BattlEye Server: Initialized
13:26:39 BattlEye Server: Update successfully completed. Restarting...
13:26:39 BattlEye Server: Initialized
13:28:14 BattlEye Server: Update successfully completed. Restarting...
13:28:14 BattlEye Server: Initialized
13:29:48 BattlEye Server: Update successfully completed. Restarting...
13:29:48 BattlEye Server: Initialized
13:31:22 BattlEye Server: Update successfully completed. Restarting...
13:31:22 BattlEye Server: Initialized
13:32:59 BattlEye Server: Update successfully completed. Restarting...
13:32:59 BattlEye Server: Initialized
13:34:34 BattlEye Server: Update successfully completed. Restarting...
13:34:34 BattlEye Server: Initialized
13:36:08 BattlEye Server: Update successfully completed. Restarting...
13:36:08 BattlEye Server: Initialized
13:37:42 BattlEye Server: Update successfully completed. Restarting...
13:37:42 BattlEye Server: Initialized
13:39:17 BattlEye Server: Update successfully completed. Restarting...
13:39:17 BattlEye Server: Initialized
13:40:53 BattlEye Server: Update successfully completed. Restarting...
13:40:53 BattlEye Server: Initialized

Any Advice what that could be?

Share this post


Link to post
Share on other sites

Hm, this is very weird. It seems the ArmA server fails to finish the update process. I suppose it cannot rename the .new file and therefore permanently loads the old version again.

Do you run 2 or more servers from the same installation? If you do, please use the -bepath=[folder/path] command line option to use different BE locations for each instance (relative paths are relative to the application data folder, see below).

Please check if there is a .new file in the server's application data folder (default: "C:\Documents and Settings\[user Name]\Local Settings\Application Data\ArmA\BattlEye"). Anyway, the .new file is probably incomplete when you check, as your server constantly tries to update, so you should update manually here: http://www.battleye.com/download.html. Keep in mind that this doesn't really fix your problem though, as it will come up again on the next update.

Share this post


Link to post
Share on other sites

Yes maybe a permission error (but it worked always before)... there is indeed this .new file in the folder.

No, currently only one server is running. Will see if i can fix it with a different permission on the BE folder.

Thanks anyway.

Share this post


Link to post
Share on other sites

Make sure you only change permissions on the appdata BE folder (the one in your ArmA install folder is irrelevant here).

If there is a .new file, the ArmA server process at least has write access though, which should always be the case for appdata anyway (hence the files are stored/loaded from there).

Maybe for some reason the BEServer.dll is locked or write-protected and cannot be deleted.

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.
Sign in to follow this  

×