Skip Ribbon Commands
Skip to main content
Navigate Up
Sign In

Quick Launch

Average Rating:

facebook Twitter
Email
Print Bookmark Alert me when this article is updated

Feedback

"SIP-50265: Failed to create a task for the process name[BeUpdateWithApprovalTask] because of the following error : [(404)Not Found]" while updating or adding BE on the E360 in ActiveVOS
Problem Description
Invoking the ActiveVOS workflow fails when updating or adding BE on the E360. The following error in cmxserver log: 

Caused by: com.informatica.mdm.bpm2.BPMAdapterException: SIP-50265: Failed to create a task for the process name[BeUpdateWithApprovalTask] because of the following error : [(404)Not Found]
at com.informatica.mdm.bpm2.be.activevos.ActiveVOSWorkflowAdapter.create(ActiveVOSWorkflowAdapter.java:252)
at com.delos.cmx.server.datalayer.repository.workflow.CompositeBPMAdapter.create(CompositeBPMAdapter.java:87)
at com.informatica.mdm.cs.steps.BPMAdapterAware.createTask(BPMAdapterAware.java:173)
... 82 more
Caused by: (404)Not Found
at org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:744)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:144)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at com.siperian.mrm.workflow.activevos2.IDDTaskBindingStub.start(IDDTaskBindingStub.java:226)
at com.informatica.mdm.bpm2.be.activevos.ActiveVOSWorkflowAdapter.create(ActiveVOSWorkflowAdapter.java:235)
... 84 more
Cause
This issue occurs when the BPR is not deployed or deployed with user which does not have abAdmin role.
Solution
To resolve this issue, make sure the following:
  1. ​Go to ActiveVOS console, make sure the task which should get created, its corresponding worflow is not deployed in ActiveVOS.
    In ActiveVOS, deploy the BPR. This process should be available in the process definition.
  2. In the contributions, the deployer should be a user who has abAdmin role and present in application server with abAdmin role. If not login with an abAdmin ​user and redeploy the BPR. 

More Information
Applies To
Product: Active VOS; MDM Multidomain
Problem Type: Configuration
User Type: Administrator
Project Phase: Configure
Product Version:
Database:
Operating System:
Other Software:

Reference
Attachments
Last Modified Date:9/14/2020 1:47 PMID:629923
People who viewed this also viewed

Feedback

Did this KB document help you?



What can we do to improve this information (2000 or fewer characters)