Adobe Experience Manager Forms

NirmalAEM · 6/12/23

Forms application running in AEM 6.5 OSGI Server installed on Windows 10 Enterprise machine. XMLForm.exe stopped working abruptly after restarting the O/S. Verified all the pre-requisite for running XMLForm -

Microsoft Visual C++ 2008 redistributable
Microsoft Visual C++ 2010 redistributable
Microsoft Visual C++ 2012 redistributable
Microsoft Visual C++ 2013 redistributable (as of 6.5)

Exception while generating pdf -

13.06.2023 00:09:14.236 *INFO* [POADestructor] jacorb.poa POA BR-6 destroyed
13.06.2023 00:09:14.236 *INFO* [[0:0:0:0:0:0:0:1] [1686629352933] GET /content/forms/af/formdoc/channels/print/jcr:content.treejson HTTP/1.1] com.adobe.service.ResourcePooler Failure while process launch, attempt: 5
13.06.2023 00:09:14.238 *INFO* [[0:0:0:0:0:0:0:1] [1686629352933] GET /content/forms/af/formdoc/channels/print/jcr:content.treejson HTTP/1.1] jacorb.poa Using server ID (7345908197) for transient POA
13.06.2023 00:09:14.248 *INFO* [[0:0:0:0:0:0:0:1] [1686629352933] GET /content/forms/af/formdoc/channels/print/jcr:content.treejson HTTP/1.1] com.adobe.service.ProcessResource Service XMLFormService: Starting native process with command line "C:\\MyDrive\\Server\\AEM65AuthorInvest2\\crx-quickstart\\bedrock\\svcnative\\XMLFormService\\bin\\XMLForm.exe" -MyPath C:\MyDrive\Server\AEM65AuthorInvest2\crx-quickstart\bedrock\svcnative\XMLFormService -IOR IOR:000000000000002249444C3A636F6D2F61646F62652F736572766963652F4D616E616765723A312E30000000000000010000000000000070000102000000000E3139322E3136382E302E31313500C5E600000018373334353930383139372F42522D372F0100000000000000000000020000000000000008000000004A41430000000001000000200000000000010001000000010501000100010109000000020501000100010100 -AppServer Adobe-OSGi
13.06.2023 00:09:14.373 *ERROR* [[0:0:0:0:0:0:0:1] [1686629352933] GET /content/forms/af/formdoc/channels/print/jcr:content.treejson HTTP/1.1] com.adobe.forms.aem.impl.XFANativeServiceImpl Exception:
java.lang.IllegalStateException: Connection to failed service.
at com.adobe.service.ResourcePooler.allocateResource(ResourcePooler.java:104)
at com.adobe.service.ConnectionFactoryManagerPeer.getConnectionResourceFromPool(ConnectionFactoryManagerPeer.java:76)
at com.adobe.service.ConnectionFactoryManagerPeerImpl.getConnection(ConnectionFactoryManagerPeerImpl.java:155)
at com.adobe.service.impl.PlatformPeerImpl.lookup(PlatformPeerImpl.java:49) [adobe-aemds-core-bmc:3.0.110]
at com.adobe.forms.aem.impl.XFANativeServiceImpl.paExecute(XFANativeServiceImpl.java:136) [com.adobe.livecycle.adobe-lc-forms-bedrock-connector:8.0.198]
at com.adobe.forms.aem.impl.XFANativeServiceImpl.paExecute(XFANativeServiceImpl.java:481) [com.adobe.livecycle.adobe-lc-forms-bedrock-connector:8.0.198]
at com.adobe.forms.xtg.impl.XMLFormServiceImpl.$anonfun$paExecute$4(XMLFormServiceImpl.scala:177) [com.adobe.livecycle.adobe-lc-forms-core:8.0.198]
at com.adobe.forms.logging.PerfLogger.measure(PerfLogger.scala:60) [com.adobe.livecycle.adobe-lc-forms-core:8.0.198]

Thanks in advance for any help to resolve this issue.

Pulkit_Jain_ · 6/12/23

@NirmalAEM This [0] is a generic issue that indicates that the XMLForm service failed to launch, so did the service work as expected before the OS restart? Could also be related to file system permissions.

Most of the time it boils down to the C++ redistributable issue.

[0]

com.adobe.forms.aem.impl.XFANativeServiceImpl Exception:
java.lang.IllegalStateException: Connection to failed service.

NirmalAEM · 6/13/23

I checked the "C++ redistributable", and attached the installed C++ redistributable snapshot in my machine. It started happening abruptly after restart. Is there an easy way to determine, what is causing this issue? The exceptions are generic.

12.06.2023 12:43:29.048 *WARN* [ProcessResource@76af2bea(name=XMLForm.exe,pid=0) Error Reader] com.adobe.service.ProcessResource Service XMLFormService: Process ProcessResource@76af2bea(name=XMLForm.exe,pid=0) terminated abnormally with error code -1073741515

Any pointer would help. Thanks.

Pulkit_Jain_ · 6/13/23

@NirmalAEM

Got a similar issue reported by another customer. Did you reach out to Adobe support for this issue yesterday?

If not, check for OS level patches (or any other changes) that were applied on the system recently. That will help us narrow down the trigger point of this issue, if the conversion was working earlier.

NirmalAEM · 6/14/23

Yes @Pulkit_Jain_ we created adobe ticket yesterday as it is impacting document generation process. The XMLForm.exe was running and stopped abruptly, after restarting the windows machine. There is automatic update enabled, so we are trying to identify what is blocking the XMLForm process from running.