Posts in Category "General"

LiveCycle ES2: “ImportFormDataException: ALC-FDI-001-305″ importing data to a PDF

Issue

The following exception occurs when you use FormDataIntegration to merge xml data into a prerendered PDF file:

com.adobe.livecycle.formdataintegration.client.ImportFormDataException: 
ALC-FDI-001-305: Operation aborted: Malformed input PDF or data.

Reason

When a PDF form contains a rich-text enabled field with data (default or already merged), the FormDataIntegrationClient can’t import the data. This issue has been identified as a limitation in the AFML library as it presently does not support the tab-interval style attribute.

In the current LiveCycle ES2 documentation, it states that the FormDataIntegrationClient is the preferred way to import data to a PDF form:

http://livedocs.adobe.com/livecycle/es/sdkHelp/programmer/sdkHelp/importingExportingIntro.51.2.html

Adobe Engineering confirms that the Forms service using renderPDFForm is the recommended way to import data, rather than using the FormDataIntegrationClient. Adobe plans to update the documentation to reflect this information.

Solutions

Do one of the following:

  • Place the text in rich-text fields that do not have the tab-interval style attribute.
  • Use the renderPDFForm API from Forms ES2 by setting “Generate Server Appearances” to false.

reference: (181504595/2591446)

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

LiveCycle ES: AdminUI stalled branch list does not show all reported results

Issue

 If you are using the AdminUI for LiveCycle ES to search for stalled branches, you may notice that some of the items are missing from the returned list.  For example in the returned list you may notice the totals report 7 items but only 5 are shown.

Reason

The stalled branches list is compiled from the TB_BRANCH_INSTANCE table in the database.  Any branch that has a sub_status of “-99” should appear in the list in the AdminUI.  If however some of these branch entries refer to processes or actions which do not exist (or have been deleted) from the database, then this list may display the reported behaviour.

To verify this, you should run the SQL statements below on the database.  We would expect that the results returned match the missing entries from the stalled branches list in the adminui.

select * from TB_BRANCH_INSTANCE B
where ( select count(*) from TB_PROCESS_INSTANCE
 where TB_PROCESS_INSTANCE.id=B.PROCESS_INSTANCE_ID)=0
and not B.PROCESS_INSTANCE_ID is null
and B.PROCESS_INSTANCE_ID !=0
and B.SUB_STATUS=-99
order by CREATE_TIME
select * from TB_BRANCH_INSTANCE B
where ( select count(*) from TB_ACTION_INSTANCE
 where TB_ACTION_INSTANCE.id=B.CURRENT_ACTION_INSTANCE_ID)=0
and not B.CURRENT_ACTION_INSTANCE_ID is null
and B.CURRENT_ACTION_INSTANCE_ID !=0
and B.SUB_STATUS=-99
order by CREATE_TIME

Solution

  If either of these statements return some results, then you can fix the entries in the database to prevent the items from being included in the stalled branches totals.  The entires are referring to process/action ids that do not exist in the process/action tables in the database, and so they will never be completed or continued.  This situation can occur if you have been modifying the database using external (not from Adobe LiveCycle) code, or if you are running a 3rd party process purge tool.

If you want to prevent these entries from being reported in the list of stalled branches, then you can change the sub_status value to -1.  If the status value is already 2 (completed) or 4 (terminated) you should change the sub_status to 4.

reference: (181599726)

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

LiveCycle ES: SAXParseException: White spaces are required between publicId and systemId.

Issue

If you have migrated from LiveCycle 7 to LiveCycle ES you may encounter the following exception when attempting to call a web service from an orchestration at runtime:

####<Feb 18, 2010 5:09:56 PM MET> <Warning> <com.adobe.workflow.AWS> <sunc01016> <wl01qalc01> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-56EAC5B49D0141CB0D30> <> <1266509396427> <000000> <ALC-DSC-000-000: com.adobe.idp.dsc.DSCRuntimeException: Internal error. 
...
Caused by: ALC-DSC-000-000: com.adobe.idp.dsc.DSCRuntimeException: Internal error. 
 at com.adobe.idp.dsc.util.CoercionUtil.toDOMDocument(CoercionUtil.java:683) 
 at com.adobe.idp.dsc.util.CoercionUtil.toDOMDocument(CoercionUtil.java:688) 
 at com.adobe.idp.dsc.util.CoercionUtil.toType(CoercionUtil.java:970) 
 at com.adobe.idp.dsc.util.CoercionUtil.toType(CoercionUtil.java:836) 
 at com.adobe.workflow.datatype.runtime.support.AbstractDataTypeRuntimeHandler.coerceFrom(AbstractDataTypeRuntimeHandler.java:64) 
 at com.adobe.workflow.datatype.runtime.support.AbstractComplexDataTypeRuntimeHandler.getNode(AbstractComplexDataTypeRuntimeHandler.java:47) 
 at com.adobe.workflow.dom.VariableElement.setBoundValue(VariableElement.java:98) 
 at com.adobe.workflow.pat.service.PATExecutionContextImpl.setProcessDataValue(PATExecutionContextImpl.java:813) 
 ... 116 more 
Caused by: org.xml.sax.SAXParseException: White spaces are required between publicId and systemId. 
 at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) 
 at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) 
 at com.adobe.idp.dsc.util.DOMUtil.parseDocumentFromString(DOMUtil.java:167) 
 at com.adobe.idp.dsc.util.CoercionUtil.toDOMDocument(CoercionUtil.java:607) 
 ... 123 more

When accessing the web service through the WebService component, you sometimes get a valid response using the test tab:

Solution

The web service is returning an invalid XML result. This error usually happens when the classpath for the server is not correctly set up. Check the classpath against the Adobe documentation, make any necessary changes, and then restart the application server.

In this case, the argument for the UTF-8 charset was not set correctly and therefore the input and output data for the WebService component was not correctly encoded.

reference: (181450296)

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

LiveCycle ES: LinkageError for SOAPMessage class when accessing LC7 WSDL from LC ES

Issue

If you have exposed workflows in LiveCycle 7 as web services and then upgraded to LiveCycle ES, these web services should continue to be available under the same WSDL URL as in LC7: http://<server>:<port>/services/<servicename>?wsdl

Services exposed as web services in LC ES that did not exist in LC7 before the migration are available under the new LC ES WSDL URL path: http://<server>:<port>/soap/services/<servicename>?wsdl

However, you may notice after migrating to ES 8.2.1 that the data connections in your XDP forms are no longer working. Trying to create a new data connection to http://<server>:<port>/services/<servicename>?wsdl doesn’t work either. Trying to load the WSDL in Internet Explorer from the same client machine produces the following error:

####<Jan 26, 2010 6:17:46 PM MET> <Error> <HTTP> <xxxx> <xxxx> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> 
<<WLS Kernel>> <> <> <1264526266913> <BEA-101017> <[weblogic.servlet.internal.WebAppServletContext@1ae8935 - 
appName: 'adobe-livecycle-weblogic', name: '/services', context-path: '/services'] Root cause of ServletException.

java.lang.LinkageError: loader constraints violated when linking javax/xml/soap/SOAPMessage class
 at org.apache.axis.transport.http.AxisServlet.createMessageContext(AxisServlet.java:924)
 at org.apache.axis.transport.http.AxisServlet.processQuery(AxisServlet.java:1185)
 at org.apache.axis.transport.http.AxisServlet.doGet(AxisServlet.java:249)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
 at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)

Solution

This LinkageError is usually caused by the saaj.jar appearing multiple times in the classpath and causing conflicts with older versions. Try to remove the saaj.jar file from the adobe-wkf-service.war in the adobe-livecyle-weblogic.ear file to ensure that it uses the right version of the saaj.jar file.

Follow these steps to verify that the solution works for you:

  1. Make a backup of configurationManager/export/adobe-livecyle-weblogic.ear.
  2. Use Winzip or WinRAR and open adobe-livecyle-weblogic.ear.
  3. Extract the war file adobe-wkf-service.war from the EAR.
  4. Use Winzip or WinRAR to open adobe-wkf-service.war.
  5. Delete saaj.jar from \WEB-INF\lib\.
  6. Add the modified adobe-wkf-service.war back into adobe-livecyle-weblogic.ear using Winzip or WinRAR.
  7. Deploy the modified adobe-livecyle-weblogic.ear to the appserver.
  8. Test WSDL path http://<server>:<port>/services/<servicename>?wsdl again in Internet Explorer and Designer.

If this solution works in your environment, contact Adobe support to request a patch for this issue. This issue has already been fixed in ES2 SP2 (9.0.0.2) and later versions.  A patch is available for LC ES 8.2.1.2, and Adobe support can request this patch for your environment.

reference: (181406184/2541407)

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

LiveCycle ES: JMXBeanManager warning filling up the server log

Issue

If you are using Adobe LiveCycle ES 8.2.1.2 or 8.2.1.3 you may notice that the server logs are filling up with warnings similar to those shown below:

####<Jan 27, 2010 9:27:11 AM MET> <Warning> <com.adobe.idp.dsc.jmx.JMXBeanManager> <sunc01016> <wl01qalc01> 
<[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> 
<1264580831624> <000000> <Failed to get mbean: server1:Type=AdobeService,Name=DirectoryManagerService,version=1.0. 
This message is a warning only. It should not impact LiveCycle's invocation>

####<Jan 27, 2010 9:27:11 AM MET> <Warning> <com.adobe.idp.dsc.jmx.JMXBeanManager> <sunc01016> <wl01qalc01> 
<[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> 
<1264580831649> <000000> <Failed to get mbean: server1:Type=AdobeService,Name=DirectoryManagerService,version=1.0. 
This message is a warning only. It should not impact LiveCycle's invocation>

####<Jan 27, 2010 9:27:11 AM MET> <Warning> <com.adobe.idp.dsc.jmx.JMXBeanManager> <sunc01016> <wl01qalc01> 
<[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> 
<1264580831694> <000000> <Failed to get mbean: server1:Type=AdobeService,Name=DirectoryManagerService,version=1.0. 
This message is a warning only. It should not impact LiveCycle's invocation>

This warning is harmless and can be ignored, however it can lead to the log files growing exponentially.

Solution

This issue is fixed in LiveCycle ES2 (9.0.0.0). Patches are available for LiveCycle ES SP2 (8.2.1.2) and LiveCycle ES SP3 (8.2.1.3). Contact enterprise support if you require one of these patches to ensure that they are compatible with your environment.

reference: (181407992/2540696)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 8.0/10 (1 vote cast)

LiveCycle ES: “Documents in this folder are not available” trying to access the repository through WEBDav

Issue

If you are using WEBDAV (i.e. web folders) to access your forms and resources in the repository you may encounter the following error in Windows Explorer:

"Documents in this folder are not available.  They may have been moved or deleted, or network problems may be preventing a connection to the server."

This error occurs when some of the folders in the repository contain spaces, so the spaces get replaced with “+” characters for the standard URL encoding.  Internet Browsers are able to handle this URL encoding and you can access the folders and files, however WEBDAV cannot handle these URL encoded folder paths.

Solution

 If there are spaces in the folder names, and they are displayed as “+” characters in the WEBDAV folder view, then you can workaround the behaviour temporarily by just renaming the folder and removing the “+” characters.  Then you will be able to browse into the folder.  This will revert back to the folder name with “+” characters when you re-connect to the WEBDAV folder.

The other option would be to link the WEBDAV folder directly to the problem folder (i.e. the one with the “+” characters), instead of linking to the repository root.  This would require a WEBDAV folder entry for each problem folder in the repository, which may not be realistic depending on how many folders you have.

The ultimate solution here is to get the patch which addresses this issue in the LiveCycle repository.  The issue has been fixed in LC ES SP4 (8.2.1.4), ES3 (10) and later versions.  Please contact Adobe enterprise support if you require this patch, to ensure you get a version that will work on your platform and LC version.

Additional information

 WEBDAV refers to the method of setting up a Network Location pointing directly to the LiveCycle repository on the LiveCycle server as follows:

1. goto network places

2. add location

3. http://<LCServer_ip_address>:<port>/repository

4. enter LiveCycle credentials for WEBDAV folder (e.g. administrator:password)

5. open WEBDAV folder

reference: (181280536/2526842)

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

LiveCycle ES: XmlException: error: Invalid byte 1 of 1-byte UTF-8 sequence

Issue

 If you are trying to import an LCA archive in LiveCycle ES adminui, you may encounter the following error:

Error previewing archive: 'org.apache.xmlbeans.XmlException: error: Invalid byte 1 of 1-byte UTF-8 sequence.'

This error may be accompanied by the following exception in the server log:

SEVERE: OrchestrationImportExportHandler:previewApplicationComponent:Exception: 
org.apache.xmlbeans.XmlException: error: Invalid byte 1 of 1-byte UTF-8 sequence.

2008-01-10 09:21:20,380 INFO [STDOUT] Jan 10, 2008 9:21:20 AM 
com.adobe.repository.ui.aac.struts.actions.CommandProcessorAction execute

SEVERE: Application Administration Console: Error previewing archive: 
'org.apache.xmlbeans.XmlException: error: Invalid byte 1 of 1-byte UTF-8 sequence.

'com.adobe.repository.ui.aac.AacException: Error previewing archive: 
'org.apache.xmlbeans.XmlException: error: Invalid byte 1 of 1-byte UTF-8 sequence.

Reason

 This is a bug in LiveCycle ES 8.0.1.  If you are using quotation characters in the process XML, in the Task Instructions for example, these characters are not being handled correctly when exporting the XML for the LiveCycle archive file.  The encoding on the XML beans parser is not configured correctly.

Solution

 This issue has been resolved in LC ES 8.0.1 SP3 ( 8.0.1.3) and later versions.

reference: (1670330)

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

LiveCycle ES: ServiceConfigurationNotFoundException version 1.0 not found

Issue

 If you are trying to call a particular service on the LiveCycle server (e.g. renderPDFForm from the Forms service), you may encounter an error similar to the following :

ALC-DSC-013-000: com.adobe.idp.dsc.registry.ServiceConfigurationNotFoundException: Service Configuration : FormsService version: 1.0 not found
at com.adobe.idp.dsc.registry.service.impl.ServiceRegistryImpl.getServiceConfiguration(ServiceRegistryImpl.java:928)
at com.adobe.idp.dsc.registry.service.impl.ServiceRegistryImpl.getHeadActiveConfiguration(ServiceRegistryImpl.java:834)
at com.adobe.idp.dsc.engine.impl.ServiceEngineImpl.resolveConfiguration(ServiceEngineImpl.java:146)
at com.adobe.idp.dsc.provider.impl.ejb.receiver.EjbReceiverBean.invoke(EjbReceiverBean.java:126)
at com.adobe.idp.dsc.provider.impl.ejb.receiver.EJSRemoteStatelessInvocation_b542628e.invoke(Unknown Source)
at com.adobe.idp.dsc.provider.impl.ejb.receiver._EJSRemoteStatelessInvocation_b542628e_Tie.invoke(_EJSRemoteStatelessInvocation_b542628e_Tie.java:160)
at com.adobe.idp.dsc.provider.impl.ejb.receiver._EJSRemoteStatelessInvocation_b542628e_Tie._invoke(_EJSRemoteStatelessInvocation_b542628e_Tie.java:88)

Reason

 This error occurs primarily when the service is not running.  You can check the service state in the AdminUI.  If you have setup the application server and database to start on boot, it may occur that the application server has started before the database service.

Solution

 Set priorities for the services in the operating system boot settings to ensure the database service starts first.

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

LiveCycle ES: javax.mail.MessagingException: Could not connect to SMTP host: <hostname>, port: 25

Issue

 If you are trying to send a mail from a process in LiveCycle ES, you may encounter the following exception in the log:

java.lang.RuntimeException: javax.mail.MessagingException: Could not connect to SMTP host: <hostname>, port: 25;
nested exception is:
java.net.SocketException: Software caused connection abort: connect

Reason

 If you are using Virus Scanner software they often block port 25 to prevent worm-type mass mailings.  In McAfee for example, you can verify this if you bring up the VirusScan Console and look at the Access Protection Task. Check the properties for the port settings.

Solution

 You should disable any anti-virus checks on port 25.

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

LiveCycle ES: troubleshoot POP/SMTP email servers

Troubleshoot SMTP server

If you are having problems connecting/using an SMTP server with LiveCycle, you should manually check that you can indeed connect and send e-mails by issuing the following set of commands on the server you want to connect from.

In this example, assuming you want to troubleshoot the connection to the SMTP server mail.company.com from a Windows server, you would issue the following from a command prompt:

cmd> telnet mail.company.com 25   
220 mail.company.com ESMTP Sendmail 8.13.3/8.13.3; Fri, 3 Mar 2006 17:22:29 GMT  
helo mydomain.com  
250 mail.company.com Hello bla-dhcp-206.company.com [<ip address>], pleased to meet you  
mail from: someone@mydomain.com  
250 2.1.0 someone@mydomain.com&hellip; Sender ok  
rcpt to: support@mail.company.com  
250 2.1.5 support@mail.company.com&hellip; Recipient ok  
data  
354 Enter mail, end with '.' on a line by itself  
Text of the message .  
250 2.0.0 k23HMTO3006628 Message accepted for delivery  
quit  
221 2.0.0 mail.company.com closing connection 
Connection to host lost.  
cmd>

Preferably you should attempt to use the same e-mail addresses for the sender and recipients as the one that are meant to be used by your application.  If any of the operations above fail, it means that the problem is NOT with your application, but with the SMTP server itself.  If it works, then you should try the same from a remote host, to see if your issue might have to do with a firewall or some network issue.

If you don’t get any errors when doing these 2 operations, then it means that your server is properly set to send email, so now you can switch to troubleshooting POP.

Troubleshoot POP server

 The POP3 manual commands are almost as easy as the SMTP commands. To check your mail with POP:

cmd> telnet popserver.somedomain.com 110
user <some_valid_user>
pass <user_password>
stat

Each of these commands should return “+OK”.  The “stat” command should also return 2 numbers indicating the number of new messages received, and messages left on the server.

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