Solved: unable to open bpm task in uwl

Hi experts,

I am getting below error to open BPM task -

Unable to open the task xxxxxxxxxxxxx because of technical issues. Contact your system administrator for more details.

Error getting suddenly and log message is - I/O problem occurred when executing Archiving Command indexdescribe.

Please clarify dependency here- If I deployed DC on server with some changes, and tried to open old task which is in NEW status, what would be the chances to get error.

I believe there is no dependency, please correct me and advice how to fix above error.

Thanks in advance.

Ian

SAP Managed Tags:
SAP Business Process Management

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (1)

Hi Ian,

If you made the changes to your BPM DC and deployed the same, Changes will not be reflected in already created task even if it is in NEW Status. You will have to trigger a new process to see the changes.

If you made the changes to your WD DC and deployed the same, Changes will be reflected to the UI part of the already created task as well as new one to be created.

Regards,

Unni

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Thanks Unni..

So is the error caused BPM DC deployment? If so, each transports movement happend we couldn't able to see old tasks which was having status in NEW..Is it right.

Thank you,

cheers,

Ian

HI Ian,

If you transport the new BPM process changes, the Tasks(in any Status already there ) which corresponds to previously deployed BPM process version can be accessed and worked upon without error. But these tasks will not be reflecting the new process changes you transported.

I am not sure why this error is coming. You can check SAP Note 1586832 whether it corresponds to the issue you are facing.

Are you getting this error for newly created task?

Regards,

Unni

Edited by: UnnikrishnanSreekumar on Dec 2, 2011 1:11 PM

Hi Unni,

After deployed BPM DC with some changes, I could able to open taks means no issues with newly created one, issue is with opening old task which have status NEW.

Thanks in advance,

Ian

BPM actually takes care of old task if a new process version is deployed. An exception to this would be cases where in sub-process calls are there. If there is a change interface of the start event of the sub-process, then process will fail.

Can you login to process monitor and extract the error log corresponding to this ? that would given a better insight into extactly what is the issue.

Regards,

Mahesh

Edited by: Mahesh K on Dec 6, 2011 11:31 AM

Hi all,

I am sorry to delay in reply, I went on vaction.

Still issue persists, and observed issue seems not deploying new version of BPM DC.

As per my application, once user submits WebDynpro application, UWL task will trigger. If I open the task no error coming out, otherwise If I opened the task after few hours I am getting error.

So far I thought issue with new version of BPM DC, but issue now seems in different way.

Please find log u2013

800#Error#com.sap.tc.bpem.nwa.processmgmt.procmgmt.procmgmt.ProcMgmt#

com.sap.BPM.nwa_pm.000006#BC-BMT-BPM-MON#sap.com/tc_bpemnwa_{processmgmt#3C4A9248728053DD0000000200004770#216718650000000004#sap.com/tc}lm_itsamui_mainframewd#com.sap.tc.bpem.nwa.processmgmt.procmgmt.procmgmt.ProcMgmt#Guest#0##5366996011D611E18AB900000CEADD3A#f7da953311d511e1c6fb00000ceadd3a#f7da953311d511e1c6fb00000ceadd3a#0#Thread[HTTP Worker [@1437481805],5,Dedicated_Application_Thread]#Plain##

Retrieval of Process instance details in 'Manage Process' has failed.Contact support.[Ljava.lang.StackTraceElement;@96dcd01#

#2.0 #2011 11 18 03:13:48:471#0-800#Error#com.sap.tc.bpem.nwa.processmgmt.procmgmt.procmgmt.ProcMgmt#

com.sap.BPM.nwa_pm.000021#BC-BMT-BPM-MON#sap.com/tc_bpemnwa_{processmgmt#3C4A9248728053DE0000000000004770#216718650000000004#sap.com/tc}lm_itsamui_mainframewd#com.sap.tc.bpem.nwa.processmgmt.procmgmt.procmgmt.ProcMgmt#Guest#0##5366996011D611E18AB900000CEADD3A#0f8a891811d611e1aba600000ceadd3a#0f8a891811d611e1aba600000ceadd3a#0#Thread[HTTP Worker [@1132952642],5,Dedicated_Application_Thread]#Plain##

Retrieval of Process instance details in 'Manage Process' has failed.[Ljava.lang.StackTraceElement;@7c47dd9d

[EXCEPTION]

com.sap.tc.lm.itsam.ui.proxy.exception.JMXAccessControlOperationException: Caller Guest not authorized, required permission missing (javax.management.MBeanPermission -\#fetchProcessInstanceInfo[com.sap.default:SAP_ITSAMGalaxyProcessManager.Name=SAP_ITSAMGalaxyProcessManager_EA5.SystemHome.abdbbh0,SAP_ITSAMJ2eeCluster.CreationClassName=SAP_ITSAMJ2eeCluster,SAP_ITSAMJ2eeCluster.Name=EA5.SystemHome.abdbbh0,cimclass=SAP_ITSAMGalaxyProcessManager,type=SAP_ITSAMJ2eeCluster.SAP_ITSAMGalaxyProcessManager,version=3.3] invoke)

at com.sap.tc.lm.itsam.ui.proxy.JMXGenericModelClassMBean.invokeOperation(JMXGenericModelClassMBean.java:632)

at com.sap.tc.lm.itsam.ui.proxy.JMXAbstractModelClass.invokeOperation(JMXAbstractModelClass.java:160)

at com.sap.tc.bpem.nwa.processmgmt.procmgmt.model.SAP_ITSAMGalaxyProcessManager.fetchProcessInstanceInfo(SAP_ITSAMGalaxyProcessManager.java:104)

at com.sap.tc.bpem.nwa.processmgmt.procmgmt.procmgmt.ProcMgmt.supplyInstances(ProcMgmt.java:2125)

at com.sap.tc.bpem.nwa.processmgmt.procmgmt.procmgmt.wdp.InternalProcMgmt.supplyInstances(InternalProcMgmt.java:479)

at com.sap.tc.bpem.nwa.processmgmt.procmgmt.procmgmt.wdp.IPublicProcMgmt$IInstancesNode.doSupplyElements(IPublicProcMgmt.java:2875)

at com.sap.tc.webdynpro.progmodel.context.DataNode.supplyElements(DataNode.java:108)

at com.sap.tc.webdynpro.progmodel.context.Node.getElementListAsObject(Node.java:263)

at com.sap.tc.webdynpro.progmodel.context.MappedNode.createMappedElementList(MappedNode.java:78)

at com.sap.tc.webdynpro.progmodel.context.MappedNode.supplyElements(MappedNode.java:71)

at com.sap.tc.webdynpro.progmodel.context.Node.getElementListAsObject(Node.java:263)

at com.sap.tc.webdynpro.progmodel.context.Node.getElements(Node.java:270)

at com.sap.tc.webdynpro.progmodel.context.Node.sortElements(Node.java:555)

at com.sap.lm.itsam.ui.util.table.TableSorter.sort(TableSorter.java:211)

at com.sap.lm.itsam.ui.util.table.TableSorter.<init>(TableSorter.java:138)

at com.sap.lm.itsam.ui.util.table.TableSorter.<init>(TableSorter.java:152)

at com.sap.lm.itsam.ui.util.table.TableAccessories.createSorter(TableAccessories.java:420)

at com.sap.lm.itsam.ui.util.table.TableAccessories.createSorter(TableAccessories.java:370)

at com.sap.tc.bpem.nwa.processmgmt.procmgmt.procmgmt.ProcMgmtView.wdDoModifyView(ProcMgmtView.java:329)

at com.sap.tc.bpem.nwa.processmgmt.procmgmt.procmgmt.wdp.InternalProcMgmtView.wdDoModifyView(InternalProcMgmtView.java:2547)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:94)

at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:746)

at com.sap.tc.webdynpro.progmodel.window.ViewController.modifyView(ViewController.java:254)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:432)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:438)

at com.sap.tc.webdynpro.clientserver.phases.ModifyViewPhase.execute(ModifyViewPhase.java:69)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)

at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:514)

at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:55)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1689)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1503)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:899)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessing(ApplicationSession.java:871)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:356)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:328)

at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)

at com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:89)

at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:62)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)

at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)

at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:404)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:203)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:440)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:429)

at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)