cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Process starts sucessfully but no tasks are created

Go to solution
Former Member

on ‎01-28-2009 11:11 AM

0 Kudos

Hi,

I am facing a weird behavior in BPM. I created a process by following this [tutorial|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a0886795-eaa0-2b10-7c97-d81b97372327] by Jie Deng. Everything went fine and I am able to start the process in Process Repository. But no work item for the user is created and when I take a look at the process instance in NWA and want to view the tasks no tasks are created for the process instance.

Any recommendations. Did anyone already face and solve this issue?

Thanks a lot,

Mane

Show replies
Show replies
Answer

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
‎01-28-2009 12:42 PM
0 Kudos

Hi Manfred,

Have you assigned the user to the tasks and are you logging in from that particular user.

Have you deployed the webdynpro application.

Regards,

Srinivasan Subbiah

Show replies
Show replies
Former Member
‎01-28-2009 1:18 PM
0 Kudos

Hi Srinivasan, thanks for the reply.

Yes, the web dynpro application was build and deployed successfully and so did the process. Each step has the particular user with all necessary rights specified in the tutorial. I started the process with this user and also with the administrator. In each case no tasks are created. I can see the process instances as running but no tasks assigned to it.

Former Member
‎01-28-2009 2:18 PM
0 Kudos

Hi,

Please check whether you have assigned the following roles to the users:

1.BPEM End User

2.Every User Core Role

For Further details refer Step 5 :Create Users and Grant Access in [this|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/501bd56f-a5a6-2b10-4fbf-a61a64055fe4] document.

After doing this login to the portal again. Then you can see the tasks assigned.

Regards,

Gayathri.

Former Member
‎01-28-2009 2:28 PM
0 Kudos

Hi,

Can you check whether you have got any exceptions in process monitoring( error log).

In NWA the tasks will be shown only when user claims the task. That is the user should open it. Only then it will be logged in nwa.

Hope it helps.

Regards,

Srinivasan Subbiah

Answers (2)

Answers (2)

Former Member
‎01-29-2009 4:34 PM
0 Kudos

The hint of Julius in [this|; thread helped. Just maintained the locale/timezone and restarted the server.

Thanks to all that helped.

Show replies
Show replies
Former Member
‎01-28-2009 4:49 PM
0 Kudos

@Gayathri: The user has both roles. In the document you provided there was no section 5 that described the creation of the user. But I am pretty sure that the user itself is fine. Are there any additional customization tasks for the portal to show the tasks correctly in the UWL?

@Srinivasan: What exactly do you mean by Monitoring. Where can I find it in NWA? Do you mean the Log in Process Troubleshooting? There was not even one entry and I haven't been able to select anything in this view. Do I have to switch this feature on explicitely?

To investigate the problem I also created a process with only one system task executing a read operation. Even when I deploy and start this process I see the process instance as running but the system task is not executed. So I think it is no problem related to the user because this process doesn't even interact with a user and also does not run properly.

Thanks,

Mane

Edited by: Manfred Maierhofer on Jan 28, 2009 7:08 PM

Show replies
Show replies
Former Member
‎01-29-2009 5:14 AM
0 Kudos

Hi Manefred,

By monitoring i mean, managing process which we will do from nwa>operations management>processes and tasks-->manage processes.There itself you can see the error log if the process fails.

Regards,

Sriniavasan Subbiah

Former Member
‎01-29-2009 8:18 AM
0 Kudos

Thanks Srinivasan,

very good hint. All started Process are visible as "Running processes" and also "Failed processes". Here are the error logs. Looks like there is a problem with the language. I checked the DC and it is American English. I also set Englisch (USA) as language for the user but still same behaviour.

Edited: Looks like it is a problem with the locale/timezone as Julius describes [here|;. I did the default configuration wizard in NWA for setting the locale/timezone for BPM but nothing happened. Do I have to restart the CE Server or are there additional settings for locale/timezone?

Any hints???? Your help is really appreciated ...


com.sap.glx.core.kernel.api.TransitionRollbackException: Exception during prepare, rolling back
com.sap.glx.core.kernel.mmtx.AbstractTransactionBase.rollback(AbstractTransactionBase.java:517)
com.sap.glx.core.kernel.mmtx.AbstractTransaction.do_prepare(AbstractTransaction.java:174)
com.sap.glx.core.kernel.mmtx.AbstractTransaction.commit(AbstractTransaction.java:77)
com.sap.glx.core.kernel.execution.LeaderWorkerPool$Follower.run(LeaderWorkerPool.java:120)
com.sap.glx.core.resource.impl.common.WorkWrapper.run(WorkWrapper.java:58)
com.sap.glx.core.resource.impl.j2ee.ServiceUserManager$ServiceUserImpersonator$1.run(ServiceUserManager.java:116)
java.security.AccessController.doPrivileged(Native Method)
javax.security.auth.Subject.doAs(Subject.java:337)
com.sap.glx.core.resource.impl.j2ee.ServiceUserManager$ServiceUserImpersonator.run(ServiceUserManager.java:114)
com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
java.security.AccessController.doPrivileged(Native Method)
com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:169)

com.sap.glx.core.kernel.api.KernelException: javax.ejb.EJBTransactionRolledbackException: (Failed in component: sap.com/tc~bpem~tm~ear, BC-BMT-BPM-DSK) Exception raised from invocation of public com.sap.bpem.tm.ITaskInstance com.sap.bpem.tm.adapter.impl.GalaxyTaskProviderBean.createTaskInstance(com.sap.bpem.tm.adapter.TaskInstanceTO) method on bean instance com.sap.bpem.tm.adapter.impl.GalaxyTaskProviderBean@962eab for bean sap.com/tc~bpem~tm~ear*annotation|bpem~tm~ejb.jar*annotation|GalaxyTaskProviderBean in application sap.com/tc~bpem~tm~ear.; nested exception is: java.lang.IllegalArgumentException: language is not specified; nested exception is: javax.ejb.EJBException: (Failed in component: sap.com/tc~bpem~tm~ear, BC-BMT-BPM-DSK) Exception raised from invocation of public com.sap.bpem.tm.ITaskInstance com.sap.bpem.tm.adapter.impl.GalaxyTaskProviderBean.createTaskInstance(com.sap.bpem.tm.adapter.TaskInstanceTO) method on bean instance com.sap.bpem.tm.adapter.impl.GalaxyTaskProviderBean@962eab for bean sap.com/tc~bpem~tm~ear*annotation|bpem~tm~ejb.jar*annotation|GalaxyTaskProviderBean in application sap.com/tc~bpem~tm~ear.; nested exception is: java.lang.IllegalArgumentException: language is not specified
com.sap.glx.core.kernel.mmtx.PrimaryTransaction.inPrepare(PrimaryTransaction.java:150)
... (11 more)

javax.ejb.EJBTransactionRolledbackException: (Failed in component: sap.com/tc~bpem~tm~ear, BC-BMT-BPM-DSK) Exception raised from invocation of public com.sap.bpem.tm.ITaskInstance com.sap.bpem.tm.adapter.impl.GalaxyTaskProviderBean.createTaskInstance(com.sap.bpem.tm.adapter.TaskInstanceTO) method on bean instance com.sap.bpem.tm.adapter.impl.GalaxyTaskProviderBean@962eab for bean sap.com/tc~bpem~tm~ear*annotation|bpem~tm~ejb.jar*annotation|GalaxyTaskProviderBean in application sap.com/tc~bpem~tm~ear.; nested exception is: java.lang.IllegalArgumentException: language is not specified; nested exception is: javax.ejb.EJBException: (Failed in component: sap.com/tc~bpem~tm~ear, BC-BMT-BPM-DSK) Exception raised from invocation of public com.sap.bpem.tm.ITaskInstance com.sap.bpem.tm.adapter.impl.GalaxyTaskProviderBean.createTaskInstance(com.sap.bpem.tm.adapter.TaskInstanceTO) method on bean instance com.sap.bpem.tm.adapter.impl.GalaxyTaskProviderBean@962eab for bean sap.com/tc~bpem~tm~ear*annotation|bpem~tm~ejb.jar*annotation|GalaxyTaskProviderBean in application sap.com/tc~bpem~tm~ear.; nested exception is: java.lang.IllegalArgumentException: language is not specified
com.sap.engine.services.ejb3.runtime.impl.TransactionAttributeHandler$Required.error(TransactionAttributeHandler.java:307)
com.sap.engine.services.ejb3.runtime.impl.TransactionAttributeHandler$TransactionAttributeErrorsHandler.error(TransactionAttributeHandler.java:130)
com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:40)
com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
$Proxy510.createTaskInstance(Unknown Source)
com.sap.bpem.tm.adapter.invocation.CreateTaskManagmentObject.persist(CreateTaskManagmentObject.java:144)
... (12 more)

javax.ejb.EJBException: (Failed in component: sap.com/tc~bpem~tm~ear, BC-BMT-BPM-DSK) Exception raised from invocation of public com.sap.bpem.tm.ITaskInstance com.sap.bpem.tm.adapter.impl.GalaxyTaskProviderBean.createTaskInstance(com.sap.bpem.tm.adapter.TaskInstanceTO) method on bean instance com.sap.bpem.tm.adapter.impl.GalaxyTaskProviderBean@962eab for bean sap.com/tc~bpem~tm~ear*annotation|bpem~tm~ejb.jar*annotation|GalaxyTaskProviderBean in application sap.com/tc~bpem~tm~ear.; nested exception is: java.lang.IllegalArgumentException: language is not specified
com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:83)
com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
... (26 more)

java.lang.IllegalArgumentException: language is not specified
com.sap.glx.handler.text.TextManager.createLocaleFallback(TextManager.java:341)
com.sap.glx.handler.text.TextManager.getTexts(TextManager.java:149)
com.sap.glx.handler.text.TextManager.initializeTextCache(TextManager.java:299)
com.sap.bpem.tm.impl.TaskManagerImpl.createTaskInstance(TaskManagerImpl.java:139)
com.sap.bpem.tm.adapter.impl.GalaxyTaskProviderBean.createTaskInstance(GalaxyTaskProviderBean.java:40)
sun.reflect.GeneratedMethodAccessor1476.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:585)
... (32 more)

Edited by: Manfred Maierhofer on Jan 29, 2009 9:37 AM

Ask a Question