LiveCycle Workbench ES3: AttributeNotFoundException trying to create a new process


If you have installed ES3 SP1 (10.0.3) to your LiveCycle ES3 server and Workbench ES3 you may encounter a problem creating new processes.  Selecting the menu item to create a new process does not have any effect.  If you look in the Workbench log file (C:\Users\<YOUR_USER_NAME>\Workbench ES2\.metadata\.log) you may notice the following exception:

!ENTRY org.eclipse.ui 4 0 2012-05-31 21:58:28.424
!MESSAGE Unhandled event loop exception
ALC-DSC-110-000: com.adobe.idp.dsc.registry.endpoint.EndpointStoreException: endpoint registry failure.
Caused by: com.adobe.pof.schema.AttributeNotFoundException: Attribute: parent_oid does not exist on object-type: dsc.sc_category.
 at com.adobe.pof.schema.POFAbstractObjectType.getAttribute(
 at com.adobe.pof.omapi.POFDefaultQuery.addSort(
    at com.adobe.pof.omapi.POFDefaultQuery.addSortAsc(
    at com.adobe.idp.dsc.registry.endpoint.impl.EndpointStoreImpl.getEndpointCategories(
    at com.adobe.idp.dsc.registry.endpoint.impl.EndpointRegistryImpl$2.doInTransaction(
    at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.execute(
    at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.doRequiresNew(
    at sun.reflect.GeneratedMethodAccessor546.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(
    at java.lang.reflect.Method.invoke(


ES3 SP1 includes some feature enhancements in Process Management.  This involved addition of new columns and tables to the existing ES3 DB schema and hence requires a DB re-initialization when running LCM.


You should always read the installation steps in the ES3 SP1 readme (link below) before attempting the installation.  In this case, you will need to re-run LCM and select the step to initialize the database.

You can download ES3 SP1 here:

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

CQ5.5: Members of administrators group not able to unlock pages from other users


Only the user who locked the page, or the “admin” user, can unlock it.  Members of the administrators group, apart from the “admin” user, cannot unlock pages which were locked by other users.

The documentation ( states:

You can only unlock locked pages if you locked the page or if you have administrator privileges.

This may be misleading, as it is not sufficient to have administrator privileges (i.e. general members of the administrators group).  Only the “admin” account has the correct privileges.

How to unlock a page

It is possible to unlock a page using the sidekick in WCM, or using Content Explorer.

1. Using the sidekick

Log into CQ as the user who locked the page or the “admin” user.

Open the page that is currently locked in the WCM Websites panel.

In the sidekick, select the Page tab and then “Unlock Page”.

2. Using Content Explorer (http://<server>:<port>/crx/explorer)

Browse the tree to the locked page.

Right-click on the jcr:content node below the locked page.

Select “Unlock” from the context menu.

reference: (35128/CQ5-18339)

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