That's a very good question! unfortunately, the problem "fixed" itself and worked fine for 6 days. This week it has returned, being "broken" for 1-2 hours each day - at different times. The problem (always) appears first in a large (490k) form that has 410 fields and uses primarily Arial. I have converted most of the fields in that form to MyriadPro and got that form to still fail. I have totally converted it to MuriadPro but now I need to wait until the system is "broken" again before I can test. Sometimes that is the only form that fails. other times that one fails and so will another form (200k). There have been times when even the IVS sample forms fail. Once again, there is no consistency here - other than generally the problem is repeatable for the duration that the system is broken ie: for the 1-2 hours that it's broken I can consistently fail forms - although not all forms.
We are running this is a WebSphere cluster with other activity going on - yet we are unable to identify or isolate any other potential influence.
And yes, we are going crazy trying to determine the root cause of this! We are also unable to move this to production until we have either identified root cause or run for a long time without form render failures.
It sounds to me like one of the instances of Forms executable is dying due to invalid font, and is then failing for subsequent renders. The reason that it's intermittent may be that you have multiple instances of the Forms executable, and one of them has failed, and the other(s) are okay.
One thing to try is to check your fonts in the underlying XML for each of your forms, because sometimes it's hard to locate all the instances of font usage. Search for:
<font typeface="Nyala" psName="Nyala-Regular" weight="normal" posture="normal"/>
We have some internal tools that will go through a set of forms, and extract all this information - if you're interested in us running these tools against your forms, please email info-at-avoka.com.
I've the almost exact same issue.. (same error code ALC-FRM-001-004 but different error msg as highlight in red below)