Posts tagged "terminated"

LiveCycle ES: Error “Stalling action since child process is terminated”


 Terminating a sub-process in LiveCycle ES (8.x) stalls the sub-process’s parent action with the following message:

2010-04-23 10:55:21,884 ERROR [com.adobe.workflow.AWS] stalling action-instance: 328 with message: Stalling action since child process is terminated

This happens even if the parent action is already complete.  The expected behavior is that the parent action would not be stalled and this is how it worked in LC7.


This issue has been addressed in LiveCycle ES2 SP2 and later verions.   There is a patch available for this issue for LC ES, so contact enterprise support should you require this patch.

reference: (181577032/2610886)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycleES: “The application has failed to start because omniDynamic403_rt.dll was not found”


When you are attempting to perform a render operation in LiveCycle ES, you may receive the following error in Windows itself:

The application has failed to start because omniDynamic403_rt.dll was not found.
Re-installing the application may fix the problem.

You should then check the server log for any exceptions. You may see the following exception:

Service XMLFormService: Starting native process with command line
-MyPath D:\bea\user_projects\domains\lc_domain\null\adobe\lc_server\XMLFormService................
BMC024: Service XMLFormService: Process ProcessResource(name=XMLForm.exe,pid=0) terminated abnormally with error code {3}

This could also be accompanied with an ALC-WKS-007-040 error in workspace if you are attempting to render into the browser. You may also see another error code in the server log ALC-FRM-001-004, which indicates a problem with the XMLFormService, of FontManager service. You can check that both of these services are running in the admin console for LiveCycle.


The underlying cause of this is that the XMLFormService could not be found. This is due to the “null” entry in the path to the XMLFormService as seen in the exception above. This actually creates a “null” directory on your server’s file system, and will populate it with the native files. However at runtime it cannot interpret this “null” in the path, and so reports that it cannot find the XMLFormService.


You will have to modify your weblogic startup script to set the adobeidp.RootDirectory property.
1. stop your weblogic server and any admin server that might be running
2. find the setDomainEnv.cmd or script and search for JAVA_OPTIONS (this is usually at the end of the file)
3. you will need to add the following argument to the JAVA_OPTIONS:
-Dadobeidp.RootDirectory=<path to LiveCycle Domain>  (e.g. D:\bea\user_projects\domains\lc_domain)
4. save the file
5. restart your weblogic server

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 10.0/10 (2 votes cast)