Posts in Category "LiveCycle"

LiveCycle Designer ES2: Designer hangs after renaming the binding file

Issue

While editing an XDP in certain versions of LiveCycle Designer ES2, if the data binding file on disk is renamed, designer registers this change and offers to reload the current form.  If you then click Save, it again offers to reload the current form.  After clicking “Yes” to reload the form, you may notice that Designer hangs.

Method:
1. Download test_files.zip
2. Extract the 2 files to the same local folder
3. Open XDP in Designer
4. Rename the binding XML file in your local folder
5. You will see a dialog in Designer asking to reload the form, click Yes
6. Click Save
7. Again the dialog in Designer asking to reload the form, click Yes

Result:
Designer hangs

Solution

This is an issue in certain versions of LiveCycle Designer ES2 and has been addressed in later versions, including Designer ES3.  If you require a quickfix for this issue in LiveCycle Designer ES2 you should contact the enterprise support team.

reference: (183667516/3337854)

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

LiveCycle Designer ES2: Multiple pages imported to a single Master Page causing overlap

Issue

If you are importing a multi-page PDF into LiveCycle Designer ES2 to create a form using the “…Flowable Layout > Place Content In > Master Pages” method you may notice that the content of the pages are placed in a single Master page causing overlap.

Solution

This is an issue in LiveCycle Designer ES2 and has been addressed in later versions, including Designer ES3.  If you require a quickfix for this issue in LiveCycle Designer 9 you should contact the enterprise support team.

reference: (183629724/3337453)

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

LiveCycle Designer ES2: Corners appear unexpectedly when clicking on hidden rectangle object

Issue

If you are editing older XDP forms from LiveCycle Designer 7.1, or 8,  in Designer ES2, and you have hidden rectangle objects in the form design, you may notice that when selecting these hidden objects in the hierarchy, visible corners suddenly appear on these objects.  These hidden rectangle objects are created automatically when importing Word documents into Designer to create a form.

Reason

The problem is caused by the import from doc/PDF where the edge property for the rectangle is created and set to hidden, but no corners property is created.  When you create a new form in Designer (without importing), the edge and corner properties for a rectangle are always created together and the presence for both usually kept in synch.
It seems that when Designer finds a rectangle without a corner property it creates it automatically with visible corners.

Rectangle in XML after import from word:
               <rectangle>
                  <edge thickness=”0pt” presence=”hidden”/>
               </rectangle>

Rectangle in XML after selecting it on canvas:
               <rectangle>
                  <edge thickness=”0pt” presence=”hidden”/>
                  <corner radius=”5.08mm”/>
               </rectangle>

Rectangle in XML after manually fixing it in Designer (XML Source or Object Palette):
               <rectangle>
                  <edge thickness=”0pt” presence=”hidden”/>
                  <corner radius=”5.08mm” presence=”hidden”/>
               </rectangle>

Workaround

You can change the line style to “solid” and back to “none”, and then the corners property in XML is synchronized (presence=hidden) with the line edge property as expected.

Solution

This is an issue in LiveCycle Designer ES2 and will be fixed in Designer 10 and later versions.  If you require a quickfix for Designer 9 you should contact the enterprise support team.

The logic has now been changed, so that when Designer creates the corner property, it checks if the relevant edge is hidden, and sets the presence for the corners to match.

reference: (183589079/3322036)

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

LiveCycle ES: AccessDeniedException: Access Denied. The system is currently in read-only mode.

Issue

If you are using LiveCycle Content Services you may notice the following error message in the server logs when starting the server:

00:05:55,646 ERROR [org.alfresco.service.descriptor.DescriptorService] Error installing embedded license
org.alfresco.service.license.LicenseException: Failed to save license
                at org.alfresco.repo.descriptor.RepositoryDescriptorDAOImpl.updateLicenseKey(RepositoryDescriptorDAOImpl.java:294)
                at org.alfresco.enterprise.license.AlfrescoLicenseManager.setLicenseKey(AlfrescoLicenseManager.java:220)

Caused by: org.alfresco.service.cmr.repository.ContentIOException: Failed to create directory for file storage: \\share\Adobe\lccs_data\contentstore\2012\10\26\0\5
                at org.alfresco.repo.content.filestore.FileContentStore.makeDirectory(FileContentStore.java:288)
                at org.alfresco.repo.content.filestore.FileContentStore.createNewFile(FileContentStore.java:234)
                at org.alfresco.repo.content.filestore.FileContentStore.createNewFile(FileContentStore.java:202)
                at org.alfresco.repo.content.filestore.FileContentStore.getWriterInternal(FileContentStore.java:478)
                at org.alfresco.repo.content.AbstractContentStore.getWriter(AbstractContentStore.java:242)
                at org.alfresco.repo.content.RoutingContentService.getWriter(RoutingContentService.java:402)
                at org.alfresco.repo.descriptor.RepositoryDescriptorDAOImpl.updateLicenseKey(RepositoryDescriptorDAOImpl.java:285)
                … 15 more
03:00:00,020 ERROR [org.quartz.core.JobRunShell] Job DEFAULT.indexBackupJobDetail threw an unhandled Exception:
org.alfresco.repo.security.permissions.AccessDeniedException: Access Denied.  The system is currently in read-only mode.

Reason

This error can occur when the user account that started the application server (JBoss/WebSphere/Weblogic) no longer has “write” permissions on the lccs_data shared directory used by content services (alfresco).

During startup sequence, Alfresco tries to create files in lccs_data shared directory, and if it cannot, it starts content services in read only mode.

Solution

Verify the user rights on the shared lccs_data directory, and try to create a folder/file manually.  Restarting the LiveCycle server will usually resolve the problem, but you should investigate the root cause why the user permissions are being lost in your environment.

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

LiveCycle Designer ES2: Unable to delete default value in rich-text fields

Issue

After updating to LiveCycle Designer ES2 QF4 (9.0.0.2.20110401.1.827986), you may notice that you are no longer able to delete the default value in rich-text fields.  It is possible to edit the value, but when you delete it, the value will re-appear in the field after refreshing.  This only happens for rich-text fields and not standard text fields.

Solution

This is an issue in LiveCycle Designer 9.5 QF4 and has been addressed in later versions, including Designer 10.  If you require a quickfix for this issue in LiveCycle Designer 9 you should contact the enterprise support team.

Workaround

You can delete the default value by opening the XML Source tab and removing the value manually.

reference: (183571067/3318438)

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

LiveCycle ES3 SP1: Gemfire errors in server log after installing patches on top of 10.0.2

Issue

If you are using TCP locators in a LiveCycle cluster with ES3 (10.0.2) and have installed a service pack or patches on top of this version, you may notice some errors in the server log similar to the following:

com.adobe.livecycle.cache.CacheRuntimeException: Error loading cache configuration
at com.adobe.livecycle.cache.adapter.GemfireCacheAdapter.getCacheContainer(GemfireCacheAdapter.java:164)
at com.adobe.livecycle.cache.adapter.GemfireCacheAdapter.createRootRegion(GemfireCacheAdapter.java:853)
at com.adobe.livecycle.cache.adapter.GemfireCacheAdapter.init(GemfireCacheAdapter.java:218)
at com.adobe.livecycle.cache.adapter.GemfireCacheAdapter.<init>(GemfireCacheAdapter.java:207)
at com.adobe.livecycle.cache.adapter.CacheAdapterFactory.getCache(CacheAdapterFactory.java:103)

Caused by: com.gemstone.gemfire.SystemConnectException: Attempt to connect to distributed system timed out

If you have a UDP-based cluster caching mechanism, you are not affected by this issue.

Reason

This issue occurs when the Gemfire version on the server is different from the Gemfire version used by the TCP locators.  Gemfire.jar and GemFireVersion.properties are delivered in two different places in the LC installation – 1. Core EAR 2. /lib/caching directory.

Gemfire version 6.5.1.17 was used for LC ES3 (10.0.2).  To address some known issues a new Gemfire version (6.5.1.35) was used in later versions and patches.  This newer Gemfire version was used for the Core EAR, but unfortunately not included for updating the caching directory.

To verify the issue, compare the Gemfire version in the GFLocator.log file for your TCP Locator with the Gemfire version in the Gemfire logs for your application server at the following location:

  • JBoss: <adobe_temp_dir>/adobejb_<server_name>/caching/Gemfire.log
  • Weblogic: <adobe_temp_dir>/adobewl_<hostname>/caching/Gemfire.log
  • WebSphere: <adobe_temp_dir>/adobews_*/caching/Gemfire.log

You will find that Gemfire on the LiveCycle server has a higher version.

Solution

This issue has been addressed in SP2 and later patch versions.

Note: the patch installer will only update the default caching directory (<lc_install_dir>/lib/caching) on the machine where LC is installed.  If you are running LC on various machines, and/or use custom caching directories, you will need to update the 2 Gemfire files for your TCP locators manually.  All TCP locators need to be restarted before starting LC servers.

Workaround

For existing patches you can use the following workaround to fix the issue on your LiveCycle installation.

  1. Stop the LiveCycle server(s).
  2. Stop the TCP Locator(s).
  3. Go to <LC_INSTALL_DIR>/deploy folder.
  4. Open adobe-core-<appserver_name>.ear.
  5. Go to TCP locator installation directory. Typically the default location is <LC_INSTALL_DIR>/lib/caching.
  6. gemfire.jar and GemFireVersion.properties can be found here.
  7. Replace the two files above in the TCP locator with the same files from the core ear.
  8. Repeat the replacement procedure (steps 5 – 7) for each TCP locator.
  9. Start TCP Locator(s).
  10. Start LiveCycle server(s) in the Cluster.

Verify the Gemfire versions in GFLocator.log and Gemfire.log files. You should see the same Gemfire version in both files.

reference: (183615151/3327651)

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

LiveCycle Designer ES2: Word (version XP or onwards) could not be found on the machine

Issue

If you are using LiveCycle Designer ES2 to import Microsoft Word documents from MS Word 2010 or later, you may receive the following error

Word (version XP or onwards) could not be found on the machine

Reason

This error occurs because LC Designer ES2 does not recognise the installation folder for Microsoft Word 2010 or later versions.  LiveCycle Designer ES2 was released before these versions existed and therefore the installation folders were not known/recognised.

Solution

This issue has been fixed in LiveCycle Designer ES3 and last cumulative QuickFixes (QF) for Designer ES2.  Ensure you are using the latest QF for Designer ES2, or request the latest from your support representative.

If you require an urgent fix for this issue you can make the following change in the registry:

Note: we cannot provide support for any problems that may arise as a result of modifying the registry.  Only an experienced user or an administrator should attempt this, and a full registry backup should be performed before making changes.

1. For 32-bit Windows:

  • Create the following path in the registry:
    • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\12.0\Word\InstallRoot
  • Create a new string value named Path with value C:\Program Files\Microsoft Office\Office14\

2. For 64-bit Windows

  • Create the following path in the registry:
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\12.0\Word\InstallRoot
  • Create a new string value named Path with value C:\Program Files (x86)\Microsoft Office\Office14\

You should check the installation folder used in the Path value exists and contains WINWORD.EXE.  You will need to restart LiveCycle Designer for the changes to take effect.

Additional information

This issue is also being discussed in the forums:

http://forums.adobe.com/message/3983628

reference: (183608560/2751566)

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

LiveCycle Designer ES2: Unable to save old XDPs with external data binding option

Issue

If you are attempting to save an XDP file in LiveCycle Designer ES2, created with an earlier version of Designer (i.e. 7, 7.1 or ES), then it can occur that the Save process never completes, and you must kill the Designer process manually in Task Manager.  If you analyse the files on your local disk, you will notice some tmp files with large file sizes.

Reason

This issue is related to the Data Binding option Allow binding to data not defined by the default data connection.  For some forms that contain data connections, Designer ES2 can get stuck in an endless loop while saving the XDP to an intermediary tmp file.  You will see the tmp file will contain a huge number of repeated entries related to the DataDescription similar to the following:

<DATACONNECTION xmlns:dd=”http://ns.adobe.com/data-description/” dd:additions=”$template(DATACONNECTION)”/>

Solution

This issue has been fixed in LiveCycle Designer ES3 and later cumulative QuickFixes for Designer ES2.  You should ensure you are using the latest QF for Designer ES2, or contact your support representative.

Workaround

Removing the data connection will allow the file to be saved, and also disabling the option in the form properties Allow binding to data not defined by the default data connection.  Also putting the sample XML data/schema file used to create the data connection into the same folder as the XDP, opening the XDP, refreshing the Data connection, will then allow to save properly.

reference: (183464630/3296440)

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

LiveCycle ES: ALC-PDG-001-001 The Job Configuration either cant be obtained or is invalid

Issue

If you are using PDFG to process documents on your LiveCycle server you may encounter problems with the conversions accompanied by the following exception in the server log:

GeneratePDFIm A com.adobe.pdfg.logging.PDFGLogger log ALC-PDG-001-000-Job ID for the submitted createPDF job =CreatePDF-2012-07-23 12-05-26.643.docdfaed6-f564cb-14cb09-338b02-c5fd79-ba0c90

GeneratePDFIm E com.adobe.pdfg.logging.PDFGLogger log ALC-PDG-001-000-ALC-PDG-001-001-The Job Configuration either cant be obtained or is invalid.  Invocation error.

AWS  E com.adobe.workflow.engine.PEUtil logFailedFaultRouting An exception was thrown with name com.adobe.livecycle.generatepdf.client.InvalidParameterException message:ALC-PDG-001-001-The Job Configuration either cant be obtained or is invalid.  Invocation error while invoking service GeneratePDFService and operation CreatePDF2 and no fault routes were found to be configured.

WorkflowDSCIn E com.adobe.idp.workflow.dsc.invoker.WorkflowDSCInvoker logFailedFaultRouting An exception was thrown with name com.adobe.livecycle.generatepdf.client.InvalidParameterException message:ALC-PDG-001-001-The Job Configuration either cant be obtained or is invalid.  Invocation error. while invoking service GeneratePDFService and operation CreatePDF2 and no fault routes were found to be configured.

JobManagerBea E com.adobe.idp.jobmanager.ejb.JobManagerBean doOnMessage JobManagerBean:onMessage():Exception:ALC-DSC-003-000: com.adobe.idp.dsc.DSCInvocationException: Invocation error.  Reference     I org.apache.xml.security.signature.Reference verify Verification successful for URI “#d6f16633df10d6efd649f0d2becce92c”

FileResultHan A com.adobe.idp.dsc.provider.service.file.write.impl.FileResultHandlerImpl tryPreservingFiles FileResultHandlerImpl —– preserved- source —-\\server\WatchedFolders\folder\stage\Wx840560ff8bdc142771fc0a18\CreatePDF-2012-07-23 12-05-26.643.doc— to —\\server\WatchedFolders\folder\failure\CreatePDF-2012-07-23 12-05-26.643\CreatePDF-2012-07-23 12-05-26.643.doc

Reason

PDFG uses file settings to specify what type of PDF file you would like to be generated.  These settings are stored in the LiveCycle server and can be referenced in the AdminUI:

http://livedocs.adobe.com/livecycle/8.2/admin_pdfg/000006.html

This exception occurs when you are converting files using the API, an orchestration, or a custom service, but the settings you have defined do not exist on the LiveCycle server.  This may happen if you have custom conversion settings and then deploy an application/process, which references these settings from one environment to another.  We have also seen this issue when the name of the conversion settings was localized (as LiveCycle was installed on a non-English OS), and therefore the name defined in the service by default was no longer valid.

Solution

You should check your code or custom service to ensure you are referencing a valid PDFG settings file.  You may need to import a settings file in the adminUI, if you use custom settings in your code/service.

reference: (183454350)

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

LiveCycle ES2: XMLForm.exe terminated abnormally with error code {3}

Issue

If you are using LiveCycle to process PDF documents you may encounter problems displaying/converting forms or PDF documents, accompanied by exceptions similar to the following in the server log:

ProcessResour W com.adobe.service.ProcessResource doProcessExitCleanup BMC024: Service XMLFormService: Process ProcessResource@f1f45(name=XMLForm.exe,pid=0) terminated abnormally with error code {3}

XMLFormAgentW E com.adobe.livecycle.formsservice.logging.FormsLogger logMessage ALC-OUT-002-004: Unable to find service: XMLFormService, error: Connection to failed service.

Solutions

The error message “XMLForm terminated abnormally with error code {3}” can occur in various situations, and the relevant solutions are described below.

1. The LiveCycle font directory is not valid

In this situation you should see a warning or error in the server log during startup similar to the following:

FontManager   E com.adobe.fontmanager.FontManager loadFromFontDirectories ALC-FMR-001-009:FontManager: Null/Non-existent font directory : /opt/server   /resources/fonts

When configuring LiveCycle you can enter a directory where fonts are stored and can be used by LiveCycle.  If this directory is not valid when calling XMLForm it can result in the error code {3}.

You can modify the location of the font directories in the administration console under Settings > Core System Settings > Configurations.  You will need to restart the application server after modifying these settings.

Further details here:

http://help.adobe.com/en_US/livecycle/9.0/adminHelp/admin.htm?content=000006.html

2. The LiveCycle root directory contains “null” in the path

This can occur particularly on Weblogic installations.  You should explicitly set the path using -Dadobeidp.RootDirectory=<path> in the server startup script.

Further details available here:

http://blogs.adobe.com/dmcmahon/2009/05/10/livecyclees-the-application-has-failed-to-start-because-omnidynamic403_rt-dll-was-not-found/

3. Solaris 10 Update 10 has been applied

If you have recently applied Solaris 10 Update 10 XMLForm may start failing with error code {3}.  There is a compatibility issue between the compiler settings that Adobe uses to compile the XMLFormService and some additions that Oracle have made to Solaris to support GNU extensions to their ELF symbol versioning.  What this means is that Solaris no longer recognizes XMLFormService as a valid executable and will not run it.

The best solution here is to update Solaris to a more recent version that contains the fix.  Details on exact versions can be attained from Oracle.

A workaround is to disable the run-time linker check by removing the DT_VERSYM entry from the objects dynamic section in libstdc++.so.6.

To apply the workaround you should run the following command on the libstdc++.so.6 file found in ServicesNatives2/lib directory:

% elfedit -e 'dyn:delete versym' libstdc++.so.6 libstdc++.so.6-alt

The workaround should only be applied by a sysadmin in critical situations, as it is a system change that may cause other side-effects.  You should make a backup of the original file before making that change.  Further details here: https://forums.oracle.com/forums/thread.jspa?threadID=2294952

You can find further details here:

http://helpx.adobe.com/livecycle/kb/xmlformservice-terminates-error-code-3.html

4. WebSphere global security is turned on

In this situation you will most likely see the following exception also in the server log:

CSIServerRIBa W   JSAS0638E: [com.ibm.org.omg.CORBA._ObjectStub.signalStringValue] Client authentication required at the server but no principal information is present in the <server>:<port> method request from client {2}.

We have seen this issue occur when strict global security was turned on in WebSphere and the clientcertificateauthentication for the csiv2inbound property in the WebSphere configuration was set to “Required” instead of “Supported”, and when the transport was set to “SSLRequired” instead of “SSLSupported”.  Change these to “Supported”, as shown below, to resolve this issue.

<csiv2inbound basicauthentication=”Supported” clientcertificateauthentication=”Supported” identityassertion=”false” stateful=”true” transport=”SSLSupported” sslconfigalias=””/>

<csiv2outbound basicauthentication=”Supported” clientcertificateauthentication=”Supported” identityassertion=”false” stateful=”true” sessiongcinterval=”300000″ sessiongcidletime=”900000″ transport=”SSLSupported” sslconfigalias=””/>

Further details here:

http://blogs.adobe.com/livecycle/2012/05/livecycle-xmlforms-native-process-and-websphere-global-security.html

5. SELinux security is in “enforcing” mode

If LiveCycle is running on a server where NSA Security Enhanced Linux (SELinux) is in enforcing mode, XMLForm will terminate with error code {3}.

To correct this problem, change SELinux security to permissive mode.

6. Other native library problems

To investigate native library problems you should enable debugging on the XMLForm process as follows:

  • On Unix/Linux deployments locate <XMLFormService/bin>/XMLForm.exe shell script and edit using a text editor.
  • Navigate to end of the file and you should see an “exec” line.
  • Modify “exec” line to include Corba debug parameters and add ldd/env commands before “exec” line as shown below.
 ldd $myPath/bin/XMLForm > /tmp/XMLForm.ldd_dump.txt
 env > /tmp/XMLForm.env_dump.txt
 exec $myPath/bin/XMLForm $* ORBtraceLevel 40  -ORBtraceThreadId 1
  • After that either restart your app server or kill XMLForms process instance(s) if running.
  • Render a form using FormsService or OutputService and new instance of XMLForms process should get launched.
  • Analyze the ldd_dump.txt, env_dump.txt, StdOut and StdErr logs looking for errors related to loading native shared libraries and/or Corba debug messages.

You can find further details on debugging in XMLForm here:

http://blogs.adobe.com/livecycle/2011/11/debugging-form-rendering-issues-related-to-xmlforms-native-process.html

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

LiveCycle ES2: This scheduler instance (SchedulerName) is still active but was recovered by another instance in the cluster

Issue

If you are working with LiveCycle ES2 in a cluster you may notice the following message in the server log:

org.quartz.impl.jdbcjobstore.JobStoreSupport findFailedInstances “This scheduler instance (<SchedulerName>) is still active but was recovered by another instance in the cluster. This may cause inconsistent behavior”.

Reason

This exception often occurs when the clock times on the cluster nodes are not synchronized.  If the clock times on cluster nodes are more than 1.7 seconds out of synch you will start to see these Quartz messages in the log.

Solution

Synchronize the time on all cluster nodes and then restart the cluster.  The messages should no longer appear in the log.

reference: (1647846)

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

LiveCycle ES3: CertificateException: Terminating SSL connection – The server is not trusted

Issue

If you are using LiveCycle ES3 Digital Signatures to apply signatures to PDF documents using a timestamp (TSP) server you may encounter the following exception:

WARN  [com.adobe.livecycle.signatures.pki.client.PKIException] (http-0.0.0.0-8080-7) Exception from transport package   (in the operation : internalSendReceive)

Caused By: java.security.cert.CertificateException: Terminating SSL connection – The server is not trusted(Alerts.java174)

Caused By: Terminating SSL connection – The server is not trusted(PKISocketFactory.java255)

Reason

This exception will occur if the TSP server is configured to use SSL, i.e. with a HTTPS URL, and the relevant certificate from the TSP server is not found in the LiveCycle Trust Store.  In this case the connection to the TSP server is ignored by LiveCycle as it is not configured correctly, and the signature on the PDF will be applied using the local time from the LiveCycle server machine.

Solution

You will need to import the certificate from the TSP server into the LiveCycle Trust Store (AdminUI > Settings > Trust Store Management > Certificates > Import).

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

LiveCycle ES3: PKIException: ALC-DSS-310-033 Invalid timestamp mime type

Issue

If you are using LiveCycle ES3 Digital Signatures to sign PDF files using a timestamp server (TSP) you may encounter the following exception:

2012-06-22 06:48:31,608 WARN  [com.adobe.livecycle.signatures.pki.client.PKIException] (http-0.0.0.0-8080-7) ALC-DSS-310-033 Invalid timestamp mime type. (in the operation : createTimestamp)

Reason

This exception occurs when the TSP server does not return a response with the expected mime-type.  LiveCycle assumes that the TSP servers conform to the standards defined in RFC-3161 (http://www.ietf.org/rfc/rfc3161.txt).  According to this RFC the mime-types for communicating with TSP servers should be

application/timestamp-query
application/timestamp-reply

Solution

You should use a TSP server that conforms to RFC-3161 when integrating with LiveCycle Digital Signatures.

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

LiveCycle: JBoss stopped logging in server.log

If you have installed LiveCycle in a JBoss application server the server activity will normally be logged in:

<JBOSS_HOME>\server\<profile>\log\server.log

If the JBoss log is no longer logging activity you should check the following:

1. Log4J

The jboss-log4j.xml file is located in <JBOSS_HOME>\server\lc_turnkey\conf and controls logging in JBoss.  If there is any problem with this file then logging may stop working.  You can download this file (jboss-log4j-working) from a fresh LiveCycle installation on JBoss and replace the original (make a backup first).  Restart JBoss after swapping the log4j file and logging should switch to the server1.log file.

2. User account

If you are starting JBoss using a Windows service ensure that the user account used for the service has administrative privileges.  See the installation documentation for further requirements such as disabling UAC on Windows.

reference: (183305796)

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