FiveBoroPrez

Update #5: We have discovered that deleting your "@DayZ" folder on the client side (aka YOUR PC) has corrected the problem permanently. Instructions: Step 1. - Go to your "C:\Program Files (x86)\Steam\SteamApps\common\arma 2 operation arrowhead" Step 2. - Delete the "@DayZ" folder from your hard drive Step 3. - Remove custom run parameters from your DayZ Commander settings Step 4. - Connect to game server you wish to play on Step 5. - Smile and say thank you to everyone that contributed to this thread Note: If I stumble across more issues related to this problem I will update this thread as soon as I can.

Update #4: Players are reporting that completely uninstalling Arma 2, Arma 2 OA, DayZ, and Epoch, then re-installing everything has allowed them to connect to the server. Hence, correcting the issue of being kicked from server by BattleEye for "instance_11_chernarus" error. I will continually update this thread as we debug this problem.

Update #3: New players are reporting that they have deleted their custom run parameters for other Epoch map types. This allows them to successfully connect to my server. Server owners/admins need to communicate to their players to delete ANY run parameters they may be using to connect to other servers. Stay tuned for additional updates as I isolate this problem.

Update #2: Players trying to connect to my server are still being kicked by BattleEye. Here are some tips to try: 1. Update your BattleEye (delete your old BattleEye folder first, then re-install) 2. Re-install Arma 2 within DayZ Commander 3. Re-install DayZ within DayZ Commander 4. Re-install Epoch within DayZ Commander 5. Clear your player profiles in your Arma 2 directory (my documents\Arma2..) 6. Make sure you DO NOT have any Run Parameters for Arma2 in your DayZ commander settings or Steam settings 7. Try reconnecting to the server that has been causing you trouble and verify if the problem still persists or has been corrected. if not, proceed to step #8.. 8. Try to connect to another DayZ server that you've been able to successfully connect to so it may update your BE files 9. Again, try to connect to server you're having trouble with. 10.If you still have problems try steps 1-9 again! (You may have missed something) 11. If you still can not successfully connect to the server ask "what would Jesus do?" J/K Just keep researching the problem. Some people are instantly kicked while others are successful. Don't ask me why. Heck if I know the reason. I didn't write the server codes for Arma 2. It stinks! Please keep this post updated if you found an easier way to fix this problem without having to follow my 10 steps. Good luck!

Update: After investigating this problem, Kichilron and I have determined that this problem is client side. Meaning, the player that is attempting to connect to your server MUST check his router settings and firmware, firewall settings, game settings, DayZ Commander settings (No custom run parameters for DayZ Epoch Chernarus), and antivirus programs. The list of probable causes can be infinite. Please look into all of these potential causes if you're having trouble connecting to a private server being run on a dedicated or virtual dedicated box. Also, keep in mind that your ISP and less than ideal internet connection will also affect if you can successfully connect to a DayZ server. If you're located in Narnia or Never never land, forget it! :P We hope this helps you fix your problem. Good luck out there. @Kichilron, thanks for your time and help with this issue. It is much appreciated. :)

I am the server owner, Kichilron. I sent you a Skype request. I'm not sure if I should post the entire RPT file here in this thread. The file has 24k lines of text in it. Please let me know how you would like me to post the RPT file. I appreciate your time. Thank you. @Polenar, thanks for posting this thread. Hopefully we'll get this sorted out asap. :)