Posts tagged connector

Could not initialize class com.documentum.fc.client.DfClient while starting livecycle documentum connector services for documentum 6.7 SP1

If you are trying to configure documentum 6.7 sp1 with livecycle and while starting the services for livecycle connector for emc documentum you are getting the below error, then this post may be help ful to you.

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.

LiveCycle SharePoint Connector option convert to pdf is not available on .xml or .aspx pages

Users keep facing the issue that the LiveCycle SharePoint connector options are not available on certain type of files like xml and aspx.

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.

LiveCycle ES3 – FileNet Connector for FileNet 5.0 – Documentation Clarification

Issue:

For LC ES3 – the “Preparing to Install Adobe LiveCycle ES3″ Guide – section 2.2.9 (Additional requirements for Connector for IBM FileNet) – for FileNet Connector configuration is unclear.

The section reads as below -

=======

IBM FileNet 5.0

If LiveCycle is connecting to IBM FileNet 5.0 Content Engine, you must install the Content Engine Java Client. Use the IBM FileNet 5.0 content engine client installer located by default in C:Program FilesFileNetCEClient. During installation, select at least one of the components from Application Engine or Process Engine on the component selection screen.

For IBM FileNet 5.0 Process Engine, you must install the IBM FileNet 5.0 Process Engine Client located by default in C:Program FilesFileNetBPMClient. During installation, select the Other option on the component selection screen.

=======

Questions:

The above text in red does not clearly answer the below questions:

- Does this mean that during the Java Client installation, the user needs to point to an existing Application Engine installation (which maybe be on a different server than LiveCycle)?

- Or does this mean that the Java Client has to be installed where the Application Engine resides (which it already is) and so this step can effectively be skipped?

- Or does this mean that another instance of Application Engine needs to be installed on the same server as LiveCycle?

---

Read the complete post at Adobe LiveCycle Blog.

Access Denied while activating ‘Adobe LiveCycle Connector’ feature on SharePoint 2010

- Pankaj Gakhar,  Software Engineer @ Adobe

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.

LiveCycle ES2 Connector for Microsoft SharePoint – Upload Large File sizes

- Abhijit Ghosh, LiveCycle TRT Engineer @ Adobe

We were recently working on a customer scenario who was facing issues with uploading documents greater than 50 MB on the Microsoft Sharepoint Server 2010. There are a couple of things that one needs to keep in mind when dealing with large file sizes.

---

Read the complete post at Adobe LiveCycle Blog.

Go to Top