Get latest workflow instance programatically?

hi,
i am building sate machine workflow and when i upgrade the solution another workflow instance is created when workflow starts again.
now i want to get latest workflow instance problematically.
thanks,
gaurav.

Hi Jassik112,
You can use the following code get the latest work flow instance. Use bubble sort method.
public SPWorkflow GetTheLatestWorkflowInstance(SPListItem myitem)
SPWorkflowCollection ss = myitem.Workflows;
SPWorkflow[] sort = new SPWorkflow[ss.Count];
int k = 0;
foreach (SPWorkflow ghy in ss)
sort[k] = ghy;
k++;
SPWorkflow temp = null;
int i, j;
for (i = 0; i < sort.Length; i++)
for (j = i + 1; j < sort.Length; j++)
if (sort[i].Created < sort[j].Created)
temp = sort[i];
sort[i] = sort[j];
sort[j] = temp;
return sort[0];
Thanks,
Jack
Jack Gao
TechNet Community Support

Similar Messages

Getting WLI Workflow Instance getting NULL.

Hi All WLI Users,
I am getting following problem while executing WLI workflow. After work
flow gets triggered by an XML event and instantiated, after some time workflow
instance becomes null.
and the execution is aborted. Kindly give me a solution to this problem.
Thanks
Kiran

Hi tony
It won't be possible for us to send us the workflow, beacuse it has
lots of interfaces
like MQ series and TCP/IP adpater.
But I can explain u in brief the workflow.
Workflow sends message to HOST1 after getting successfull response
from HOST1 it sends
another request to HOST2 and waits for the response.
Now this can iterate for say 200-500 times (depends on response
from HOST1).
Each message length is aroung 5000 bytes.During this iteration the
instance somehow sets to NULL.
I hope you can simulate the same at your end.
Also note we also do XML transformation before sending the request.
Thanks
"tony lodge" <[email protected]> wrote in message
news:[email protected]...
Hi
I recommend given this level of detail you open a case, what I amseeing
looks like a valid bug. Please provide the sample workflow if possible
Tony
"Saurabh" <[email protected]> wrote in message
news:[email protected]...
Hi,
The Versio ni am using is wlisp2.1 (service pack 2.1)
and Exception Stack trace is as follows,
<Mar 30, 2002 1:53:55 AM GMT-05:00> <Error> <T3Services> <Workflowtrace:Template=28003
Template Definition=31003
Instance=null>
Workflow warning: com.bea.wlpi.common.WorkflowException: The system
could
not
find the specified workflow instance: null.
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.getWorkflowInsta
nce(WorkflowProcessorBean.java:537)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.getWorkflowInsta
nceData(WorkflowProcessorBean.java:551
atcom.bea.wlpi.server.workflow.Variable.setValue(Variable.java:92)
atcom.bea.wlpi.server.workflow.Workflow.setVariable(Workflow.java:833)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.setVariableValue
(WorkflowProcessorBean.java:1017)
at
com.bea.wlaiplugin.server.WLAIServiceImpl.execute(WLAIServiceImpl.java:211)
atcom.bea.wlpi.server.workflow.action.ActionPlugin.execute(ActionPlugin.java:1
23)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
at
com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
va:50)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
at
com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
va:50)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
at
com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
va:50)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
at
com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
va:50)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
at
com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
va:50)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
at
com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
va:50)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
at
com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
va:50)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
at
com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
va:50)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
at
com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
va:50)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
at
com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
va:50)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
at
com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
va:50)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
at
com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
va:50)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
at
com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
va:50)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Start.activate(Start.java:168)
at
com.bea.wlpi.server.workflow.Workflow.start(Workflow.java:657)
atcom.bea.wlpi.server.workflow.Workflow.instantiate(Workflow.java:617)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean$1.invoke(Workflo
wProcessorBean.java:713)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.performWithError
Handling(WorkflowProcessorBean.java:11
32)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.instantiate(Work
flowProcessorBean.java:709)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean_h7kt4j_EOImpl.in
stantiate(WorkflowProcessorBean_h7kt4j
_EOImpl.java:78)
at
com.bea.wlpi.server.eventprocessor.EventProcessor.checkTrigger(EventProcesso
r.java:358)
at
com.bea.wlpi.server.eventprocessor.EventProcessor.onEvent(EventProcessor.jav
a:244)
at
com.bea.wlpi.server.eventlistener.EventListenerBean.onMessage(EventListenerB
ean.java:130)
at
weblogic.ejb20.internal.MDListener.execute(MDListener.java:254)
atweblogic.ejb20.internal.MDListener.onMessage(MDListener.java:206)
at
weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1864)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:1819)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
<Mar 30, 2002 1:53:55 AM GMT-05:00> <Notice> <EJB> <Error markingtransaction
for rollback: java.lang.IllegalStateException:
Cannot mark the transaction for rollback. xid=4883:97fdb06e981bb8b8,status=Rolled
back. [Reason=weblogic.transaction.interna
l.TimedOutException: Transaction timed out after 89 seconds
Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie
sOwedOthers=0,seconds
since begin=89,seconds left
=60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread
Group> > for Queue: 'default',ServerResourceInfo[weblo
gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
er]=(state=active),properties=({weblogic.jdbc=t3:
>
file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)]
java.lang.IllegalStateException: Cannot mark the transaction for
rollback.
xid=4883:97fdb06e981bb8b8,
status=Rolled back. [Re
ason=weblogic.transaction.internal.TimedOutException: Transaction timedout after
89 seconds
Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie
sOwedOthers=0,seconds
since begin=89,seconds left
=60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread
Group> > for Queue: 'default',ServerResourceInfo[weblo
gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
er]=(state=active),properties=({weblogic.jdbc=t3:
>
file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)]
at
weblogic.transaction.internal.TransactionImpl.throwIllegalStateException(Tra
nsactionImpl.java:1486)
at
weblogic.transaction.internal.TransactionImpl.setRollbackOnly(TransactionImp
l.java:466)
at
weblogic.ejb20.manager.BaseEJBManager.handleSystemException(BaseEJBManager.j
ava:255)
at
weblogic.ejb20.manager.BaseEJBManager.setupTxListener(BaseEJBManager.java:21
5)
at
weblogic.ejb20.manager.StatefulSessionManager.preInvoke(StatefulSessionManag
er.java:371)
at
weblogic.ejb20.manager.StatefulSessionManager.remove(StatefulSessionManager.
java:756)
at
weblogic.ejb20.internal.StatefulEJBObject.remove(StatefulEJBObject.java:87)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean_h7kt4j_EOImpl.re
move(WorkflowProcessorBean_h7kt4j_EOIm
pl.java:856)
at
com.bea.wlpi.server.eventprocessor.EventProcessor.clearSessionBeans(EventPro
cessor.java:510)
at
com.bea.wlpi.server.eventprocessor.EventProcessor.onEvent(EventProcessor.jav
a:284)
at
com.bea.wlpi.server.eventlistener.EventListenerBean.onMessage(EventListenerB
ean.java:130)
at
weblogic.ejb20.internal.MDListener.execute(MDListener.java:254)
atweblogic.ejb20.internal.MDListener.onMessage(MDListener.java:206)
at
weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1864)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:1819)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>
javax.transaction.TransactionRolledbackException: EJB Exception: :weblogic.transaction.internal.TimedOutException:
Transacti
on timed out after 89 seconds
Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie
sOwedOthers=0,seconds
since begin=89,seconds left
=60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread
Group> > for Queue: 'default',ServerResourceInfo[weblo
gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
er]=(state=active),properties=({weblogic.jdbc=t3:
>
file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)
at
weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransaction
Impl.java:1122)
at
weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTr
ansactions(ServerTransactionManagerImp
l.java:441)
at
weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManag
erImpl.java:1581)
at
weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTran
sactionManagerImpl.java:404)
at
weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManage
rImpl.java:1547)
at java.lang.Thread.run(Thread.java:484)
--------------- nested within: ------------------
weblogic.transaction.RollbackException: Transaction timed out after 89seconds
>
Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie
sOwedOthers=0,seconds
since begin=89,seconds left
=60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread
Group> > for Queue: 'default',ServerResourceInfo[weblo
gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
er]=(state=active),properties=({weblogic.jdbc=t3:
>
file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)
- with nested exception:
[weblogic.transaction.internal.TimedOutException: Transaction timed out
after> > 89 seconds> >>Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie> sOwedOthers=0,seconds> > since begin=89,seconds left> > =60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread> Group> > for Queue: 'default',ServerResourceInfo[weblo
gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
er]=(state=active),properties=({weblogic.jdbc=t3:
>
file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)]
at
weblogic.transaction.internal.TransactionImpl.throwRollbackException(Transac
tionImpl.java:1475)
at
weblogic.transaction.internal.ServerTransactionImpl.registerSynchronization(
ServerTransactionImpl.java:435)
at
weblogic.ejb20.internal.TxManager.registerSynchronization(TxManager.java:157
at
weblogic.ejb20.manager.BaseEJBManager.setupTxListener(BaseEJBManager.java:21
0)
at
weblogic.ejb20.manager.StatefulSessionManager.preInvoke(StatefulSessionManag
er.java:371)
at
weblogic.ejb20.manager.StatefulSessionManager.remove(StatefulSessionManager.
java:756)
at
weblogic.ejb20.internal.StatefulEJBObject.remove(StatefulEJBObject.java:87)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean_h7kt4j_EOImpl.re
move(WorkflowProcessorBean_h7kt4j_EOIm
pl.java:856)
at
com.bea.wlpi.server.eventprocessor.EventProcessor.clearSessionBeans(EventPro
cessor.java:510)
at
com.bea.wlpi.server.eventprocessor.EventProcessor.onEvent(EventProcessor.jav
a:284)
at
com.bea.wlpi.server.eventlistener.EventListenerBean.onMessage(EventListenerB
ean.java:130)
at
weblogic.ejb20.internal.MDListener.execute(MDListener.java:254)
atweblogic.ejb20.internal.MDListener.onMessage(MDListener.java:206)
at
weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1864)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:1819)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
; nested exception is:
weblogic.transaction.RollbackException: Transaction timed outafter 89
seconds
Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie
sOwedOthers=0,seconds
since begin=89,seconds left
=60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread
Group> > for Queue: 'default',ServerResourceInfo[weblo
gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
er]=(state=active),properties=({weblogic.jdbc=t3:
>
file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)
- with nested exception:
[weblogic.transaction.internal.TimedOutException: Transaction timed out
after> > 89 seconds> >>Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie> sOwedOthers=0,seconds> > since begin=89,seconds left> > =60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread> Group> > for Queue: 'default',ServerResourceInfo[weblo
gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
er]=(state=active),properties=({weblogic.jdbc=t3:
>
file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)]
weblogic.transaction.internal.TimedOutException: Transaction timed outafter 89
seconds
Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie
sOwedOthers=0,seconds
since begin=89,seconds left
=60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread
Group> > for Queue: 'default',ServerResourceInfo[weblo
gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
er]=(state=active),properties=({weblogic.jdbc=t3:
>
file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)
at
weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransaction
Impl.java:1122)
at
weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTr
ansactions(ServerTransactionManagerImp
l.java:441)
at
weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManag
erImpl.java:1581)
at
weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTran
sactionManagerImpl.java:404)
at
weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManage
rImpl.java:1547)
at java.lang.Thread.run(Thread.java:484)
--------------- nested within: ------------------
weblogic.transaction.RollbackException: Transaction timed out after 89seconds
>
Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie
sOwedOthers=0,seconds
since begin=89,seconds left
=60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread
Group> > for Queue: 'default',ServerResourceInfo[weblo
gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
er]=(state=active),properties=({weblogic.jdbc=t3:
>
file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)
- with nested exception:
[weblogic.transaction.internal.TimedOutException: Transaction timed out
after> > 89 seconds> >>Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie> sOwedOthers=0,seconds> > since begin=89,seconds left> > =60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread> Group> > for Queue: 'default',ServerResourceInfo[weblo
gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
er]=(state=active),properties=({weblogic.jdbc=t3:
>
file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)]
at
weblogic.transaction.internal.TransactionImpl.throwRollbackException(Transac
tionImpl.java:1475)
at
weblogic.transaction.internal.ServerTransactionImpl.registerSynchronization(
ServerTransactionImpl.java:435)
at
weblogic.ejb20.internal.TxManager.registerSynchronization(TxManager.java:157
at
weblogic.ejb20.manager.BaseEJBManager.setupTxListener(BaseEJBManager.java:21
0)
at
weblogic.ejb20.manager.StatefulSessionManager.preInvoke(StatefulSessionManag
er.java:371)
at
weblogic.ejb20.manager.StatefulSessionManager.remove(StatefulSessionManager.
java:756)
at
weblo

BPM an Mapping: Get the workflow instance number?

Hi everybody,
wen need in some cases the message-ID that was generated in message-mapping.
But when I take this message-ID and try to find it via SXMB_MONI the message could'nt be found due to reasons I do not know.
So now I would like to capture the BPM instance number. Is this possible in message-mapping?
Thanks regards
Mario

I doubt you would be able to get the BPM instance no. However, I don't understand why u r facing problem with message ID.
Regards,
Prateek

How to get workflow instance for a workitemid

Hi all ,
I have a requirement where i need to get the workflow instance from a perticular workitem id .
I have searched the forum , i dint get anything .No standard FM is also there .
Please guide me on the same .
regards
sarmistha

Hi Sarmistha,
If you workitem ID open the workitem in SWI1/SWIA tcode. Click on workflow log (shiftF8). then click on List with technical details icon (shiftF9). now click on your workflow description (first step under steps column). The workitem ID given in the details column is the workflow instance ID.
If you have queries let me know.
Regards,
Raj

How to get latest instance using BO Enerprise SDK?

Post Author: sureshpolishetty
CA Forum: .NET
How to get the lastest instance of a report stored in crystal enterprise server (XIR2) using BO Enterprise sdk and .NET?.
Can anybody help me with the query(using CI_INFOOBJECTS table)?
Thanks

Post Author: Argan
CA Forum: .NET
Select SI_LAST_SUCCESSFUL_INSTANCE_ID from ci_infoobjects where si_name = 'Charting'
Jason

Note: Due to heavy load, the latest workflow operation has been queued. It will attempt to resume at a later time

Dear all,
sorry for opening another thread on this.
I think I have a performance issue with workflows attached to document sets in SharePoint. And I say “I think” because people keep telling me that this is the way it just is.
The user creates a new document set, which triggers a workflow in which the user has to confirm/review/approve a series of tasks. The time it takes from clicking the OK button on those task form to the workflow status moving to the next step is about 4 seconds.
And visiting that status page within those 4 seconds brings up the infamous “Note: Due to heavy load, the latest workflow operation has been queued. It will attempt to resume at a later time.” message.
Hitting Refresh in the browser after those 4 seconds will make the new workflow status appear and the red text go away.
Is that normal? Is that the performance that everyone else is seeing as well?
I struggle to see why simply moving a workflow from one task to another should take that on a machine that isn’t doing anything else at the time.
(1)
I have a standalone (non-clustered) SharePoint box, 4 CPUs, 8 GB of memory, more than half of that available, acting as application server and wfe; only the database is on different box.
(2)
The CPU only goes up to 18 or 19%, so CPU does not seem to be the bottleneck. Half the RAM is also still free.
(3)
The workflow is designed with Nintex, and has about 9 flexi and review tasks – the last 2 of them in a loop iterating over typically 3 or 4 items.
(4)
Looking at the logs it looks like the processing in Nintex only takes about 1 second – I don’t know where the other 3 seconds are going.
(5)
There is nothing obvious in the logs.
(6)
We’ve looked at all the “theoretical” improvements around throttling and batch sizes etc. – none of them appeared make any difference. And the workflow is so small that it looks like my tasks gets executed straight away. The problem appears
to be that the execution takes too long(?) and therefore has not finished by the time the page get redrawn.
(7)
I am running perfmon and I can e.g. see one(!) workflow being loaded into memory – as expected as I am the only user.
(8)
I am seeing a total of 3(?) SQL queries being executed(?). I get the Bytes Sent/sec spiking at 25K, and Bytes received at 18K. But is this good or bad or a bottleneck?
Where do I take it from here?
I have been told that “[…] most customers have no issue with this as they are used to the way SP operates and it can be slow at times.” Is it really that bad?
If it is worth watching more performance counters then I’d need to know what to compare them to.
Is there something else I am missing?
Thanks
Martin

Hi,
Before considering an additional hardware try to change following configurations for workflow:
Increase Throttle Size
Increase Batch Size
Time Out
Workflow Timer Interval
AutoCleanUpDays
Increase Throttle Size
The Workflow throttle setting controls how many Workflows can be processing at any one time on the entire server farm. By increasing the throttle it will allow the number of Workflows execution or can be initiated at a time.
Use below PowerShell command to get the current Throttle Size:
Get-SPFarmConfig | Select WorkflowPostponeThreshold
Use below PowerShell command to set new Throttle Size:
Set-SPFarmConfig -WorkflowPostponeThreshold 100
Increase Batch Size
This is the size that determines number of events processed for a single Workflow instance. Default value is 100, but it can be range from 1 to any number.
Use below PowerShell command to get the current Batch Size:
Get-SPFarmConfig | Select WorkflowBatchSize
Use below PowerShell command to set new Batch Size:
Set-SPFarmConfig -WorkflowBatchSize 200
Time Out
This decides the time out of the Workflow event. The default value is 5 and can be any integer. The time is in minute.
Use below STSADM command to get the current Time Out value:
stsadm -o getproperty -pn workflow-eventdelivery-timeout
Use below STSADM command to get the current Time Out value:
stsadm -o setproperty -pn workflow-eventdelivery-timeout -pv “15″
Workflow Timer Interval
This setting is applicable at Web Application level and not the farm level. The workflow timer interval specifies how often the workflow SPTimer job fires to process pending workflow tasks. This interval also represents the granularity of delay timers within
your workflow. If a timer is set to delay for one minute, but the interval timer fires only every five minutes, the workflow delays for five minutes, not one minute.
Use below STSADM command to get the current Workflow Timer Interval value:
stsadm -o getproperty -pn job-workflow -url <Web Application Url>
Use below STSADM command to get the current Workflow Timer Interval value:
stsadm -o setproperty -pn job-workflow -pv “Every 10 minutes between 0 and 30″ -url <Web Application Url>
Here is the url for reference :
http://praveenkasireddy.wordpress.com/2013/06/14/workflow-due-to-heavy-load-the-latest-workflow-operation-has-been-queued-it-will-attempt-to-resume-at-a-later-time/

Due to heavy load, the latest workflow operation has been queued. It will attempt to resume at a later time.

I have SharePoint 2010 Enterprise running SP1. Configuration is one SharePoint server in the farm and a SQL 2008 R2 database for the backend. Our user environment is 80 users with very little load on the SharePoint server. I have the workflow timer
set to 1 minute.
I have a SPD workflow that starts manually on a form library. Whenever I publish a new version of the workflow, the next time I start the workflow it takes the full minute to finish. If I click on the workflow status before it finishes, I see the message
"Due to heavy load, the latest workflow operation has been queued. It will
attempt to resume at a later time.". After the minute completes the workflow finishes.
Here's the weird thing, the next time I start the workflow, it runs in a couple of seconds - almost instantly. I've tried up to 15 times after the inital publishing and everything seems to work fine on initiation.
Well, that would be fine for me, however, I intermintantly get this heavy load message during task processes that are running inside the workflow. It's probably less than 5% of the time. It's really frustrating though so I appreciate some help. I'm look
online and haven't found anything that describes my situation.
Thank you in advance!

Hi,
Before considering an additional hardware try to change following configurations for workflow:
Increase Throttle Size
Increase Batch Size
Time Out
Workflow Timer Interval
AutoCleanUpDays
Increase Throttle Size
The Workflow throttle setting controls how many Workflows can be processing at any one time on the entire server farm. By increasing the throttle it will allow the number of Workflows execution or can be initiated at a time.
Use below PowerShell command to get the current Throttle Size:
Get-SPFarmConfig |
Select WorkflowPostponeThreshold
Use below PowerShell command to set new Throttle Size:
Set-SPFarmConfig -WorkflowPostponeThreshold
100
Increase Batch Size
This is the size that determines number of events processed for a single Workflow instance. Default value is 100, but it can be range from 1 to any number.
Use below PowerShell command to get the current Batch Size:
Get-SPFarmConfig |
Select WorkflowBatchSize
Use below PowerShell command to set new Batch Size:
Set-SPFarmConfig -WorkflowBatchSize
200
Time Out
This decides the time out of the Workflow event. The default value is 5 and can be any integer. The time is in minute.
Use below STSADM command to get the current Time Out value:
stsadm -o getproperty -pn workflow-eventdelivery-timeout
Use below STSADM command to get the current Time Out value:
stsadm -o setproperty -pn workflow-eventdelivery-timeout -pv “15″
Workflow Timer Interval
This setting is applicable at Web Application level and not the farm level. The workflow timer interval specifies how often the workflow SPTimer job fires to process pending workflow tasks. This interval also represents the granularity of delay timers within
your workflow. If a timer is set to delay for one minute, but the interval timer fires only every five minutes, the workflow delays for five minutes, not one minute.
Use below STSADM command to get the current Workflow Timer Interval value:
stsadm -o getproperty -pn job-workflow -url <Web Application Url>
Use below STSADM command to get the current Workflow Timer Interval value:
stsadm -o setproperty -pn job-workflow -pv “Every 10 minutes between 0 and 30″ -url <Web Application Url>
Here is the url for reference :
http://praveenkasireddy.wordpress.com/2013/06/14/workflow-due-to-heavy-load-the-latest-workflow-operation-has-been-queued-it-will-attempt-to-resume-at-a-later-time/

Workflow. Latest workflow operation has been queued

Good day,
I have sequential workflow which Is started after item created in list. Sometimes, after start of workflow in status I can
see note:
Due to heavy load, the latest workflow
operation has been queued. It will attempt to resume at a later time.
After several page refreshes it disappears.
Can I somehow make this note not to appear?

Hi,
Before considering an additional hardware try to change following configurations for workflow:
Increase Throttle Size
Increase Batch Size
Time Out
Workflow Timer Interval
AutoCleanUpDays
Increase Throttle Size
The Workflow throttle setting controls how many Workflows can be processing at any one time on the entire server farm. By increasing the throttle it will allow the number of Workflows execution or can be initiated at a time.
Use below PowerShell command to get the current Throttle Size:
Get-SPFarmConfig | Select WorkflowPostponeThreshold
Use below PowerShell command to set new Throttle Size:
Set-SPFarmConfig -WorkflowPostponeThreshold 100
Increase Batch Size
This is the size that determines number of events processed for a single Workflow instance. Default value is 100, but it can be range from 1 to any number.
Use below PowerShell command to get the current Batch Size:
Get-SPFarmConfig | Select WorkflowBatchSize
Use below PowerShell command to set new Batch Size:
Set-SPFarmConfig -WorkflowBatchSize 200
Time Out
This decides the time out of the Workflow event. The default value is 5 and can be any integer. The time is in minute.
Use below STSADM command to get the current Time Out value:
stsadm -o getproperty -pn workflow-eventdelivery-timeout
Use below STSADM command to get the current Time Out value:
stsadm -o setproperty -pn workflow-eventdelivery-timeout -pv “15″
Workflow Timer Interval
This setting is applicable at Web Application level and not the farm level. The workflow timer interval specifies how often the workflow SPTimer job fires to process pending workflow tasks. This interval also represents the granularity of delay timers within
your workflow. If a timer is set to delay for one minute, but the interval timer fires only every five minutes, the workflow delays for five minutes, not one minute.
Use below STSADM command to get the current Workflow Timer Interval value:
stsadm -o getproperty -pn job-workflow -url <Web Application Url>
Use below STSADM command to get the current Workflow Timer Interval value:
stsadm -o setproperty -pn job-workflow -pv “Every 10 minutes between 0 and 30″ -url <Web Application Url>
Here is the url for reference :
http://praveenkasireddy.wordpress.com/2013/06/14/workflow-due-to-heavy-load-the-latest-workflow-operation-has-been-queued-it-will-attempt-to-resume-at-a-later-time/

Error while creating concurrent workflow instances with dynamic participant

Hi All,
I have a workflow which has 3 interactive activites. The second interactive activity has requires approval of atleast 3 users to proceed. The participants are also not known in advance and are created dynamically by creating the directory session. The workflow is instantiated using an external trigger. The approval for interactive activities is also provided by an external trigger (API call).
Now, there is a scenario where i have 1000 requests coming in to ALBPM and workflow instance should be created for each of them. But only one instance is created and for the rest i get the following exception. This also happens with just 2 requests. I also tried calling the API in a synchronized way but didnt help.
Is anybody aware why is this error encountered anf how it can be resolved?
java.lang.IllegalStateException: Cannot set the directory Connector Service while connector service is started
at fuego.connector.CompositeConnectorService.setDirectoryConnectorService(CompositeConnectorService.java:97)
at fuego.connector.CompositeConnectorService.restartDirectoryConnectorService(CompositeConnectorService.java:52)
at fuego.directory.DirectoryConfigurationManager.loadDirectoryConfiguration(DirectoryConfigurationManager.java:265)
at fuego.directory.DirectoryConfigurationManager.getDirectoryConfiguration(DirectoryConfigurationManager.java:217)
at fuego.directory.DirectoryConfigurationManager.getDirectoryConfigType(DirectoryConfigurationManager.java:199)
at fuego.directory.provider.Factory.getDirectoryFactory(Factory.java:214)
at fuego.directory.Directory.fillPassport(Directory.java:122)
at fuego.directory.DirectoryPassport.fillPassport(DirectoryPassport.java:274)

Hi Dan,
Thanks for replying and giving attention. I have the following scenario :-
1. I am getting a list of identifiers(some number) from a third party application along with the users/participants who are liable to approve the workflow instance.
2. I create a workflow instance using this identifier through PAPI using process service session and also create the user/participant through PAPI by using the following code. Please note that i dont create participant in ALBPM instead i do it programatically in java using the PAPI :-
DirectorySession directorysession = null;
if (userVO != null && userVO.getUserId() != null && !userVO.getUserId().trim().equals(""))
+{+
+     directorysession = this.createFDISession();+
+     List<RoleAssignment> roleAssignmentList = new ArrayList<RoleAssignment>();+
+     try {+
DirOrganizationalRole[] dirOrganizationalRoleArray = DirOrganizationalRole.fetchAll(directorysession);
for(int i=0; dirOrganizationalRoleArray!=null && i<dirOrganizationalRoleArray.length; i+) {+
+DirOrganizationalRole role = dirOrganizationalRoleArray;+
+}+
int permissions = -1;
permissions
+= 0 |+
DirHumanParticipant.getPermissionValue("X") |
DirHumanParticipant.getPermissionValue("R") |
DirHumanParticipant.getPermissionValue("S") |
DirHumanParticipant.getPermissionValue("A") |
DirHumanParticipant.getPermissionValue("D") |
DirHumanParticipant.getPermissionValue("E") |
+0;+
+String[] whichRoles = new String[]{+
+"Approver",+
+"Requestor",+
+};+
+DirHumanParticipant.RoleAssignment[] roleAssignments = new DirHumanParticipant.RoleAssignment[whichRoles.length];+
for(int i=0; i<whichRoles.length; i+) {+
+roleAssignments[i] = new DirHumanParticipant.RoleAssignment(whichRoles[i], permissions, DirOrganizationalRole.fetch(directorysession, whichRoles[i]).getIn());+
+}+
+     String organizationUnit = configuration.getProperty("ORGANIZATION_UNIT");//fuegoFileProperties.getProperty(BVIDConstants.FUEGO_CONNECTIVITY_KEY_ORGANIZATION_UNIT);+
+     String newUserPwd = configuration.getProperty("FUEGO_FDI_NEW_USER_PASSWORD");//fuegoFileProperties.getProperty(BVIDConstants.FUEGO_CONNECTIVITY_KEY_FDI_PWD);+
+     DirOrganizationalUnit orgUnit = DirOrganizationalUnit.fetch(directorysession,organizationUnit);+
+     DirHumanParticipant user = DirHumanParticipant.create(directorysession, userVO.getUserId(), userVO.getFirstName(), userVO.getLastName(),+
+                              userVO.getFirstName(), userVO.getEmail(), userVO.getPhone(), "",+
+                              newUserPwd, orgUnit,roleAssignments, true);+
+     user.update();+
+     }+
+     finally+
+     {+
+               log.info("diconnecting the directory session created for creating participant");+
+               directorysession.disconnect();+
+     }+
+}+
3. The workflow instance then waits at interactive activity to get the next trigger with the same identifier to move the workflow ahead.
4. Now the case is that i can get 1000 such identifiers at a time in a file which i ll read for which i need to create 1000 workflow instances parallely. During this process i get the following exception : -
java.lang.IllegalStateException: Cannot set the directory Connector Service while connector service is started
at fuego.connector.CompositeConnectorService.setDirectoryConnectorService(CompositeConnectorService.java:97)
at fuego.connector.CompositeConnectorService.restartDirectoryConnectorService(CompositeConnectorService.java:52)
at fuego.directory.DirectoryConfigurationManager.loadDirectoryConfiguration(DirectoryConfigurationManager.java:265)
at fuego.directory.DirectoryConfigurationManager.getDirectoryConfiguration(DirectoryConfigurationManager.java:217)
at fuego.directory.DirectoryConfigurationManager.getDirectoryConfigType(DirectoryConfigurationManager.java:199)
at fuego.directory.provider.Factory.getDirectoryFactory(Factory.java:214)
at fuego.directory.Directory.fillPassport(Directory.java:122)
at fuego.directory.DirectoryPassport.fillPassport(DirectoryPassport.java:274)
Please let me know if you need any more information. awaiting your help
Thanks,
Anand

At odd times I will get a second instance of Firefox startup. I have run avast av, spybot, malwarebytes, both in normal and safe mode and nothing has been found, any ideas?

at odd times I will get a second instance of Firefox startup. I have run avast av, spybot, malwarebytes, both in normal and safe mode and nothing has been found, any ideas?

That second one sounds like malware.
Do a malware check with some malware scanning programs on the Windows computer.<br />
You need to scan with all programs because each program detects different malware.<br />
Make sure that you update each program to get the latest version of their databases before doing a scan.<br /><br />
*http://www.malwarebytes.org/mbam.php - Malwarebytes' Anti-Malware
*http://www.superantispyware.com/ - SuperAntispyware
*http://www.microsoft.com/security/scanner/en-us/default.aspx - Microsoft Safety Scanner
*http://www.microsoft.com/windows/products/winfamily/defender/default.mspx - Windows Defender: Home Page
*http://www.safer-networking.org/en/index.html - Spybot Search & Destroy
*http://www.lavasoft.com/products/ad_aware_free.php - Ad-Aware Free
See also:
*"Spyware on Windows": http://kb.mozillazine.org/Popups_not_blocked

How to pick up the latest report instance of a schedueld report

Hi,
I am supporting a custom application (.NET), which has to pick up the latest report instance by accepting the Report ID.
At times, the application does seems to be pick up the wrong (older) instance. This is not happening all the times but certain reports behaves this way once a while.
This is how the application seems to be determining the latest instance.
SELECT * FROM CI_INFOOBJECTS
WHERE SI_PROGID = 'CrystalEnterprise.Report'
AND SI_INSTANCE_OBJECT = 1
AND SI_SCHEDULE_STATUS = 1
AND SI_PARENTID= '" + id + "'
ORDER BY SI_ID DESC
Once the above statement returns all the available instances it just pick up the very first instance and returns it back to the application and it gets displayed through the Report Viewer.
My question here is that, does this order (ORDER BY SI_ID DESC) will always return me the latest instance first? When I manually verify the instance ID, it seems to be getting incremented eventhough it is a random number.
When I review the InfoView code, which also seems to be doing the same thing I have found that it is using SI_UPDATE_TS instead of SI_ID.
Could someone please tell me which is the correct one to use? I tried by could not able to find references anywhere.
Environment: BO XI R2 - SP2

Jason,
Thanks for the info. The query builder o/p and the application o/p are the same. When this situation happened last time I just simply deleted those older instances from the history and left only the current one.
This has forced the query to return the only available instance, which is the current one.
My suspect here is that, the SI_ID of a new instance is smaller than the older instance...
for example,
Instance 1 - 10023
Instance 2 - 12344
Instance 3 - 9892
Is this possible?? Since I have deleted the older instances I have no way to confirm this case unless it happens again.
The BO documentation about SI_ID reads like this...
"This property is used to uniquely identify an object. The number is assigned at creation time, and is never changed until the object is destroyed. You should never hard-code this number, however, since if the object is destroyed the number may be assigned to another object. No two objects have the same ID, even if they are different types of objects; that is, you will never find a report that has the same ID as a folder."
As it claims that an ID can be re-used if the object is destoryed I assume that though the new ID will be unique there is no guarantee that it will be bigger than the previous instance of the same object.
But the problem is that I dont have a documentation proof to claim this hence asking help from the guru's here...
Regards,
Elan.

Unhandled exception occurred during the execution of the workflow instance

I had a workflow and library working with no issues, but had to move the library and export the workflow to another subsite (though on the same web site/collection). I followed these how-tos:
http://msdn.microsoft.com/en-us/library/office/jj819316%28v=office.15%29.aspx
http://technet.microsoft.com/en-us/library/ee428301%28v=office.15%29.aspx
Anyway, I've stripped all actions from the workflow and only have an Assign Task, but get this below:
An unhandled exception occurred during the execution of the workflow instance. Exception details: System.ArgumentException: ContentTypeId at Microsoft.Activities.Hosting.Runtime.Subroutine.SubroutineChild.Execute(CodeActivityContext context) at System.Activities.CodeActivity.InternalExecute(ActivityInstance
instance, ActivityExecutor executor, BookmarkManager bookmarkManager) at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)
To troubleshoot, I removed all library columns, removed then re-added the Custom Content type the New Document uses, and still the same error - with the workflow going into Suspended mode.
I also tried the removal of the file from /Relationships%20List/allitems.aspx and de-activating then re-activating the SharePoint Publishing feature, also that didn't work.
I've gone into ULS, but unable to find anything definitive, so not sure what to try next?
Thank you,
Chad

Hi Chad,
Glad to hear the issue is resolved. Content types could be used for multiple lists in SharePoint site at the same time.
However, I'm not quite sure why you said the resolution is for a "bug". I read the article per your link:
http://www.andrewconnell.com/blog/SP2013-Workflow-Custom-Task-Outcomes
The article is showing how to create custom outcomes buttons in task forms. As I understand, the issue you encountered is that workflow migrated from the other site shows the suspended status.
Please be more specific on the issue if assistance is needed. If this is the second question, I’d recommend you open another thread in the relevant forum and provide specific information about the issue. In order to avoid confusion and keep track of troubleshooting
steps, we usually troubleshoot one issue per thread in order to find a resolution efficiently.
Thanks for the understanding.
Regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected] .
Rebecca Tu
TechNet Community Support

Cannot create process to handle workflow instance conversation

<Nov 18, 2002 1:04:30 PM IST> <Error> <B2B> <000000> <<Process>
Hi,
Iam getting following error when iam trying to invoke
subworkflow.
can anyone help me in solving this problem.
regards
Ananth
ERROR: Cannot cr
eate process null.>
<Nov 18, 2002 1:04:30 PM IST> <Error> <B2B> <000000> <<B2B-BPM-Plugin> ERROR:
Cannot create process to handle workflow instance conversation
com.bea.b2b.protocol.ProcessManager$CreateException: ERROR: Cannot create proces
s null.

Hi Ajaz,
Error description is not detailed enough to provide the solution. You need to post the error message what you got in the server log files. This should contain specific details about the issue.
Not sure but issue may be related to JVM settings. if it is so, server log file will provide the error description.

Change Workflow-Instance-Container values

Hi Experts,
I would like to ask you how to change a value in a container of a Workflow-"Instance".
For e.g.:
I have a workflow-instance which contains a (bor-) Object "Switchdocument". This switchdocument contains also a (Bor-) Object "serviceprovider". And I would like to change the value of the parameter of "serviceprovider".
How is the relationship between the "father"-object and the "child"-object and where are the relationship saved?
I know the table "sww_cont" and "sww_contob". But these tables are not enough, aren't?
Because in the mentioned tables (sww_cont) I see the elements with their values of the container of the workflow-instance. I don't the elements with their values of the object (father-object) contained in the workflow-instance-container and also not the elements with their values of the object (child-object) in the father-object.
or (explanation as a list)
Workflow-Instance-Container:
1.element
2.element
3. Switchdocument (object) (father-object)
3.1 element of switchdocument
3.2 .....
3.3 Serviceprovider (object) (child-object)
3.3.1 element of serviceprovider <--- here I would like to change the value
I hope I explained the situation in a detail way
I apologize if I don't use the right terms!
If anyone has a hint or a way to get to the "child-object" I would be very thankfull.
Thanks a lot for your answers in advance!!!
with lovely regards.

Hi all,
at first I thank you all for your answers!!!
As I understand the values are permanently saved in the subobjects. Like I said the subobject (Distributor) with the attribute, e.g. Serviceprovider in Own System = 'X' is contained in the Object Switchdocument.
That means for me that I have to retrieve the attribute of the subobject via a method for the special instance and change it, e.g. to set it blank.
I have forgotten to say that I am developing a report (se38) to change all attributes of workflow-instances with object/subobject.
As I said above in a condition step it is asked whether a "serviceprovider is in own system". if yes (means = "X") then the process has another way. And I have to change the "X" to "blank", so the workflow goes always the, in my case, second way.
For the next time, I will explain my problem in a more detail way
Thanks again.
with kind regards!

Get the Process Instance as a process variable

Hi,
is there a way on a Workflow Process to get the process instance in order to save it as a process variable (and then store it via a backend call).
In other words: I have many processes designed via NWDS Process Composer and I'd like to get the process instance ID in order to save it for faster retrieval of the process in the NWA's Manage Process application.
Thank you,
Pietro.

Does it work if the process instance is already created?
Can you give me an example?
I've put as the first step of every workflow a callback method that is executed that calls an RFC to confirm, backend-side, that the process has been created.

Get latest workflow instance programatically?

Similar Messages

Maybe you are looking for