That sounds exactly like the problem I'm having on my server. I've been trying to run MArtials Takistan NATOFOR ALiVE mission in it's most recent form, as well as modified versions to fit my unit's play style, and this is happening to me.

I can run the server, it will populate with units as normal.
I can join, others can join, an we can play with player or ALiVE generated missions. But at some random point ,2 minutes in or 2 hours in, it will freeze up for one or more players. It will not crash, just freeze things in place while one or others can still move about.
We have to ALT+F4 out, or if possible exit Arma, and try to come back in. Server will show as up, but we cannot load back in.
Most recent RPTs I have for it I think:
https://www.dropbox.com/s/ayzs4i6tlcnpt89/arma3server_2016-01-22_04-24-45.rpt?dl=0
https://www.dropbox.com/s/efxmsxdoaoxxqxi/arma3server_2016-01-22_00-53-34.rpt?dl=0

I will try to remove the C2ISTAR module and see if only running it with Player generated missions will fix the problem.

Edit:
Just loaded up my version of NATOFOR (just tweaked medical and TFAR a little, changed bad guys to ISTS) with the removal of C2ISTAR. So, autogeneration of tasks is gone like I expected, but it also removes manually generated missions completely. So, there are no tasks that are able to be generated.
I see that OpFor units are still being placed by ALiVE OpCOm, so I assume the Mission just becomes Sandbox at that point , with players tasking missions for themselves, or Zeus placing missions.

@ Monty, Would that be a fair assessment of what you guys are experiencing?

Ok, forum seems to keep losing my password or booting me out for some reason.

We have been using auto-generation or Player generation of missions from the Player Operations in the HQ to run our missions.

What you're saying is that missions should be generating for us if we go out and do active patrolling, with interaction with civilians bringing us these missions?

The current build of M4RTI4L's mission that I'm attempting to get working has Spyder's Civilian interaction scripting. So, that should bring about missions for the unit?

If so, I'll try to get the unit trying that out, both with and without the C2ISTAR module in. I may have to turn off all auto-generation of missions with it in though to hopefully keep the freezing from happening.

@ ski2060 Yep exactly what we are experiencing, We have the same mission running, create "things" to do with Zues and it all runs perfectly well.
Stupid ammounts of AI spawning, CQB, civilians, server handles it nicely and will run it for days no freeze.

As soon as C2Istar is there are missions are requested/auto generation is used. Boom, freeze will occur.

Other thoughts I have to test, but have not yet are:
OPFOR Faction. We use the RHS insurgent faction or the SUD_Insurgents factions.

Island choice, we have been using SUP islands. May give it a run on Stratis/Altis again. - this may be a factor as I have noticed occasionally when creating a C2Istar mission it will spawn units in the lower left corner of the map. well away from the objective, they are still grouped etc, just off in the middle of nowhere. its the the entire group either, useusally 1 or 2 men out of a section.
So perhaps its a compounding problem ? cannot spawn units together, cannot move them together etc etc.

I'm willing to bet at this point it's just server branch issues. I ran M4RTI4L's mission with AIATP, and then with CUP and it hung the server with either one active.

If it could be nailed down and get stabilized so I can run our tweaked version, that would be phenominal.

I'll see if I can get the performance binaries put up on our server.
Do all the clients have to be running the same EXE's? Or just the server running one?

And think, with the new update coming, even more things may be broken. I think they're are making some changes to file architecture and other stuff. I'm not looking forward to half the mods I use being broken :(

I am currently in progression testing to see which mods are working and which aren't, also.
Basic AliVE Takistan map with CBA and Alive, ran fine for 12 hours yesterday.

Put anything with ACE up, and it hangs. Not even a hard crash, but teh same as you, a Freeze, with no messages generated on screen.
The server always shows Cannot Communicate Errors.

I think I'll either find or put together a mission with just Alive and RHS to test also.
My unit would hate to lose ACE, so I would probably be relegated to NOT using Alive for my experimental server.

I think it's ACE. I am using RHS Insurgency ALIVE and it is not crashing. I had it on overnight with a couple unit mates playing on it, no crashes.
Put NATOFOR Insurgency that has ACE on it, and it Freezes in anywhere from 2 minutes to 2 hours.

There is something in ACE that is conflicting with ALIVE. No clue what it might be though.

I have 4 days off starting tomorrow (but tomorrow is daughter's birthday party). So, I'll see about throwing a mission together with a basic ALiVE setup, CBA, and ACE. Now, what ACE modules should I put down? Because there are a ton of modules for it- Advanced Medical, ballistics, mechanics, etc. Should I just drop em all down and see how that runs? Or maybe just Advanced Medical and Ballistics?

Also, I noticed from streaming my RPT file off host site, that I get the same Server: Object not found error repeating in significant amounts bloating the RPT. BUT, it's not crashing or freezing the server.

So I have Operation Landlord with ACE running on my server right now if anyone want to see if they can get it to Freeze. It's been up about 5 hours now with no freezing.
But I've only had one player on it so far as I'm at work.
If anyone wants to jump on and test it out to see if they can get it to freeze, please feel free.
69.162.125.22 -port=2347
ski2060 Testing Server
@CBA; @ACE, @ALiVE. Everything is vanilla otherwise.

I ran Operation Landlord with @AliveServer no problem. CBA, ALive, AliveServer and ACE. Ran several days 12-16 hours each time with no crash or Freezing.

I get massive amounts of the Object not found errors if I am running ACE and RHS togther.
I tried dropping LeightsOpFor for CAF Aggressors and still got the freezing. RHS was involved both times.

I found a modded version of RHS Russian Insurgency the other night that seemed to be running stable. So, I swapped the Russian stuff out for US and have it up on my server now. @CBA_A3;@ace;@ALiVE;@task_force_radio;@IWAR- Irregular Warfare;@Leights OPFOR Pack OFFICIAL;@Spyder Addons;@RHSUSAF;@RHSAFRF;@Ares;@CUP Terrains - Core;@CUP Terrains - Maps;@Aliveserver

It hasn't crashed or frozen yet as far as I can see. Although It is throwing the Object not found error, and I've been the only one on the server.

I'll see if removing @aliveserver does anything if the currently running mission freezes.

@Tupolov @SOAR_Jooce honestly, your point about CBA and ALiVE working fine was lost in the noise :) If that is the case then we just need to ID the mod it conflicts with.

We appreciate your testing and effort absolutely. As you can imagine we want to focus on specific ALiVE issues. If we can nail down if its ALiVE and ACE (for example), then we know where to start. This thread just is full of people reporting issues with a whole mix of mods, we just don't have the spare hours to chase those combination of mods down.

We are interested in fixing any conflict with ACE (or RHS).

If someone can confirm the issue with CBA, ALIVE and ACE - that would be great!

Also, if someone can confirm the issue exists with ALiVE 0.9.9 (and any modset) that would be useful too!

Thanks for your patience and apologies for any perceived "aggro" from us :)

If you do confirm that issue - please pass us RPT log, plugin log and the mission SQM/files.

Cheers

Your own Developers have said they have reproduced it with 100% success rate. Using CBA/ALIVE an ACE is pointless at this time. Are you not in communication with your developers?

If they have a 100% success rate of reproducing the issue, why are we going back to square one? We have done nothing but support ALiVE and give information non stop. We tested Alive 1.0 within 30 minutes of hearing it was released. And as soon as we report it does not fix the issue Tupolov goes full defensive on the Arma subreddit, Tupolov acts like ALiVE cannot possibly be conflicting with the mods, even though your developers have now clearly stated that it does.

"It does not mean that ALiVE is at fault. Until we can get a reproducible issue without other mods (i.e. just CBA and ALiVE) then we can actually go about fixing something." - Tupolov

Guess what, if removing ALiVE from our modpack brings stability. It does mean ALiVE is partially to blame.
Now please work with your developer who says he has a 100% chance of reproducing the issue, it seems like he is the only one actually doing positive work to get this done and fixed.

@dixon13 That means the server hasn't given up and crashed yet.

Yeah, but when it sits there for hours without fully crashing it kind of impacts your ability to use the server to play on. So it just gets restarted or the mission changed.

If I can find a suitable replacement for RHS I would use it. CUp would most likely work, but lots of my unit guys don't seem to like CUP, and think their models are too low quality for some reason.

I wouldn't mind it, and may switch on a map build just to see how it looks and plays.

@ski2060 Yeah, but when it sits there for hours without fully crashing it kind of impacts your ability to use the server to play on. So it just gets restarted or the mission changed.

If I can find a suitable replacement for RHS I would use it. CUP would most likely work, but lots of my unit guys don't seem to like CUP, and think their models are too low quality for some reason.

This is the exact situation we have been put in as well. The server will just freeze and will not create any meaningful logs. If we don't shut down the server manually it will hang there forever.

CUP is a quantity over quality mod (weapon/unit) so its not an option for replacing RHS which is quality over quantity. I used to be a CUP supporter until I realized this fact.

And we can't drop RHS to support ALiVE to only have CUP as a backup. Its why we have chosen RHS over ALiVE at this point. We can replace some of the functionality of ALiVE with DAC if we need to. Obviously we would prefer ALiVE but seeing as there really isn't hope for a fix in the near future, we will have to focus on implementing DAC with Headless Client.

If the ALiVE devs can give us something to test other than "CBA, ALiVE, and ACE" we will help, but testing redundant mod packs is out of the question at this point. We know those three are not conflicting, and we know RHS is.

So, I have a question and maybe something to narrow down the freezing.
SOAR team, are you using an RHS BLUFOR or OpFor OpCom in your missions?

Whenever I have a mission using an RHS faction as BLUFOR (typically USarmy_d) I have the freezing issues.
I have a modified RHS Russian Insurgency mission that I swapped out the player faction from Russian to US Army.
However, I am not using a BLUFOR OpCom. I have 2 enemy OpComs, an IWAR USML_AIF Occupation commander, and a Leights OpFor ISTS Insurgent commander.
the plan is to have the map heavily occupied by the main AIF forces, and the ISTS are recruiting from the local civilians. This will put some heavy pressure on the players when they are in the field.

I have this mission up and running now, and it appears to not be freezing. I had 3 unit members on yesterday for several hours with no problems.
I left the server up and running overnight, so it's probably been on 16 hours or so at this point without crashing. I have no logs though, I turned off logging because I was getting bloated RPTs with the Server: Object #:###### not found (message type_91 or _119) messages, but the server was not freezing.

I will try to leave this mission running for a couple of days and see what happens. It is on 0.9.10 right now, and I plan to update to 1.0 middle of next week when I am off work again.

@Tupolov Looks like 1.52 is stable so far - 4 hours of testing... With ALiVE 1.0 and same mission that was freezing with 1.54+

SOAR also rolled back and attempted to use 1.52 prior to ALiVE 1.0 as well. It appeared to resolve the freezing issues but created more issues for us as a result.