Archive for October, 2009

LiveCycle ES: SAXParseException: The processing instruction target matching “[xX][mM][lL]” is not allowed

Issue

 If you are attempting to upgrade a LC7 process in Workbench you may encounter the following error related to a SetValue QPAC:

None (Error finding upgrades: org.xml.sax.SAXParseException: 
The processing instruction target matching "[xX][mM][lL]" is not allowed.)

The SetValue QPAC is not upgraded, but other QPACs are upgraded successfully to LC ES components.

Reason

 The error is caused by the presence of the XML declaration <?xml version=”1.0″ encoding=”iso-8859-1″?> at the start of an XPath value in a SetValue expression.  The upgrade tool cannot handle this XML declaration correctly and throws the error.  If you remove this XML declaration manually before upgrading the process, it will upgrade successfully.

Solution

 This issue is fixed in Workbench ES2.  There is a patch available for LC Workbench ES 8.2.1.2, so you can contact enterprise support if you require this patch.

reference: (181105115/2403177)

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

LiveCycle ES: what is the AdobeFnt11.lst file?

The AdobeFnt11.lst file is created by the XMLForm process when CoolType is started and the fonts are enumerated.  The file is used when generating PDF, Postscript, PCL and ZPL output to find the correct fonts for the document content.

If you have added a font and it is not being picked up you can force an update on the file by stopping the XMLForm process (e.g. manually in task manager), deleting the file and then restarting the XMLForm service (e.g. by re-starting the original document generation/conversion process). The AdobeFnt11.lst file will be recreated with all of the new fonts added. Normally you don’t have to do this, as the new font should be located and added automatically.

PDFMM also uses this file, as it deals with PDF files, which also use fonts.

reference: (181025376/2371040)

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

LiveCycle ES: ALC-FDI-001-307: Processing importData operation on source document

Issue

 If you are trying to render a form in Workspace, you may encounter the following exception in the server log:

2007-08-28 16:39:16,604 INFO [com.adobe.livecycle.formdataintegration.server.FormData]
ALC-FDI-001-307: Processing importData operation on source document 182270.
2007-08-28 16:39:16,963 ERROR [com.adobe.livecycle.formdataintegration.client.ImportFormDataException]
ALC-FDI-001-305: Operation aborted: malformed PDF or data.

exception: flex.messaging.MessageException: ALC-WKS-005-028: A problem occurred in the Render Service.
Please review the render orchestration for this process.

This exception can occur especially when you have created a process, dragged an XDP form from the repository in Workbench to the variables view to create a variable.  It will automatically create an xfaForm type variable, and use the Default Render service.

Reason

The Default Render service does not render XDP forms, only PDFs.

Solution

 You must change the render properties manually for the xfaForm variable and choose another render service.

reference: (1568204)

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

LiveCycle ES: values in a LC7 SetValue expression are being lost after a process upgrade

Issue

 After upgrading a process from 7.x to 8.2 in workbench, the value expressions that existed in the 7.x SetValue activity no longer exist and appear as blank assignments in the 8.2 SetValue activity.

Example:

7.x SetValue Settings:

/process_data/myXMLVar = '<node>value</node>'

/process_data/myStringVar2 = 'test string'

/process_data/myXMLVar3 = '<node>value</node>'

8.2 SetValue Settings (post upgrade):

/process_data/myXMLVar = ''

/process_data/myStringVar2 = 'test string'

/process_data/myXMLVar3 = '<node>value</node>'

The upgrade appears to be removing XML based strings (unless escaped).

Reason

 This is a bug in LC 8.2.1.2 and is caused by the loss of XML data encoding:

– encoded XML attribute values are read from the input process action template and decoded during read by Xerces

– decoded values are rewritten as XML elements (not attribute values) and never re-encoded.

– the subsequent symptom is that the unencoded XML data is (rightly) interpreted by an XML parser, but should have been interpreted as text data.

Solution

 This issue will be fixed in Workbench ES2.  There is a patch available for LC ES 8.2.1.2, so contact enterprise support if you require this patch.

reference: (181109986/2403113)

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

LiveCycle ES: ALC-PDG-001-001 Invocation error.

Issue

 If you are using the API for PDFG ES to convert documents to PDF on a localized operating system as outlined in the documentation, you may encounter the following error message:

"Error OCCURRED: ALC-PDG-001-001 Invocation error."

It may also say that the Job settings cannot be found, or are invalid.  Conversion through the PDFG web interface works successfully.

You may be using code similar to:

HtmlToPdfResult result = new HtmlToPdfResult();
result = new GeneratePdfServiceClient(factory).htmlToPDF(
    inputFileName,
    "Standard",
    "No Security",
    null,
    null);

Reason

The names of the settings files for file type (“Standard”), and security settings (“No Security”) as mentioned in the documentation, may have been localized, which explains why the server cannot find the files at run time.

Solution

 Use the localized names for these settings files in your code.  You can check the names for these settings files in the AdminUI > Services > LiveCycle PDFG ES > File Type Settings.

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

Workspace ES: Error 500: Null input provided: Accepted-Language null

Issue

 If you are trying to access Workspace in the internet browser you may receive the following error:

An error occurred determining the locale.

Error 500: Null input provided: Accepted-Language null

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

[2/5/08 16:35:59:984 EST] 0000003f WebApp E [Servlet Error]-[determine-locale]: 
java.lang.IllegalArgumentException: Null input provided: Accept-Language null
at com.ibm.ws.genericbnf.impl.BNFHeadersImpl.appendHeader(BNFHeadersImpl.java:470)
at com.ibm.ws.webcontainer.channel.WCCResponseImpl.addHeader(WCCResponseImpl.java:149)
at com.ibm.ws.webcontainer.srt.SRTServletResponse.addField(SRTServletResponse.java:288)
at com.ibm.ws.webcontainer.srt.SRTServletResponse.addHeader(SRTServletResponse.java:1534)
at javax.servlet.http.HttpServletResponseWrapper.addHeader(HttpServletResponseWrapper.java:202)
at com.ibm.ws.cache.servlet.CacheProxyResponse.addHeader(CacheProxyResponse.java:421)
at com.adobe.workspace.users.DetermineLocale.doGet(DetermineLocale.java:37)

Reason

 The workspace client code uses the browser language settings to control the locale.  Unfortunately, on the client there is no way to ask the browser for that setting.  So as a workaround, the HTML wrapper requests the determine-locale servlet from the server.  The determine-locale servlet simply returns the Accept-Language header that the browser sent.  So the string returned by determine-locale completely depends on the settings and capabilities of the client you hit that servlet from.  In this case, the browser should be sending the ‘Accept-Language’ headers so either the browser did not send this information, or it was stripped along the way.

Solution

 This has been fixed in Lc ES 8.2.1, to correctly handle the situtation where no ‘Accept-Language’ information is received from the browser/server.

reference: (1708975)

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: how to purge old process recordings in Workbench

Information

 Recording information is globally shared by all users.

There is an option in the workbench.ini file that controls the life span of process recordings. It is defined by default as follows:

-Dcom.adobe.workbench.recordings.remove_on_save=false

Changing the default to be ‘true’ would prune away ‘old’ recordings as they get stale.

 

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: how to reset the administrator password for the LC server

Issue

 If you wish to change the administrator’s password for the LiveCycle server you must do it manually in the database.

Reason

 The administrator’s password is the only password stored in the database table EDCPrincipalLocalAccountEntity.

Solution

 To select the correct record run this query:

SELECT uidstring, password, salt
FROM adobe.edcprincipallocalaccountentity A, adobe.edcprincipaluserentity B
WHERE A.refuserprincipalid = b.id AND b.uidstring = ‘administrator';

The values in the salt and password field together constitute the password for the administrator account. On a sample installation where the password for the administrator account was “password” the password field was set to:

TXScDjEEQCzWccUMUdf8wijx/hE=

and the salt field was set to:

JNIBnmos3d0WE9W8oquFIQ==

To reset your password to “password” run this update command to update the two fields in the EDCPrincipalLocalAccountEntity table with the above values and you should be able to login.

UPDATE adobe.edcprincipallocalaccountentity, adobe.edcprincipaluserentity
SET password = ‘TXScDjEEQCzWccUMUdf8wijx/hE=’, salt = ‘JNIBnmos3d0WE9W8oquFIQ==’
WHERE adobe.edcprincipallocalaccountentity.refuserprincipalid = adobe.edcprincipaluserentity.id
AND adobe.edcprincipaluserentity.uidstring = ‘administrator';

You may have to restart the application server for these changes to take affect.

Additional Information

This solution has been verified on a MySQL database with LiveCycle ES 8.0.  The database schema for later versions of LiveCycle ES (8.2.1, 9, 10 etc…), and for other Database types (Oracle, SQL Server) may differ, and may require modifications to the above SQL statements.

In some databases the “edcprincipallocalaccountentity” table does not exist, but is represented by the “edcprincipallocalaccount” table. The information in this technote is provided as-is and should be tested before applying it to a production database.  Performing a full backup of the database before applying any changes is recommended.

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 10.0/10 (2 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)