Proper Startup Line for CA/OA Beta Dedicated Server?

[pchaxor 0]

ARMA2_OA_Build_72418 - Dedicated Server - CA - OA

Having some issues when loading up a mission. Server seems to start fine, but when mission is read from bank I get a long pause and eventually the server crashes silently. I then see the error that it crashed when I reboot.

Program: C:\Program Files\arma 2\Expansion\beta\arma2oaserver.exe

Working Directory: C:\Program Files\arma 2

Params: -nosound -world=empty -config=OAACEserver.cfg -cfg=ArmA2OAServer.cfg -profiles=Expansion\beta\profile -mod=ca;Expansion\beta;Expansion\beta\Expansion

My folder Layout is:

c:\Program Files\arma 2

...\Expansion\beta\

Dta paths:

C:\Program Files\arma 2\Dta

C:\Program Files\arma 2\Expansion\beta\expansion\dta

I think I am missing something in my startup params... any ideas?

Do I need to combine the dta folders or specify the path when using the beta?

What are the proper startup params to run the beta?

Both arma2 and OA are in the same folders as show above.

Thanks!

Edited August 5, 2010 by pchaxor

[MJK-Ranger 0]

Hi.

Try to make a bat file(i.e: ArmA2_CO_Start.bat) and put this line into the bat file:

This will run ArmA2: Combined Operation(beta)

"C:\Program Files\arma 2\Expansion\beta\arma2oaserver.exe" "-mod=ca;Expansion\beta;Expansion\beta\Expansion" -nosplash -port=2302 -nosound -world=empty -config=OAACEserver.cfg -cfg=ArmA2OAServer.cfg -profiles=Expansion\beta\profile -name=server -gamerTag=server

Put the "ArmA2_CO_Start.bat" bat file into your ArmA 2 install folder: C:\Program Files\arma 2\

The double click on the bat file

Edited August 4, 2010 by MJK-Ranger

[pchaxor 0]

Thanks for the reply, however I run the dedicated server as a service.

The params you gave me are actually no different than what I am already using are they? It only appears you just change the order and also specified information that is already set in the configs as startup.

Thanks for the try; I am only asking for help because I think I have the startup params wrong or the beta has some issues.

Soemthing with the beta .bin file and artilary specified in Domination is causing some hang ups and crashes.

Please reply if you have something 'NEW' for me to try.

Thanks!

Edited August 4, 2010 by pchaxor

[MJK-Ranger 0]

Hi.

You mean this "error" in your RPT file:

=====================================================================
== E:\ArmA 2\arma2oaserver.exe
== "E:\ArmA 2\arma2oaserver.exe" -mod=ca -port=2302 -nosound -world=empty -config=_server\ArmA2_CO\ArmA2_CO_Server.cfg -cfg=_server\ArmA2_CO\ArmA2_CO.cfg -profiles=_server\ArmA2_CO -name=ArmA2_CO
=====================================================================
Exe timestamp: 2010/08/04 16:35:54
Current time:  2010/08/04 18:14:11

Version 1.52.72418
Item str_disp_server_control listed twice
Cannot register unknown string STR_DISP_LEFT
Updating base class ->RscText, by ca\ui\config.bin/RscSplashText/
String STR_artillery_computer not found
String STR_artillery_computer not found
String STR_ACTION_REPAIR_VEHICLE not found
String STR_ACTION_REPAIR_VEHICLE not found

If so, this is normally arma 2 error, has nothing to do with the Domination map.

I have reported this "error" message here: http://dev-heaven.net/issues/12243

[pchaxor 0]

Edit: Unrelated to beta stability.

YES! That is what I am getting. Does anyone have a solution? (I did not sepcify in original post as I really just want to make sure my params are correct)

I changed the way I start the beta .. "proper" instead of copying the beta server exe to the root and moving the dta files.

I would really like to launch these betas how they were meant to be launched to ease the pain of updating and "doing it right".

Also crashes the server silently. So on reboot, the crash will reveal itself on startup.

(be sure to disable or set the service to manual before rebooting if you run as service.)

Perhaps I will try without CA and see what happens... Good to know it is not just my server having issues.

Right now my server is down until I get home from work to test it more. (Windows 2003 Server here btw)

Edited August 5, 2010 by pchaxor

[MJK-Ranger 0]

Hi.

The "error" message in the start of your RPT is normally. Everybody has those messages in the start. Even the official update have those message :/

But i have been running the server here without any problems.

My server spec:

Win XP Pro 32bit

Intel C2D E6600

2048 MB RAM

I suggest you to try out the bat file startup parameters i posted in my first post, you can simple add the bat file into your service(startup service).

Download this Zip file and unpack it and copy the ArmA2_CO_Start.bat file into your ArmA 2 install root.

Double click on the bat file and see if it runs OK. If you run into some error, with default profile error, try to move the ArmA2_CO_Start.bat into your C:\Program Files\arma 2\Expansion\beta\profile

Then try to start the bat file.

This is how my server runs. I know, we don't have the same startup parameters, but i have tested that one i posted and my server start and i was able to play Domination map from Xeno.

http://rapidshare.com/files/411024752/ArmA2_CO_Start.zip

[pchaxor 0]

Just verified ... its the '-mod=ca' causing the crashes with the OA beta server.

Appears we can't run the beta OA server and ca anymore??

It is odd that BIS would break this.

I still think it is something I have set incorrectly.

I am going to dig a bit more.

[gossamersolid 155]

Hey there, I'm saving the same issues. If I run my CO server with the latest beta as a service, it crashes.

If I run it under my user, no crashes... but that's not a viable solution for any server admin/host.

I'd suggest to everybody that hosts a server to NOT put the latest beta on their server until a solution to this issue has been found.

@Devs: minidumps -> http://thegamewardens.com/dump/

Edited August 5, 2010 by GossamerS

[pchaxor 0]

I reverted back to dedi ARMA2_OA_Build_72291 and all is well again, even with ca. However, dedi ARMA2_OA_Build_72418 is unstable with or without ca from my testing.

- I am willing to test the next dedi beta release.

- I also noticed a perf increase with the older 72291 as well. Higher server frame rate.

Note that the client beta is stable so far and this is only the dedi files having issues.

Edited August 5, 2010 by pchaxor

[pchaxor 0]

Issues related to unstable beta patch and confirming startup params.

This thread can be closed as all issues have been resolved.

Thanks!