User Details
- User Since
- Mar 7 2013, 8:29 PM (611 w, 6 h)
Oct 6 2022
Possibly fixed in T167788?
This seems related to the ticket I opened T166964? Looking forward in seeing working 'cateyes' on MP servers :-)
Aug 10 2022
Aug 5 2022
Aug 30 2021
Attached Crash Files (ZIP) -
Oct 18 2020
Mods in use.
Mission fails to load successfully with the 64-bit A3 Linux Server.
May 10 2016
Added another crash file to this ticket (stable exe)
arma3server_2015-02-08_19-04-33.zip
No further information available
Added another crash file to this ticket.
arma3server_performance_138v2_2015-02-07_18-52-33.zip
No further information available
Brilliant - I hope its a fairly simple resolvable one for the team.
I've been given a heads up by one of our 16AA group members who has said that the crash 'might' be related to a 'placed down a broken static weapon' (a weapon from a mod that was ported from Arma 2)
I forgot to add that the 'client crash' file is running the 'Stable' release, and not the 'Performance' exe.
Server Crash File 'arma3server_performance_138v2_2015-02-04_19-53-35.rar'
End user crashed just before the server crash and has provided the crash dumps from his system - Client Crash file 'clientcrash.rar'
Similar / Related ticket - http://feedback.arma3.com/view.php?id=22133
Hmm, I'm wondering if its something similar that I've encountered over the past day
http://feedback.arma3.com/view.php?id=22552
I've used both the Stable and latest Performance EXE's (Windows)
If you check your RPT while the server is started, do you see the message that it's connected to the 'Steam Servers'? I don't, unless I remove the offending 'bikey' from the 'keys' folder of the dedicated server.
example - end of RPT file
13:59:09 Initializing Steam server - Game Port: 2302, Steam Query Port: 2303
The next line, if successful would show (but doesn't, unless I remove the bikey causing the issue):
14:03:00 Connected to Steam servers
I've also noticed that if I kill/terminiate/end task the service via the 'Wait chain' I get a crash dump appear (if I just kill the service via end tasking the exe process I don't)
What I mean is this:
- Resource Monitor
- Select the service - in this case the a3 server exe
- Right-click it and select 'Analyse Wait Chain
- Select all the processes listed
- Select 'End Task'
A crash dump/rpt then occurs.
If I go the normal route and just 'End Process Tree', the server exe from the Resource Monitor, I don't get the dumps.
I believe a resign of the keys resolved the issue for the particular mods key which wasn't working/corrupted.
Crash also occurs in the latest performance exe (1.38_perf_v2)
Crash File attached:
arma3server_performance_138v2_2015-02-03_13-36-00.rar
Another 1.38 server crash....
File added: arma3server_2015-02-03_12-56-17.rar
Some what related to the above issues reported but in this case with the sig keys.
Sig keys signed for the mod doesn't connect to the steam servers on this Windows 8 Enterprise x64 dedicate server system (but DOES when run from a Windows 7 Enterprise x64 or Windows Server 2008 R2 dedicated server). Weird one. Usually it doesn't provide a crash dump/rpt but in this case I terminated the session 'wait chains' which prodcued the RPT and Dumps.
Nailed what the mod issue was...
ATLAS_LHD mod
http://forums.bistudio.com/showthread.php?186728-ATLAS-Mod-LHD-Plus
Seems one of the PBO's (ATLAS_Weapons.pbo) wasn't correct (not the mod makers fault but possibly internally to our group when sorting our mod pack out).
We had to re-pack the ATLAS_Weapons.pbo and include it back into our mod.
This seems to have resolved the problem.
Still I believe this should have a developer look into ways of reporting it into the RPT rather than having the server crash.
While we haven't attempted to run it without our set of mods (which was updated). We suspect it is one of the mods that has caused the issue.
The purpose for reporting this is that is crashes the dedicated server exe (blah blah has stopped working).
It was suggested by one of our group members that it seems to be a possible 'clipping' issue with an object 'clipping' on the 'Chernarus' map.
Because its a hard crash of the Dedicated server I think it's worth the BIS Devs taking a look to see if there's anything that can stop the server from 'crashing' and do something different to warn of errors in this instance.
Uploaded another v1.38 Server Crash (.zip)
You're welcome - Glad to read that you're back up and running :)
@Moderators - You can probably close this ticket :)
Check this thread, it might be the cause to your issue...
http://forums.bistudio.com/showthread.php?187922-Game-crashes-instantly-on-launch/page2
Similar / Related issue - http://feedback.arma3.com/view.php?id=22567
I've added a crash dump from the latest release (v1.38)
'1-38-servercrash.rar'
Server & HC RPTs from the same session added to the ticket
Ignore this ticket as I've found out this is related to the Virtual Ammobox System (VAS)
http://forums.bistudio.com/showthread.php?149077-Virtual-Ammobox-System-(VAS)
Potentially fixed in the latest version too (v2.3)
http://forums.bistudio.com/showthread.php?149077-Virtual-Ammobox-System-(VAS)&p=2603701&viewfull=1#post2603701
3rd Party Mod
This will be/has been resolved by the 3rd party mod that was the actual cause for the error message.
Apparently fixed in today's DEV Branch Update
Advise to re-test and confirm results here.
Reported fixed here:
I advise re-testing and confirming the fix :)
Anyone available to test and confirm so this ticket can be set to fixed/resolved?
This is still occurring in the latest DEV Branch Build
Type: Public Beta
Branch: Development
Version: 0.77.109940
Uploaded a recent HC (Headless Client) RPT file
Type: Public Beta
Branch: Development
Version: 0.77.109136
- Start Dedicated Server (I have CBA enabled)
- Start Headless Client (Optional)
- Start 'Players' Client & connect to Dedicated Server
- Select mission 'COOP 7 Headhunters'
Play the mission as you want (I just used 1 player, disabled AI) and walked upto the Lighthouse, facing towards the Range where the 1st target is - Decided to take a few pot shots until the enemy vehicle eventually killed my character.
Upon disconnection I checked the server RPT to find the errors which I've attached to this ticket (a3-svr_rpt-errors1.zip).
Some errors will be the same from the originally logged issue.
Type: Public Beta
Branch: Development
Version: 0.77.109643
Mission: Official BIS (COOP 07 Headhunters)
Another error (fairly new) now seen within the RPT.
c:\w\c_branch\poseidon\futura\lib\network\networkserver.cpp NetworkServer::OnClientStateChanged:NOT IMPLEMENTED - briefing!
Type: Public Beta
Branch: Development
Version: 0.77.109243
- Start Dedicated Server (I have CBA enabled)
- Start Headless Client (Optional)
- Start 'Players' Client & connect to Dedicated Server
- Select mission 'COOP DEFEND 10 Defend Kamino'
Play the mission as you want - In my case I just connected as the Bluefor Squad Leader and randomly started laying mines around the place.
Errors can be seen within the Log 'a3-svr-rpt2.txt
Claimed fixed...
I advise that this is re-tested and confirmed so the ticket can be closed.
This has been labelled as fixed...
Recommend this is regressed/re-tested and confirmed as fixed so this ticket can be closed.
This has been labelled as fixed....
I recommend this is regressed/re-tested and confirmed so this ticket can be closed.
This has been reported fixed here...
Advise to regress/re-test and confirm the fix :)
Confirmed its working for me as I no longer get the error as mentioned in my last post above:
Type: Public Beta
Branch: Development
Version: 0.77.108906
I think it would be good if others could test and confirm :)
Type: Public Beta
Branch: Development
Version: 0.75.108717
I'm no long seeing the issue appearing in the console output (I've disabled BE):
<time> Cannot join the session. Wrong password was given.
My HC however never seem to be able to keep a connection to the server.
This is probably now a different issue, and hopefully one that is just configuration issues if everyone is able to connect ok)
[Server Console output]
15:08:33 Dedicated host created.
15:08:36 Host identity created.
15:08:56 Player [HC]Client_1 connecting.
15:10:27 Player [HC]Client_1 connected (id=76561198095017001).
15:10:34 Player [HC]Client_1 disconnected.
15:10:49 Player [HC]Client_1 connecting.
[HC Console output]
15:08:52 Dedicated client created.
15:08:57 > Player [HC]Client_1 connecting
15:08:57 > Welcome to 16AA ARMA3 Beta Server #1
15:08:59 > Website - http://www.16aa.com
15:09:02 > Forum - http://www.16aa.net/forumindex.php
15:09:05 > Blade BL460c, 2 * Intel Xeon(R) CPU E5420 @ 2.5GHz (2 Physical Processors) - Quad Core
15:09:08 > 16GB RAM PC2-5300 DDR2, 2 * 146GB SFF SAS HDD's (RAID 1), Windows Server 2008 Standard x64 (64-bit OS)
15:10:28 > You were kicked off the game.
15:10:49 Client connected: 127.0.0.1:2302
15:10:49 > Player [HC]Client_1 connecting
15:10:49 > Welcome to 16AA ARMA3 Beta Server #1
15:10:52 > Website - http://www.16aa.com
15:10:55 > Forum - http://www.16aa.net/forumindex.php
15:10:58 > Blade BL460c, 2 * Intel Xeon(R) CPU E5420 @ 2.5GHz (2 Physical Processors) - Quad Core
15:11:01 > 16GB RAM PC2-5300 DDR2, 2 * 146GB SFF SAS HDD's (RAID 1), Windows Server 2008 Standard x64 (64-bit OS)
Issue still present in the latest dev beta release
Type: Public Beta
Branch: Development
Version: 0.75.108659
Issue still present in the latest dev beta release
Type: Public Beta
Branch: Development
Version: 0.75.108541
Issue still persists in the latest dev beta release
Type: Public Beta
Branch: Development
Version: 0.75.108469
Yes confirm - HC is still NOT working when a server (join) password is set
<Server & Client Version>
Type: Public Beta
Branch: Development
Version: 0.75.108378
Client responds with:
<time> Cannot join the session. Wrong password was given.
Issue still present in today's update....
Type: Public Beta
Branch: Development
Version: 0.75.108432
Claimed fixed...
I suggest you chaps re-test and confirm so this ticket can be closed :)
I confirm I get similair experiences (using the development build) @ 1920 x 1080 resolution (not tested at any other resolution)