nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Cannot attach lifecycle policy to the object

Hosam Salem

Dear All,

Suddenlly, we are unable to attach lifecycle to objects, with the following error message:

Cannot attach lifecycle policy to the object #######, LifeState ARCHIVED, LifeAlias due to Documentum error: [DM_POLICY_E_EXIST_NO_BP_LOG]error: "BP Log (C:\Documentum\dba\log\00022cea\bp\bp_transition_#######.out) was not created.".

Please advice.

Thanks in advance.

Find more posts tagged with

Documentum

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Button

Accepted answers

Hosam Salem

Thanks a lot, guys, for your inputs.

The issue has been resolved, and the cause was with the node holding the content server cluster. As when we performed a fail-over to the other node, the issue has gone. We are now analysing the issue with the problematic node.

Thanks again for your interest.

All comments

jklawrence

Interestingly, we've been experiencing the same kinds of problems. This is apparently some kind of generic (non-helpful) message that could indicate a lot of issues.

First thing to do is check your lifecycle actions. One of the issues we had was that the folder the lifecycle was supposed to link the document to no longer existed. So when the lifecycle attempted to perform the link action, we got the above message. Verify that all your actions still make sense.

I had opened a case with EMC on this, and another thing they suggested was to uncheck the "Use Method Server" box in the dm_bp_transition method (the docbasic one) since we are using Java lifecycles. I don't really know if that had any effect or not.

- Jane

PanfilovAB

 Cannot attach lifecycle policy to the object #######, LifeState ARCHIVED, LifeAlias  due to Documentum error: [DM_POLICY_E_EXIST_NO_BP_LOG]error:  "BP Log (C:\Documentum\dba\log\00022cea\bp\bp_transition_#######.out) was not created.".

Actually, this message is not an error, it only means that something happened during BP Transition but CS does not know what - it tried to open BPTransition log to read actual error, but was unable to find log file.

lastnitescurry

PanfilovAB wrote:Cannot attach lifecycle policy to the object #######, LifeState ARCHIVED, LifeAlias  due to Documentum error: [DM_POLICY_E_EXIST_NO_BP_LOG]error:  "BP Log (C:\Documentum\dba\log\00022cea\bp\bp_transition_#######.out) was not created.".Actually, this message is not an error, it only means that something happened during BP Transition but CS does not know what - it tried to open BPTransition log to read actual error, but was unable to find log file.

TRUE but of no help when your lifecycles are not working

This rather useful feature of lifecycles is a pain in the behind. Basicly your lifecycle failed and you have to figure it out yourself what is wrong because producing a useful error log is not the job of the Content Server!!!!

PanfilovAB

TRUE but of no help when your lifecycles are not working

The problem is you should have enough programmer/dba/administrator skills to diagnose such problems

This rather useful feature of lifecycles is a pain in the behind. Basicly your lifecycle failed and you have to figure it out yourself what is wrong because producing a useful error log is not the job of the Content Server!!!!

There is another annoying thing: CS does not correctly handle timeouts of BPTransition - it rises exception to client but method continues working and sooner or later do its job.

Hosam Salem

Thanks a lot, guys, for your inputs.

Thanks again for your interest.

lazo983

Hello LimoMan and others,

we have the same problem, how did you resolved it?

It is urgent, so could you give an advice.

Thank you.

Regards

Hosam Salem

Is your content server clustered? if so, check my previous reply in the thread.

Otherwise, I guess you may have a different cause for the issue.

lazo983

No , we don't have cluster.

jklawrence

1. Make sure you don't have any errors in your lifecycle, or old lifecycles attached to your documents that have errors (e.g., they are set to move the documents to a folder that doesn't exist or apply an acl that doesn't exist). This is what caused our issues.

2. The user that is attaching the lifecycle must be the owner of the document or a superuser.

- Jane

lazo983

Hi Jane,

1. all the lifecycles and workflows, worked fine, no errors. I have not changed acl, i do not move the documents to folder, simply set an attribute in every state.

2. all the testing is performed by superuser.

Could you please see this disscusion

https://community.emc.com/message/698310#698310

, I have explained with logs.

Thank you