Archive for March, 2010

LiveCycle ES: ALC-UPG-040-000 UpgradeException: Invalid Join: process_instance

Issue

When you upgrade your LiveCycle 7 environment to LiveCycle ES 8.2.1, the following exception may occur during the Migrate Essential Data step while running the LCM:

[2010-03-11 10:33:11,699], SEVERE, Thread-54, com.adobe.livecycle.upgrade.control.PhaseRunner, Aborting. Invocation of method 
[migrateCriticalData] failed for com.adobe.livecycle.upgrade.workflow.WorkflowUpgradePlugin. Caught 
com.adobe.livecycle.upgrade.UpgradeException, message: ALC-UPG-040-000: Internal error: ALC-UPG-040-000: 
Internal error: Invalid Join: process_instance
com.adobe.livecycle.upgrade.UpgradeException: ALC-UPG-040-000: Internal error: ALC-UPG-040-000: 
Internal error: Invalid Join: process_instance
 at com.adobe.livecycle.upgrade.workflow.WorkflowUpgradePlugin.execute(WorkflowUpgradePlugin.java:320)
 at com.adobe.livecycle.upgrade.workflow.WorkflowUpgradePlugin.migrateCriticalData(WorkflowUpgradePlugin.java:226)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at com.adobe.livecycle.upgrade.control.PhaseRunner.run(PhaseRunner.java:217)
 at java.lang.Thread.run(Thread.java:595)
Caused by: com.adobe.livecycle.upgrade.UpgradeException: ALC-UPG-040-000: Internal error: Invalid Join: process_instance
 at com.adobe.livecycle.upgrade.workflow.WorkflowUpgradePlugin.migrateWorkflow7Templates(WorkflowUpgradePlugin.java:392)
 at com.adobe.livecycle.upgrade.workflow.WorkflowUpgradePlugin.execute(WorkflowUpgradePlugin.java:314)
 ... 7 more
Caused by: java.lang.RuntimeException: Invalid Join: process_instance
 at com.adobe.pof.omapi.AbstractQueryCompoundExpression.addObjectFilter(AbstractQueryCompoundExpression.java:571)
 at com.adobe.pof.omapi.AbstractQueryCompoundExpression.addFilter(AbstractQueryCompoundExpression.java:325)
 at com.adobe.livecycle.upgrade.workflow.WorkflowUpgradePlugin.updateProcessInstanceWithServiceInfo(WorkflowUpgradePlugin.java:1368)
 at com.adobe.livecycle.upgrade.workflow.WorkflowUpgradePlugin.upgradeLC7ProcessTypeToService(WorkflowUpgradePlugin.java:487)
 at com.adobe.livecycle.upgrade.workflow.WorkflowUpgradePlugin.migrateWorkflow7Templates(WorkflowUpgradePlugin.java:386)
 ... 8 more
[2010-03-11 10:33:11,803], INFO, AWT-EventQueue-0, com.adobe.livecycle.upgrade.gui.UpgradePhaseDialog, ALC-UPG-040-000: 
Internal error: ALC-UPG-040-000: Internal error: ALC-UPG-040-000: Internal error: Invalid Join: process_instance

Additional information

Corruption in the LiveCycle ES database can cause this error.  The database can get corrupted if there were any manual modifications, or SQL statements run on the DB, or if you are using an external (not from Adobe) purge utility on the DB.

Solution

  1. Restore the database to a valid state before running the LCM.
  2. Make sure that there are no SQL queries running on the LiveCycle ES Database, before the LCM has run.

reference: (181485096/2526063)

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

LiveCycle ES: RequiredParameterException: Parameter: service-id is required

Issue

 When you try to access a task through the Process Management Process/Task search tools in the administration interface, the following exception occurs:

####<Mar 15, 2010 5:35:34 PM MET> <Error> <HTTP> <server> <managed_server> <[ACTIVE] ExecuteThread: '5' for 
queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1268670934789> <BEA-101017> <
[weblogic.servlet.internal.WebAppServletContext@80d069 - appName: 'adobe-livecycle-weblogic', name: '/PMAdmin', 
context-path: '/PMAdmin'] Root cause of ServletException.
ALC-DSC-000-000: com.adobe.idp.dsc.DSCRuntimeException: Internal error.
 at com.adobe.idp.dsc.registry.service.client.ServiceRegistryClient.getService(ServiceRegistryClient.java:137)
 at com.adobe.livecycle.pm.admin.action.TaskListAction.taskList(TaskListAction.java:210)
 at com.adobe.livecycle.pm.admin.action.TaskListAction.execute(TaskListAction.java:109)
 ...
ALC-DSC-002-000: com.adobe.idp.dsc.RequiredParameterException: Parameter: service-id is required.
 at com.adobe.idp.dsc.interceptor.impl.InvocationInterceptor.intercept(InvocationInterceptor.java:117)
 at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptorChainImpl.java:60)
 at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor$1.doInTransaction(TransactionInterceptor.java:74)
 at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionBMTAdapterBean.doBMT(EjbTransactionBMTAdapterBean.java:197)
 at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionBMTAdapter_jmbvky_ELOImpl.doBMT(EjbTransactionBMTAdapter_jmbvky_ELOImpl.java:141)
 at com.adobe.idp.dsc.transaction.impl.ejb.EjbTransactionProvider.execute(EjbTransactionProvider.java:95)
 at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor.intercept(TransactionInterceptor.java:72)
 at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptorChainImpl.java:60)
 at com.adobe.idp.dsc.interceptor.impl.InvocationStrategyInterceptor.intercept(InvocationStrategyInterceptor.java:55)
 at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptorChainImpl.java:60)
 at com.adobe.idp.dsc.interceptor.impl.InvalidStateInterceptor.intercept(InvalidStateInterceptor.java:37)
 at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptorChainImpl.java:60)
 at com.adobe.idp.dsc.interceptor.impl.AuthorizationInterceptor.intercept(AuthorizationInterceptor.java:109)
 at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptorChainImpl.java:60)
 at com.adobe.idp.dsc.interceptor.impl.JMXInterceptor.intercept(JMXInterceptor.java:48)
 at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptorChainImpl.java:60)
 at com.adobe.idp.dsc.engine.impl.ServiceEngineImpl.invoke(ServiceEngineImpl.java:115)
 at com.adobe.idp.dsc.routing.Router.routeRequest(Router.java:118)
 at com.adobe.idp.dsc.provider.impl.base.AbstractMessageReceiver.routeMessage(AbstractMessageReceiver.java:91)
 at com.adobe.idp.dsc.provider.impl.vm.VMMessageDispatcher.doSend(VMMessageDispatcher.java:215)
 at com.adobe.idp.dsc.provider.impl.base.AbstractMessageDispatcher.send(AbstractMessageDispatcher.java:57)
 at com.adobe.idp.dsc.clientsdk.ServiceClient.invoke(ServiceClient.java:208)
 at com.adobe.idp.dsc.registry.service.client.ServiceRegistryClient.invoke(ServiceRegistryClient.java:994)
 at com.adobe.idp.dsc.registry.service.client.ServiceRegistryClient.getService(ServiceRegistryClient.java:122)
 at com.adobe.livecycle.pm.admin.action.TaskListAction.taskList(TaskListAction.java:210)
 at com.adobe.livecycle.pm.admin.action.TaskListAction.execute(TaskListAction.java:109)
 ...

Reason

Corruption in the LiveCycle ES database resulting from manual database modifications can cause a “RequiredParameterException” error.  Database corruption can also occur if you are using an external (not from Adobe) purge utility on the LiveCycle database.

Solution

Restore the database from backup to a valid state.

reference: (181491816)

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

LiveCycle ES: Processes in Workspace and AdminUI appearing as “null – 0.0″

Issue

After you upgrade from LiveCycle 7 to LiveCycle ES 8.2.1, some of the processes in the Admin user interface and Workspace appearing as “null – 0.0″.

Reason

Corruption in the LiveCycle ES database causes process names and versions to be listed in the Admin user interface as “null – 0.0.”.  The corruption can be caused if the database content has been modified manually, or if you are using an external (not from Adobe) purge tool on the database.

Solution

Restore the database to a valid state.

reference: (181491899)

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

LiveCycle ES: Link to help files returns 404 error with localized Workspace

Issue

When you use the localized version of LiveCycle ES 8.2.1 Workspace in a web browser, clicking the link to the Help files may return a 404 error. The link works correctly when you use the standard English locale.  This issue has been reported particularly on French and German locales.

Reason

This was a bug in LC ES 8.2.1.2 and previous versions.

Solution

This issue has been fixed in LC ES2 9.0.0.0 and later versions.  There is a patch available for LiveCycle ES 8.2.1.x, so you should contact enterprise support if you require this patch.

reference: (181413026/2542542)

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

LiveCycle ES: TaskPermissionsException using TaskManager.getTaskInfo()

Issue

When you use the LiveCycle ES APIs to access tasks through the TaskManager.getTaskInfo() method, LiveCycle may return the following error:

TaskPermissionsException User: A50D7ECD-15F5-6B60-9619-44F68536EC32 does have access to get the data for the task: 560701.

You may be using code similar to the following when trying to access the tasks:

TaskManager taskManager = TaskManagerClientFactory.getTaskManager(connectionFactory.getAlcServerConnection());

TaskInfo taskInfo = taskManager.getTaskInfo(new Long(taskId)); 

If you do not have the right permissions for the user context running this code, then you will receive the exception above.

Solution

To execute this method with a user other than the super administrator, manually add the Workflow Process Administrator Role to that user. You can add this role to the user account in the adminui (Home > Settings > User Management > Role Management).

reference: (181498712)

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

LiveCycle ES: duplicate user queues appearing in Workspace ES

Issue

Users have duplicate queues in Workspace in Adobe LiveCycle ES 8.2.1. The first queue is the user’s personal queue (in blue below), and the second seems to be a shared queue (in red below).

 

Reason

Duplicate queues can appear if you had a custom application in LiveCycle 7 that created more than one queue per user. By default, LiveCycle doesn’t create more than one queue per user. LiveCycle clients, like Workspace (LC ES) and FormManager (LC 7) do not support multiple queues for the same user. The workflow engine in the background does support multiple queues per person, but this functionality is rarely used.

When there are multiple queues for a user, each queue has a row with a unique ID in TB_QUEUE. The ID in the default_queue_id column is the ID of the queue that workspace always uses for that user.

Solution

Remove the duplicate (shared) queue from the TB_QUEUE table. Before deleting the queue, run the following query to ensure that there are no assignments referencing the shared queue:

Select count(*) from tb_assignment where queue_id = xxx

Where xxx is the queue ID of the queue that is not the user’s default queue. That is, the queue ID not listed in the default_queue_id column.

reference: (181496045)

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

LiveCycle ES: InvalidCoercionException when using TaskManagerQueryService.taskSearch(TaskSearchFilter filter)

Issue

When you use the API in LiveCycle ES to call the method, “TaskManagerQueryService.taskSearch(TaskSearchFilter filter),” the following exception may occur:

ALC-DSC-119-000: com.adobe.idp.dsc.util.InvalidCoercionException: Cannot coerce object: 
com.adobe.idp.taskmanager.dsc.client.query.TaskSearchFilter@1972b9a of type: 
com.adobe.idp.taskmanager.dsc.client.query.TaskSearchFilter to type: 
class com.adobe.idp.taskmanager.dsc.client.query.TaskSearchFilter
 at com.adobe.idp.dsc.util.CoercionUtil.toType(CoercionUtil.java:1047)
 at com.adobe.idp.dsc.interceptor.impl.InvocationInterceptor.intercept(InvocationInterceptor.java:127)
 at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptorChainImpl.java:60)
 at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor$1.doInTransaction(TransactionInterceptor.java:74)
 at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.execute(EjbTransactionCMTAdapterBean.java:342)
 at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.doSupports(EjbTransactionCMTAdapterBean.java:212)
 at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapter_z73hg_ELOImpl.doSupports

Solution

  1.  Make sure that the processId object passed into the filter.addCondition() is a valid object.
  2. Verify that the libraries you are importing contain no abstract references to classes with similar names and make sure that they are the latest versions.

Additional Information

Here is the code which would generate the error message above (or download here):

____________________________

 

ServiceClientFactory factory = ServiceClientFactory.createInstance(context);

TaskManagerQueryService queryManager = TaskManagerClientFactory.getQueryManager(factory);

TaskManager taskManager = TaskManagerClientFactory.getTaskManager(factory);

TaskSearchFilter filter = new TaskSearchFilter();

filter.addCondition(TaskSearchingConstants.pPROCESS_INSTANCE_ID, Operator.EQUALS, processId);

filter.addSortAsc(TaskSearchingConstants.pPROCESS_START_TIME);

// To look on every task !!! Need to have an Administrator context!!!

filter.setAdminIgnoreAllAcls(true);

List<TaskRow> result = queryManager.taskSearch(filter);

____________________________

reference: (181492707)

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

LiveCycle ES: start_task=0 in TB_TASK table in LiveCycle database

When you develop a custom interface for an upgraded Adobe LiveCycle ES server, you can encounter problems referencing initial tasks for a process. Initial tasks must correctly show the audit history for processes in your custom interface, much the same as Workspace displays them in the tracking view.

In the TB_TASK table in the database, a start_task flag set to “1” appears for initial tasks from a process started through the TaskManager endpoint. However, for some initial tasks, this flag is set to “0.”

 

This behavior is as designed. Start_task is an ES concept that doesn’t come into play when anything from LiveCycle 7 is involved.  Any tasks migrated from LiveCycle 7, and any tasks started in Workspace with a LiveCycle 7 init-form definition in use, have a start_task value of “0.”

To determine whether a task is an initial task in all cases, locate the task that doesn’t have an action instance. That is, one where the action_instance_id=null or zero. If the process instance ID has a value, but the action instance ID doesn’t, then it’s an initial task.

reference: (181494242)

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

LiveCycle ES: IDPSystemExceptionorigin using DirectoryManagerServiceClient.findGroupMembers()

Issue

When you use the LiveCycle ES API method “DirectoryManagerServiceClient.findGroupMembers()” in a custom application, the following exception may occur:

####<Mar 8, 2010 9:31:28 AM MET> <Info> <EJB> <sunc01126> <wl01ialc01> <[ACTIVE] ExecuteThread: '1' for queue: 
'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0F2A55F8B8D325A5DE0E> <> <1268037088883> <BEA-010051> 
<EJB Exception occurred during invocation from home: 
com.adobe.idp.um.businesslogic.directoryservices.DirectoryServicesManagerBean_jrc290_LocalHomeImpl@ad9846 threw exception: 
com.adobe.idp.common.errors.exception.IDPSystemExceptionorigin: | 
[com.adobe.idp.storeprovider.jdbc.DBObjectSet] errorCode:12290 errorCodeHEX:0x3002 message:nextElement failure| 
[com.adobe.idp.storeprovider.jdbc.DBResult] errorCode:12290 errorCodeHEX:0x3002 message:object update failure| 
[com.adobe.idp.common.infomodel.StoreId] errorCode:12550 errorCodeHEX:0x3106 message:string length wrong
com.adobe.idp.common.errors.exception.IDPSystemExceptionorigin: | 
[com.adobe.idp.storeprovider.jdbc.DBObjectSet] errorCode:12290 errorCodeHEX:0x3002 message:nextElement failure| 
[com.adobe.idp.storeprovider.jdbc.DBResult] errorCode:12290 errorCodeHEX:0x3002 message:object update failure| 
[com.adobe.idp.common.infomodel.StoreId] errorCode:12550 errorCodeHEX:0x3106 message:string length wrong
 at com.adobe.idp.common.util.IDPUtil.raiseIDPSystemException(IDPUtil.java:147)
 at com.adobe.idp.um.businesslogic.directoryservices.DirectoryServicesManagerBean.findGroupMembers(DirectoryServicesManagerBean.java:4261)
 at com.adobe.idp.um.businesslogic.directoryservices.DirectoryServicesManagerBean_jrc290_ELOImpl.findGroupMembers(DirectoryServicesManagerBean_jrc290_ELOImpl.java:1504)
 at com.adobe.idp.um.api.impl.DirectoryManagerImpl.findGroupMembers(DirectoryManagerImpl.java:928)
 at com.adobe.idp.um.dscservice.DirectoryManagerServiceImpl.findGroupMembers(DirectoryManagerServiceImpl.java:238)
 at sun.reflect.GeneratedMethodAccessor1366.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)

 Solution

  1. Validate the GroupOID string and ensure that it is not the standard Group name, but an identifier of 36 characters.
  2. Validate the members of the group to ensure that they are valid objects. It is possible that one of the members has been corrupted due to manual changes through the API. Remove any corrupt members and re-create them to proceed.

Additional information

The most likely cause of this exception is that there is an invalid GroupOID being passed into the search filter used in the findGroupMembers() method. The OID strings are identifiers with 36 characters. You cannot use the standard Group name for the search filter. You can verify the GroupOID and the members of the group are valid by using the following code:
_____________________________________

DirectoryManagerServiceClient dmsc = new DirectoryManagerServiceClient(myFactory);
Principal group = dmsc.findPrincipal("9462F437-8669-0D04-24F8-F00CDF80A09E");
System.out.println("Group found: "+group.getCommonName());

GroupMembershipSearchFilter gsf = new GroupMembershipSearchFilter();
gsf.setGroupOid("9462F437-8669-0D04-24F8-F00CDF80A09E");

List<Principal> members = dmsc.findGroupMembers(gsf);
System.out.println("Members found:"+members.size());

for(Principal p : members){
 System.out.println("Principal found: " + p.getCommonName());
}
__________________________________________

reference: (181484795)

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

LiveCycle ES: com.adobe.idp.DocumentError using the UserPlus QPAC with attachments

Issue

The following error occurs at run-time when you use the UserPlus QPAC from Avoka with attachments in Adobe LiveCycle ES 8.2.1:

javax.ejb.EJBException: EJB Exception: : com.adobe.idp.DocumentError: The document pointing to the file 
"/mydomain/AdobeDocumentStorage/session_wfattach443760/6261454814295665168" has expired. Consider increasing 
the document disposal timeout.
 at com.adobe.idp.DocumentFileBackend.checkFileExistance(DocumentFileBackend.java:412)
 at com.adobe.idp.DocumentFileBackend.copy(DocumentFileBackend.java:419)
 at com.adobe.idp.Document.passivate(Document.java:1065)
 at com.adobe.idp.Document.passivate(Document.java:1012)
 at com.adobe.idp.Document.<init>(Document.java:565)
 at com.adobe.idp.Document.<init>(Document.java:621)
 at com.adobe.idp.DocumentStorage.persist(DocumentStorage.java:78)
 at com.adobe.idp.taskmanager.dsc.client.task.AttachmentInfoImpl.persistDoc(AttachmentInfoImpl.java:201)
 at com.adobe.idp.taskmanager.dsc.service.CopyAttachments.copyAttachmentsToTask(CopyAttachments.java:326)
 at com.adobe.idp.taskmanager.dsc.service.CopyAttachments.copyAttachmentsForward(CopyAttachments.java:291)
 at com.adobe.idp.taskmanager.dsc.service.TaskManagerServiceImpl.createTask(TaskManagerServiceImpl.java:465)
 at sun.reflect.GeneratedMethodAccessor1243.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)

Reason

Attachments are stored in the Adobe DocumentStorage directory for LiveCycle 7 and in the GDS directory for LiveCycle 8. An error occurs in LiveCycle 8 if the attachments are stored in the DocumentStorage directory, and are not available in the GDS directory.  This can occur if you have upgraded your server from LiveCycle 7 to LiveCycle ES.

Solution

Manually copy the documents from the LiveCycle 7 DocumentStorage directory to the LiveCycle ES GDS directory.

reference: (181472965)

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

LiveCycle ES: AuthenticationManagerImpl errorCode:16386 errorCodeHEX:0x4002

Issue

The following exception occurs when you were running custom Java code to interact with Adobe LiveCycle 7 Workflow using LDAP lookups and migrate to LiveCycle ES:

[04 Mar 2010 10:32:27, 058] ERROR (WorklistController.java:66) - java.lang.Exception: | 
[com.adobe.idp.um.api.impl.AuthenticationManagerImpl] errorCode:16386 errorCodeHEX:0x4002 message:
user_identifier:myuniqueid=XXXXXXXX,ou=people,dc=company,dc=com domain:LDAP Production| 
[com.adobe.idp.um.businesslogic.directoryservices.DirectoryServicesManagerBean] errorCode:13316 errorCodeHEX:0x3404 message:
user_identifier:myuniqueid=XXXXXXXX,ou=people,dc=company,dc=com domain:LDAP Production
com.pictet.livecycleworkflow.restservices.client.exceptions.ResourceOperationException: java.lang.Exception: | 
[com.adobe.idp.um.api.impl.AuthenticationManagerImpl] errorCode:16386 errorCodeHEX:0x4002 message:
user_identifier:myuniqueid=XXXXXXXX,ou=people,dc=company,dc=com domain:LDAP Production| 
[com.adobe.idp.um.businesslogic.directoryservices.DirectoryServicesManagerBean] errorCode:13316 errorCodeHEX:0x3404 message:
user_identifier:myuniqueid=XXXXXXXX,ou=people,dc=company,dc=com domain:LDAP Production
 at com.company.livecycleworkflow.restservices.client.impl.AbstractLiveCycleWorkflowRestServiceClient.sendRequest(AbstractLiveCycleWorkflowRestServiceClient.java:92)
 at com.company.livecycleworkflow.restservices.client.impl.AbstractLiveCycleWorkflowRestServiceClient.readRestUrl(AbstractLiveCycleWorkflowRestServiceClient.java:100)
 at com.company.livecycleworkflow.restservices.client.impl.LiveCycleWorkflowRestServiceClientImpl.getActivities(LiveCycleWorkflowRestServiceClientImpl.java:47)
 at com.company.livecycleworkflow.restservices.client.impl.LiveCycleWorkflowRestServiceClientImpl.getActivities(LiveCycleWorkflowRestServiceClientImpl.java:40)
 at com.company.managerscomments.controller.WorklistController.handleRequestInternal(WorklistController.java:54)
 at org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153)
 at org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:44)
 at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:723)
 at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:663)
 at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:394)
 at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:348)

The method that throws this error is: authResult = auth.getAuthResultOnBehalfOfUser(“myuniqueid=XXXXXXXX, ou=people”, “LDAP Production”, context).

Reason

This exception occurs when you don’t use the same user DN in the Java code as is stored in LDAP and in the LiveCycle database.

For example, the myuniqueID in the EDCPRINCIPALENTITY table is:

myuniqueid=XXXXXXXX,ou=People,dc=company,dc=com

and in the Java code it’s:

myuniqueid=XXXXXXXX,ou=people,dc=company,dc=com

The ou has a capital “P” in LDAP and in the DB, but in the Java code, it was attempting to find the user with a lowercase “p” for the ou. This error can occur in LiveCycle ES as Adobe changed the LDAP synchronization algorithm to canonicalize the DN strings during synchronization. As a result, the DN strings appear in the DB exactly as they are defined in LDAP (including case-sensitivity).

Solution

Make sure that you are using exactly the same user DN in the Java code as it is stored in LDAP and in the LiveCycle database.

reference: (181473688)

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