This error shows up randomly on a "Run Action List" inside of an "Async Action Group". I tried making a simple project that demonstrates the failure, but I couldn't get it to fail. I can reduce/eliminate the failure by changing the Async Action Group to have a thread start delay.
Execute Condition (JavaScript)Condition : !DrainWebServers || ServiceMachineCount > 2Error In Execute Condition (JavaScript) Process AppTierStack #2 : Duplicates not allowed
Thanks for any help you can provide!-John Gonyo snagajob.com
I grepped our entire source tree for “Duplicates not allowed” and found 1 hit, the Add method of a dictionary class. Unfortunately this class is used everywhere! Can you run FinalBuilder with the -LOGEXCEPTIONS command line option. This will log all exceptions (handled and unhandled) to a file in your %TEMP% folder - FinalBuilderExceptions.txt. When you see the error again, close finalbuilder and send the file to “support @ finalbuilder dot com” - Note that this option will slow down FinalBuilder a lot so once you have the error occur you can stop using this option. In the mean time I’ll see if I can reproduce the problem. Sending in your FB Project file might also help us reproduce the problem too.
BTW, we didn't see this until upgrading to version 1682 (from the very old 993!). We tried the 1724 and that didn't fix it. Looking at the release notes for 1682 I saw:
"Bug - Action Conditions - Fixed issue with log status of skipped actions."
Since this error seems to happen only with actions that should be skipped, maybe something was introduced during that change?
I was able to use this sample project to get the error, but it's only happened once and I didn't have log exceptions turned on. Maybe you can find it quicker than I can.
I'll let you know if I can get the sample project to reproduce the error, and I have the trace.
Thanks for the info. I believe I have found the problem, however I wasn’t able to reproduce the problem here at all so it’s hard to say if it is 100% resolved. This build includes some changes to hopefully solve this problem :
FYI: This issue was apparently resolved for us with the fix you provided. We also changed our asynchronous tasks to start up with a delay to avoid this problem in the future - and it seems to help performance somewhat.