java.lang.NoClassDefFoundError: Could not initialize class com.documentum.fc.client.DfClient     at com.documentum.com.DfClientX.getLocalClient(DfClientX.java:43)     at ……..

The cause of this error is that the classpath required for connecting for documentum 6.7 SP1 is not correct.

---

Read the complete post at Adobe LiveCycle Blog.

Solution:

To enable convert to pdf option for xml, aspx or any other type of documents (which are supported by LiveCycle PDF Generator component), you can follow the below steps:-

---

Read the complete post at Adobe LiveCycle Blog.

You should have LiveCycle server installed and LiveCycle connector for IBM FileNet should be configured with it.

Follow the steps below to store content to FileNet server using LiveCycle’s Java APIs:

1. Create ServiceClientFactory Object.

2. Create an object of IBMFileNetContentRepositoryConnectorServiceClient class using the object of ServiceClientFactory class.

---

Read the complete post at Adobe LiveCycle Blog.

The LiveCycle ES3 connector for Microsoft SharePoint 2010 contains two parts:-

1. Document Services Component (DSC) which is installed on LiveCycle Server.
2. Web Part that is installed on the SharePoint Server.

Installing Adobe LiveCycle ES3 Connector for Microsoft SharePoint DSC (Fresh Installation)

Install the LiveCycle ES3 server on your machine and follow the below steps to configure the SharePoint Connector:-

1. Move to the LiveCycle server installation directory and start the LiveCycle Configuration Manager (LCM). LCM is available at <LIVECYCLE_INSTALL_DIR>/configurationManager/bin/ConfigurationManager.exe or .bat.

2. If you are adding SharePoint to an existing LiveCycle ES3 Installation, please go to section Adding SharePoint Connector to an existing LiveCycle ES3 installation. If this is a fresh installation then, choose express mode of installation and on the Modulesscreen select the components that you want to install along with LiveCycle ES3 Connector for Microsoft SharePoint.

---

Read the complete post at Adobe LiveCycle Blog.

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.

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.

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.

After installing Adobe LiveCycle Connector Web Part on SharePoint 2010, you may encounter an error Access Denied while activating Adobe LiveCycle Connector feature on a SharePoint Site Collection. This issue occurs due to a new security feature implemented in SharePoint 2010. You can refer Microsoft KB 2564009 for details.

You can check SharePoint logs for details of the exception. The logs would look similar to:

w3wp.exe (0x0F48) 0x190C    SharePoint Foundation Feature Infrastructure  88jm    High     Feature receiver assembly ‘AdobeLiveCycleConnector, Version=1.0.0.0, Culture=neutral, PublicKeyToken=6720cbcc342f4ca4′, class ‘LiveCycleInterop.LiveCycleFeatureReceiver’, method ‘FeatureActivated’ for feature ’33a7c6b5-4e62-44aa-bf99-62d283de683a’ threw an exception: System.Security.SecurityException: Access denied.     at Microsoft.SharePoint.Administration.SPWebService.set_RemoteAdministratorAccessDenied(Boolean value)     at LiveCycleInterop.LiveCycleFeatureReceiver.addToWebConfig(SPFeatureReceiverProperties properties)     at LiveCycleInterop.LiveCycleFeatureReceiver.FeatureActivated(SPFeatureReceiverProperties properties)     at Microsoft.SharePoint.SPFeature.DoActivationCallout(Boolean fActivate, Boolean fForce)  The Zone of the assembly that failed was:  MyComputer    fda8f095-7baa-47e4-b400-740259ad8ff5

---

Read the complete post at Adobe LiveCycle Blog.