Page MenuHomeFeedback Tracker

Some peoples Arma 3 have their game stopped working. We on server sees: Steam ticket check failed.
Closed, ResolvedPublic


We at clan [S.O.S] have a server with an issue that seems to appear only on our server. Out of all the players that go on the public server, 10-15%(or more) of the players have their game crashing at random. Mostly on connection but also randomly at anytime when they are in. We who are in the server we get the message:
DefaultServer: Player "Name" kicked off, Steam ticket check failed: (null)

We in the clan have no idea what causes this problem and we have had it for over a month. We are at the point where we have gone through alot of the code of all the scripting on our map. Even after all we have gone through... We are still at a loss. It must be the game somewhere, but again.. It only seem to be on our server(?). Any advice would be most helpful. {F23023}


Legacy ID
Game Crash

Event Timeline

413X edited Steps To Reproduce. (Show Details)Jan 10 2014, 9:47 PM
413X edited Additional Information. (Show Details)
413X set Category to Game Crash.
413X set Reproducibility to Random.
413X set Severity to None.
413X set Resolution to Fixed.
413X set Legacy ID to 3251940574.May 7 2016, 5:43 PM
FrankHH added a subscriber: FrankHH.May 7 2016, 5:43 PM

Name of the mission you guys are running? I only crash in MP when I play TeeTimes warfare.

413X added a subscriber: 413X.May 7 2016, 5:43 PM
413X added a comment.Jan 10 2014, 11:41 PM

The mission was first made by Tier 1 and was called something among the lines of "Tier1 combat patrol generator". Then we took that and modded it ourselves into something of our own and is now called: SpecialOperations v3.5.


Vitdom added a subscriber: Vitdom.May 7 2016, 5:43 PM

This happens when the Server checks with Steam if the Client is who it says it is. If Steam fails to respond, the client is kicked.

This is protection against game piracy.

AD2001 added a subscriber: AD2001.May 7 2016, 5:43 PM

It's not really good protection. It kicks a lot of clients from certain servers, whether they actually have the game on Steam or not.

This could be an issue with Steam, though.

Lux0r added a subscriber: Lux0r.May 7 2016, 5:43 PM
Lux0r added a comment.Jan 11 2014, 5:37 PM

The error occurs often, if players try to connect to the server. I uploaded a zip file including log and minidump.

I uploaded the mission (it's 3.6 now but still the same error) and 2 server logs, hopefully this helps...

413X added a comment.Jan 18 2014, 12:09 PM

Hello, I dont want to come off as some impatient player but as issue has been active for over a week. I see Astaroth stacking up on more and other issues, I wish ours dont fall under the pile.

We suffer badly by this bug to the point where it is tearing our community apart. We in the clan have been going through a vast amount of our own code in the scripts and have come up empty. We then tried switching to Bohemia interactive maps which appears to have the same problem. (Escape Altis and a clean map with only spawn points with no scripts at all.) We have tried turning off battleeye and still the issue was active.

Are we close to a solution or can we help in any way to test and try to fix this problem because, again, our community is suffering really hard because of this issue. Sitrep plz :P

413X added a comment.Jan 21 2014, 7:42 PM

The problem still exists after the patch. We need help.

413X added a comment.Jan 24 2014, 9:01 PM

So... We think it has something to do server side. Since we have 0 response from you guys. We bought another server; . And tested and still have our steam ticket error issue. So now we have 2 servers that doesnt work.

We had full servers from 2pm to 01.00 am before the new year. Today it has been in a all time low. 9 pm with only 2 players. Honestly guys, this game is fucking broken at this point and been like this for over a month. Ive seen so many players going to other games because of this constant crashing that im even started to consider switching now.

Iceman added a comment.Apr 2 2014, 1:39 PM


Is this issue still valid for current Steam Stable 1.14.?


413X added a comment.Apr 2 2014, 1:47 PM

This issue has been dealt with in another ticket. It was caused by corrupt .paa files that we used in clantags. Unsure if it has been resolved or not, the ticket went as private i think.