Klinky

Same issue over here: Quoted my personal message to Uncle.Biddle Maybe someone k now a working solution When using the old version, without the occupied cities, the door work and the missions do de-spawn normally.....

I only have the standard Mission.pbo (altis) and i see : ["Land_CarService_F", [14618.7,16877.4,18.7724], [[0.750538,-0.660827,0],[0,0,1]], [false, false]], <-- First line as example do i have to chance the first false, the second or both?

A litle correction.. The doors at the traders can not be opened, only the doors used by EBM can be opened. But still the same issue with the not cleaning up (Finished when lost) the missions.

After having problems with the missions not cleaning up after "failed Missions", and updated DMS to the last version 1.66 (feb 2017) i got a new problem: the missions never end when not cleared. They where there until either been cleared or restating the server. In an other posting, of the problem after the last ArmA update that within the traders the doors can not be opened, i tried to solve this with the solutions given in the posting, and it did not solve it. I was desperate that the missions did not clear after mission fail..... that i decided to reinstall the older version 1.36 (the before the occupation version) And guess what.... missions fail = clear area, door can be opened again at the traders. So this problem after the last ArmA update was not in "Exile" or "Extended Base Mod", but within the "DMS" mod v1.66... Sorry for this, but i thing any found errors should be mentioned to solve the issues without any offense of course. Klinky out.

I notices that when a occupied village that not is been cleared, the IA will not be deleted, they are still alive. After a view occupied missions, and some static missions, the server (Script max AI) stops creating new missions, and the random missions are the first that stop being created. The reason for that is the ax AI, every time the AI count grows and grows.. i have to clear every time the villages. (after the missions are lost, to have the AI count low). This is since the 1.68 update.

Thank you very much .Doppelpoint , it did work, problem solved.....

LOL.... was just looking for the my.ini, found it and searched for the sql-mode (found the path by google - and discovered my misunderstanding in short messages ) I copied the line, and wanted to post here, you already corrected me.. Thanks for that, and yes i did the steps you explained... no I'm going to test the new settings.. BTW i did not manually changed it, maybe this was a result when i updated it with the "MySQL Connectors"

The sql_custom_v2 > exile.ini:

Standard install of MySQL and Workbench, updated from 5.7.12 to 5.7.17 on 29/30-12-2016 02:30 Local time (Netherlands) MySQL downloaded @ https://www.mysql.com/ in March 2016 (5.7.12)

Where can i find the rpt? The logfiles: (to big to post) http://alliedassault.nl/LOG.rar

All 4 of the files are in the folder...

Hello, since 29-12-2012 there are some SQL saving problems. My SQL version: 5.7.17 Workbench 6.3 (V. 6.3.8 build 1228CE - 64Bit) Exile: 1.0.2 Arma 3: 1.66.139586 When someone dies, it is not posible to spawn back. Exile vehicles do not been saves in the MySQL db. What could cause this issue?

Annyone of the RHS mod could have a solution?

When i buy a vehicle of the Russian Federaiton in Exile 1.0.2 my server chrashes. I took a look in the Arma 3 Editor, and checked the names of the vehicles. These names are the same as i used in the trader. rhs_t72bd_tv rhs_t80u45m rhs_t90a_tv rhs_zsu234_aa rhs_bmp1_msv rhs_prp3_vmf rhs_brm1k_msv rhs_ka60_grey RHS_Mi8mt_Cargo_vdv RHS_Mi24V_FAB_vdv RHS_Ka52_vvsc The GREF and USAF vehicles have no problem. I re-downloaded the rhsafrf.0.4.1.1.bikey , rhsgref.0.4.1.1.bikey and rhsusaf.0.4.1.1.bikey keys. This did not changed anything about the issue i have on the server with loading of the Russian vehicles. In the attachment is the I/O error of the server after buying the russian vehicle

i reduced it to the same settings as in 0.9.6 and going to test it. the settings in 0.9.6 i used was 100000 instead is 1 million.., i think i made a 0 to much.. But after the change to 100.000 (without the dot off course) i changed the permanentlyDeleteTime to 100 (days) and re-PBO-ed the exile_server_config than rebooted, and guess what.... territory gone (also in DB) My latest test: did this for a test with the original settings (Yes, i backupped it) and re-PBO-ed this one without changes..... and rebooted the server, and ther it happened the same.... Territory gone, also in DB.... UPDATE: After replacing my changed config back and restart, place territory flag, upgrade territory and restart server, the territory stays. So i think the issue is within the re-PBO (timestamp of creating the PBO) of the exile_server_config.pbo.