Hello,
My server will not save. It used to work, but I haven't used this server until recently, so I can't tell you with which ALiVE version or Arma version it stopped working with. I hit save and exit, the tablet comes up, but it doesn't go any farther than here:
http://i.imgur.com/X7NL3b4.jpg
Here is the alive plugin from a recent test running only @CBA, @ALiVE, and @AliveServer:
And my RPT:
I have also tried re-installing @ALiVE, @AliveServer and the alive.cfg to no avail.
Try replacing your data module.
same, already reported
Did not work. I tried the same mission on another server (connected to the same war room) and it worked fine. Seems this issue is tied to this particular server, but like I said, it used to work not long ago.
I should also note that the mission will load from its last persisted state, however I simply cannot save it again.
Has your IP or server name changed recently? These need to be updated on your warroom settings if so.
Do any other missions work, or are they all hanging?
Thanks
Nothing has changed recently. All missions on this particular server are hanging.
most likely a special char in mission name or player name.
Turn on Debug for data module and resubmit logs.
Mission was named Alive_Test so I renamed it to AliveTest. Still getting hung up.
With debug enabled:
need the server RPT
Sorry for the late response.
RPT: https://drive.google.com/file/d/0B3A0qrBy51cJbEVKc2w3R2x5OTQ/view?usp=sharing
Plugin: https://drive.google.com/file/d/0B3A0qrBy51cJN29GdzhBaUxydXM/view?usp=sharing
I've tried making a new war-room, but still getting hung up.
9:11:21 ALiVE SYS_DATA_COUCHDB - BULK SAVE 9:11:21 Error in expression <" scriptName 'cba\strings\strLen'; count (_this select 0); > 9:11:21 Error position: <count (_this select 0); > 9:11:21 Error count: Type Not a Number, expected Array,String,Config entry
Seems like it errors out at the start of the save.
Can you please test with the ALiVE Quick Start mission and let us know if that works.
Thanks for the logs. Hmmm see the same issue. Strange! Will likely have to give you a debug build to troubleshoot this one.