Error : BPM-0526: Cannot start process. Process is not active or validated.

[Anon Anon]

Getting below shown error while initiating process, All the things are active and validated.

 

An error occurred when initiating a process instance using process
version ID 5037675:com.niku.union.utility.MessageKeyException: BPM-0526: Cannot
start process. Process is not active or validated.

at
com.niku.bpm.engine.BusinessProcessImpl.startProcessByVersionId(BusinessProcessImpl.java:254)
at
com.niku.bpm.engine.BusinessProcessImpl.startProcessByVersionId(BusinessProcessImpl.java:227)
at com.niku.bpm.engine.BusinessProcessImpl.startProcessByVersionId(BusinessProcessImpl.java:202)
at

com.niku.bpm.gel.tags.StartProcessTag.doTag(StartProcessTag.java:96)
at

org.apache.commons.jelly.impl.TagScript.run(TagScript.java:247)

at
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)

at
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:186)

at

org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:247) at
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:186) at

org.apache.commons.jelly.tags.core.IfTag.doTag(IfTag.java:42) at
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:247) at
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:186) at

org.apache.commons.jelly.tags.core.CatchTag.doTag(CatchTag.java:44)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:247) at
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:186) at

com.niku.union.gel.tags.ScriptTag.doTag(ScriptTag.java:20) at
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:247) at
com.niku.union.gel.GELScript.run(GELScript.java:57) at
com.niku.union.gel.GELController.invoke(GELController.java:74) at

com.niku.bpm.services.ExecuteCustomAction.run(ExecuteCustomAction.java:207)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.Exception .

[Anon Anon]

Hi Anant,

 

The problem looks like a sequencing issue please follow the below technical

document after stopping all the services

 

https://comm.support.ca.com/?legacyid=TEC439440

 

https://comm.support.ca.com/?legacyid=TEC509569

 

Once this is done please make sure to check for the orphan for jobs

 

 

https://comm.support.ca.com/?legacyid=TEC608940

 

Regards

Chandrani

[Anon Anon]

Any other solution, Please ?

[navzjoshi00]

Can you check the below URL (replace the <URL> with ur clarity URL) and see the process mode ?

 

https://<URL>/niku/nu#action:bpm.processDefinitionProperties&process_version_id=5037675&object_type=admin&ui.page.space=bpm.processDefinitions&ui.page.template=union.adminPage&bpm.returnModuleAction=bpm.processDefinitionsReturn

 

NJ

[Jerin Sebastian]

Hi, I have seen this happening but for various reasons. If you are looking for an immediate fix, try flushing the cache and restart the BG. Is this happening on an env which was DB restored from a diff env? If so this might be due to sequencing. I presume you have checked all permissions and have the rights to initiate the process. Let us know how it went Thanks, Jerin

[navzjoshi00]

Can you check the below URL (replace the <URL> with ur clarity URL) and see the process mode ?

 

https://<URL>/niku/nu#action:bpm.processDefinitionProperties&process_version_id=5037675&object_type=admin&ui.page.space=bpm.processDefinitions&ui.page.template=union.adminPage&bpm.returnModuleAction=bpm.processDefinitionsReturn

 

NJ

[Anon Anon]

Thanks all, the issue got resolved

[Suman Pramanik]

Hi Anant

 

Are you on V13.3 ? Can you confirm going to process defination and see if its validated and status shows green?

 

Regards

Suman Pramanik

[Anon Anon]

Thanks, the issue has been resolved

[Suman Pramanik]

Hi Anant,

 

Please post the workaround and mark the thread as correct.

 

Regards

Suman Pramanik

[Anon Anon]

The process was on hold , Thanks

[Suman Pramanik]

Hi Anant,

 

The process going on hold is not a right thing. The root cause is process storm which can be genuine or can be bug also.

 

CLRT-74393  You might be hitting a known bug where it things there is a process storm as there is a monitoring put in place. So due to the bug it thinks its a storm and puts the process on hold

 

 

 

The workaround is to disable the flag or increase the loopLimit/processLimit

 

 

So you can login to clarity and add security.pemconfig

 

 

https://servername/niku/nu#action:security.pemconfig

 

 

Then you can see either to disable or increase the count.

 

Hope this helps for future.

 

Regards
Suman Pramanik

[Anon Anon]

Thanks

[Suman Pramanik]

Anant,

 

This is specific to 13.3 as this new feature came in from there.

Regards

Suman Pramanik

[Anon Anon]

Actually, when we checked the process table there was an update which was done by someone from our team.

 

Regards

Annat

[navzjoshi00]

Thanks for sharing this, Suman

 

NJ