java.lang.ClassNotFoundException: com.documentum.bpm.method.XCPAutoTasKMgmt

Getting following job failure events in installation owner inbox

dm_bpm_XCPAutoTaskMgmt

dm_Initialize_WQ

Environment: CS 7.1 P08, xCP 2.1 P08, WinSQL

Content Server Log:

[ERROR] [LAUNCHER 1584] Detected while completing processing for job dm_bpm_XCPAutoTaskMgmt: FAILED: Could not launch method dm_bpm_XCPAutoTaskMgmt: OS error: (No Error), DM error: ()."

JMS Log:

15:28:06,510 INFO [stdout] (http-0.0.0.0-0.0.0.0-9080-1) 15:28:06,510 ERROR [http-0.0.0.0-0.0.0.0-9080-1] com.documentum.mthdservlet.DoMethod - Exception invoking com.documentum.bpm.method.XCPAutoTasKMgmt.

15:28:06,510 INFO [stdout] (http-0.0.0.0-0.0.0.0-9080-1) java.lang.ClassNotFoundException: com.documentum.bpm.method.XCPAutoTasKMgmt

can any one help on this please...

Advance Thanks..

Find more posts tagged with

Documentum

Comments

VaishaliK

Hi,

Did you get any solution for the issue.?

I am also facing same issue.

Apart from this, we are facing one more issue where all our workflow tasks are going into future state.

Are both these issues related?

Thanks,

Vaishali

amgravem

Hi!

Did any of you find a solution for this? We've got the same issue after upgrading to the same environment as Jeevan.

I think there might be something wrong with our Process Engine install.

Regards,

Anne-Marit

MariuszPala

We're facing now the same issue. Any idea how to fix it?

Thanks,

Mariusz

amgravem

We actually had the dm_jms_config base_uris mixed up, so that BPM methods were ran in DmMethods and vice versa. I recommend checking your dm_jms_config.

Regards,

Anne-Marit

as030991

Hi,

I had same problem on the JMS for one environment with 3 Content Servers installed on High Availability:

2015-03-19 14:03:41,392 ERROR [http--0.0.0.0-9080-1] [com.documentum.bpm.method.XCPAutoTasKMgmt] - Error occured during processing the job 0802b11b80008145

DfAuthenticationException:: THREAD: http--0.0.0.0-9080-1; MSG: [DM_SESSION_E_AUTH_FAIL]error: "Authentication failed for user UserName with docbase DocBaseName."; ERRORCODE: 100; NEXT: null

The problem is the following:
For example, if we have two Content Servers and two JMS: CS1, CS2 and JMS1, JMS2.
Then the CS1 try to execute this job on JMS2, or CS2 try to execute this job on CS1, the authentication error occur.
In case if CS2 and JMS2 are stopped and CS1 and JMS1 are running, and vice versa, this error will not occur.

Solution: Use Privileged DFC client

https://community.emc.com/blogs/jubedus/2012/08/17/privileged-dfc-client

Regards,
Andrei