Posts tagged LiveCycle

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

0
332 days
by in LiveCycle Enterprise Suite

- David McMahon, Senior Technical Account Manager @ Adobe

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)

---

Read the complete post @ David's blog.

LiveCycle: JBoss stopped logging in server.log

0
333 days
by in LiveCycle Enterprise Suite

- David McMahon, Senior Technical Account Manager @ Adobe

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:

---

Read the complete post at David's blog.

Windows Service For TCP Locator

0
334 days
by in LiveCycle Enterprise Suite

- Pankaj Parashar, Lead Software Engineer @ Adobe

In most Windows server environments, users want software running as Windows services that are configured to auto-start and auto-stop on Windows start and stop. So far the LiveCycle provided TCP Locator is started using startlocator.bat script on the Windows environment. There is no inbuilt mechanism to start TCP Locator as a Windows service. However, there are various free tools available for creating Windows service for Java Applications. YAJSW (Yet Another Java Service Wrapper) is one such tool that wraps a Java process and runs it as a Windows service. YAJSW is an LGPL licensed tool.

---

Read the complate post at Adobe LiveCycle Blog.

JBoss Cluster Discarding Messages

0
334 days
by in FAQ, LiveCycle Enterprise Suite

- Pankaj Parashar, Lead Software Engineer @ Adobe

Sometimes while running LiveCycle on JBoss Cluster, you may see the following log messages appearing in server logs. WARN [org.jgroups.protocols.UDP] discarded message from different group “DefaultPartition” (our group is “LIVECYCLE-CLUSTER”). Sender was 10.56.78.90:54356

---

Read the complete post at Adobe LiveCycle Blog.

Quick way to run multiple Jboss 5.x instances on single machine

0
338 days
by in LiveCycle Enterprise Suite

- Santosh Tatke, Sr. Support Architect @ Adobe 

Use Case:

Often times one runs into use cases where you need to run multiple Jboss instances on same machine. E.g. If you are installing LiveCycle ES3 Correspondence Management solution. It needs two different app server instances for author and publish instance.

Obvious problem  you may run into is port conflicts. Known way of dealing with port conflicts is by manually changing Jboss config files.

Well, not anymore.

---

Read the complete post at Adobe LiveCycle Blog.

Unable to Create new application in workbench

0
338 days
by in LiveCycle Enterprise Suite

- Pankaj Gakhar, Software Engineer @ Adobe

You may receive the below error while creating an application in workbench:-

Failed to create application, please check if application name contains invalid string.

This is because the service provider has been changed to a value other thanRepositoryProviderService. Restore it back and you’ll be able to create applications in workbench.

---

Read the complete post at Adobe LiveCycle Blog.

Adobe LiveCycle Forms Integration with SharePoint

0
339 days
by in LiveCycle Enterprise Suite

- Pankaj Gakhar, Software Engineer @ Adobe

This post assumes that you have already installed LiveCycle server containing Forms and SharePoint Connector modules and also configured the web part for livecycle connector for sharepoint on the SharePoint server.

A sample livecycle archive adobe-formintegrationformssharepoint.lca is provided with Adobe LiveCycle Installation in the <LiveCycle_Install_DIR>/deploy folder. You can use this to see adobe livecycle forms integration with SharePoint server.

---

Read the complete post at Adobe LiveCycle Blog.

Configure LiveCycle connector for EMC Documentum with Documentum 6.7 SP1

0
340 days
by in LiveCycle Enterprise Suite

- Pankaj Gakhar, Software Engineer @ adobe

This post assumes that you have already installed LiveCycle ES3 with latest service pack and have already configured the LiveCycle Configuration Manager upto the “Validate LiveCycle Components” step.

Issue

When you try to configure the connector, you see only two options 6.0 and 6.5 as shown in the below screen.

 

---

 

Read the complete post at Adobe LiveCycle Blogs.

LiveCycle ES3: Authentication failed for user (Scheme – Username/Password) Reason: Username or password is incorrect

0
341 days
by in LiveCycle Enterprise Suite

- David McMahon, Sr. Technical Account Manager @ Adobe

Issue

If you are accessing any LiveCycle services and have problems getting a response, you may notice the following warning in the server logs:

WARN  [com.adobe.idp.um.businesslogic.authentication.AuthenticationManagerBean] (Thread-21) 
Authentication failed for user [user] (Scheme - Username/Password) Reason: Username or password is incorrect. 
Refer to debug level logs for category com.adobe.idp.um.businesslogic.authentication for further details
 

If you enable DEBUG level logging you will see the following DEBUG information in the log:

DEBUG [com.adobe.idp.common.errors.exception.IDPLoggedException] (Thread-21)
UserM:: [Thread Hashcode: 1796127844] com.adobe.idp.common.errors.exception.IDPLoggedException|
[com.adobe.idp.um.businesslogic.authentication.AuthenticationManagerBean] errorCode:12803 errorCodeHEX:0x3203 message:
Authentication failed for user [user] (Scheme - Username/Password) Reason: Username or password is incorrect
 =========== Authentication failure detail report ================== 
 Scheme Type : Username/Password 
 UserId : user 
 Current Thread : ajp-0.0.0.0-11148-8 
 Following are the response details from various authProviders.  
 1 - com.adobe.idp.um.provider.authentication.LocalAuthProviderImpl - 
 Authentication Failed : Exception stacktraces are avialable at TRACE level 
 Messages collected for this AuthProvider are provided below
      - No local user found with UserId [user] in Domain [DefaultDom]
      - No local user found with UserId [user] in Domain [EDC_SPECIAL]
These warnings in the log may also be accompanied by an Error 500 if you are attempting to call the LC services through a browser/web application.

---

Read the complete post at Adobe LiveCycle Blog.

Streamlined LiveCycle Forums

0
354 days
by in General, LiveCycle Enterprise Suite

- Jeff Stanier, Group PM Program and Release @ Adobe

The forums for LiveCycle have undergone a streamlining exercise to make participation easier and finding content simpler.  Details about the changes can be found on the LiveCycle Help Content Team’s blog .  Let us know how you like it and thanks for participating in the LiveCycle community.
« Previous
Next »
Go to Top