Page MenuHomeFeedback Tracker

AddonBuilder error since latest release: "Build failed. Result code=1"
Closed, ResolvedPublic


Tried to pack a project directory after changing only one PAA-File. Same project packing worked fine with the "old" AddonBuilder" before the latest release.

Error occurs whether "Binarize" is checked or not. No log-file is written.

See also attached screenshot. {F24022} {F24023} {F24024} {F24025}


Legacy ID
Steps To Reproduce

Select project directory
Press "Pack"

Event Timeline

TomNedry edited Steps To Reproduce. (Show Details)May 29 2014, 7:55 PM
TomNedry edited Additional Information. (Show Details)
TomNedry set Category to Tools.
TomNedry set Reproducibility to Always.
TomNedry set Severity to None.
TomNedry set Resolution to Fixed.
TomNedry set Legacy ID to 1742502212.May 7 2016, 6:40 PM
TomNedry edited a custom field.

please do the following:

  1. download the file I've just posted to directory where the AddonBuilder is installed (default is c:\Program Files (x86)\Steam\SteamApps\common\Arma 3 Tools\)
  2. rename it from logger.xml.txt to logger.xml
  3. run your packing again
  4. AddonBuilder.log will be created in the Tools install directory (so again in c:\Program Files (x86)\Steam\SteamApps\common\Arma 3 Tools\ for default install directory)
  5. upload resulting log here
MrF added a subscriber: MrF.May 7 2016, 6:40 PM

Change logger.xml inside tools root folder where it says L:\ inside to P:\ and you will get logs in P:\ logs folder , youcan change to where you wnat it.

MrF added a comment.May 31 2014, 10:53 AM


Thanks mate !! But it should be better, if BI make a readme about those things...

Regards, MrF

No problem glad it works for you also

Only wish i knew how we download those attached Files so i can see if Bis_Cooper has even better way to do it ;).

I saw the fix was made but err , i looked and now there is no loner a Log in the tools folder LOG folder , could you please state where "the correct folder" that the fix eludes to is please so i can find and check it works


ok, you can use this as logger configuration (just replace, it will log every log there is). log file will be placed along the exe file:

<?xml version="1.0"?>

  <appender name="RollingFile" type="log4net.Appender.RollingFileAppender">
    <file value="AddonBuilder.log" />
    <appendToFile value="true" />
    <maxSizeRollBackups value="2" />
    <layout type="log4net.Layout.PatternLayout">
      <conversionPattern value="%date [%level] %thread: %class.%method - %message%newline" />

  <appender name="Console" type="log4net.Appender.ConsoleAppender">
    <layout type="log4net.Layout.PatternLayout">
      <conversionPattern value="%date [%level] %thread: %class.%method - %message%newline" />
  <appender name="StatusAppender" type="AddonBuilder.StatusAppender">
    <layout type="log4net.Layout.PatternLayout">
      <conversionPattern value="%message%newline" />
    <level value="DEBUG" />
    <appender-ref ref="RollingFile" />
    <appender-ref ref="Console" />
  <logger name="user" additivity="true">
    <level value="INFO" />
    <appender-ref ref="StatusAppender" />


Thanks for the code , however the Point is the last syntax before update was only wrong by L:\ != P:\
that small change made USer and addonbuilder Log to tools \LOGS\AddonBuilder

could you paste the code to achieve this again rather than tools\addonbuilder.log that the code above achieves (yes it does work though but messy location)

Much appreciated

Sorry for the late reply => Vacation!

I uploaded the log which sums up two operations:

  1. "Binarize" unchecked => Build fails as before (Log line 1 - 22)
  2. "Binarize" checked => Build successfull (Log line 23 ff)

@TomNedry: thanks for the log. the issue is fixed. we're gonna test it internally before update.

@deanosbeano: this line "<file value="AddonBuilder.log" />" specifies log locatation. so in your case it should look like this: <file value="LOGS\AddonBuilder.log" />
or this: <file value="P:\LOGS\AddonBuilder.log" />

Fixed. Submitted for internal testing


Works Thanks for the Help :)

Only problem iss the Addon mkaer allways stays with "ready" and no longer displays Binarizing : copying : packing anymore , i think this is after yesterdays update not beause of the logger fix , shall i make new ticket or ?

The status is actually a log and it's configured in the same logger.xml file. Please make sure you have these lines there (present in original xml):

<?xml version="1.0"?>


<appender name="StatusAppender" type="AddonBuilder.StatusAppender">

<layout type="log4net.Layout.PatternLayout">
  <conversionPattern value="%message%newline" />


<logger name="user" additivity="false">

<level value="INFO" />
<appender-ref ref="UserConsole" />
<appender-ref ref="UserRollingFile" />
<appender-ref ref="StatusAppender" />




Fett_Li added a subscriber: Fett_Li.May 7 2016, 6:40 PM

I'm encounering the same problem "Build failed. Result code=1" allthough I'm using both logger.xml which have been posted by BIS_cooper on 2014-06-03 16:47 and 2014-06-20 10:11. I merged them together in on logger.xml in the directory where the addonbuilder.exe is executed (not P:/ drive allthough I have one mounted).

Can I get any help here because pboProject doens't work either?


could you please upload your log file (c:\Program Files (x86)\Steam\SteamApps\common\Arma 3 Tools\Logs\AddonBuilder.rpt)?


There was no AddonBuilder.rpt in my AddonBuilder folders (both ArmA 3 Tools directive and P: drive). But I uploaded my AddonBuilder.log, I think, this is waht you meant :) It's called AddonBuilder_Fett.log.

from the log I see you are gettring error during config convert. seems there is a bug in "C:\Program Files (x86)\Steam\SteamApps\common\Arma 3\@FETT_Test\addons\FatTrack\config.cpp" file. Maybe wrong project dir? It needs to poinnt to the root of include files used in the config.cpp

Ah. So I know the error. I'm including a userconfig file directed in the arma 3 root. I do so by: #include "userconfig\FatTrack\keys_FatTrack.hpp" and I asume it won't find it because it's a non-addon file. Do you know how I can work around that problem?

project path in options window to rescue. this defined dir used to search for includes in config files. so in your case it should point to arma 3 root

Mass-closing all resolved issues not updated in the last month.

Please PM me in BI Forums ( if you feel your bug was closed in error.

This comment was removed by Geez.
Geez added a subscriber: Geez.Sep 24 2021, 11:06 AM