wf stops at background task in 'ready' status

[Sunni sunni]

Hi all
 
thanks for your replies.
SM58 was key, the client had made a client copy and not completed all the
client specific customising namely maintaining the rfc destination and
wf-batch user again - the workflow started but since the background user was
not maintained it didnt run.  SM58 showed the error, workflow local not
maintained... pointed me to SWU3
 
cheers
sunni
 
>From: Richard Marut <rvmarut at earthlink.net>
>Reply-To: SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
>To: SAP-WUG at MITVMA.MIT.EDU
>Subject: Re: wf stops at background task in 'ready' status
>Date: Tue, 9 Mar 2004 07:37:04 -0600
>
>Sunni,
>
>Are you using a fork in your workflow and is it after a 'wait for event'?
>
>I've had background tasks hang when I used a fork with one necessary branch
>and my task was after a 'wait for event' in a branch that was not the
>necessary branch. I moved it after the end of the fork and it worked.
>
>Richard...
>
>-----Original Message-----
>From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of Chris
>Pruitt
>Sent: Tuesday, March 09, 2004 7:01 AM
>To: SAP-WUG at MITVMA.MIT.EDU
>Subject: Re: wf stops at background task in 'ready' status
>
>Sunni,
>
>Have you looked in SM58 to see if they are hanging there?
>
>-Chris
>
>
>Chris Pruitt
>SI Corporation
>E-Mail: chris_pruitt at sind.com
>Mobile: 423-400-5661
>Office: 423-553-2053
>Fax: 423-553-2373
>
>-----Original Message-----
>From: Sunni sunni [mailto:sunnilondon at hotmail.com]
>Sent: Tuesday, March 09, 2004 4:47 AM
>To: SAP-WUG at MITVMA.MIT.EDU
>Subject: wf stops at background task in 'ready' status
>
>Hi
>
>I have a problem, the workflows are stopping on a background task, in
>status
>ready, it seems that the background method does not get kicked off from
>the
>workflow however I've tested it in SWO1 and the method is fine.  It
>works
>fine in the dev system and another system.  I've tried refreshing
>buffers,
>regenerating object, any ideas why this might occur??
>
>Many thanks
>Sunni
>
> >From: "Tom Olaf @ Spring" <tom.olaf at spring.no>
> >Reply-To: SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
> >To: SAP-WUG at MITVMA.MIT.EDU
> >Subject: Re: Task Stuck In Process
> >Date: Wed, 4 Feb 2004 13:42:45 +0100
> >
> >Hi.
> >
> >It seems the update task for the invoice transaction has not finished
> >(program RSM13000 is related to the update). This update is performed
> >asynchron to perform the actual update of the tables and locks the
>object.
> >When facing such a problem I have used the requested start option of
>the
> >activity definitions to delay the start of the background task for a
>few
> >minutes so that the update has finished. You can in addition or instead
>try
> >to lock the object in your method and create an exception that will
>lead to
> >reprocessing based on the error-monitoring job interval.
> >
> >Regards
> >Tom
> >
> >-----Original Message-----
> >From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]On Behalf Of
> >Bibby, David
> >Sent: 4. februar 2004 12:57
> >To: SAP-WUG at MITVMA.MIT.EDU
> >Subject: Re: Task Stuck In Process
> >
> >
> >Michael
> >Thanks for your advice.
> >If I run it again, it runs and completes.
> >However, looking in SM58 there are entries in here for the workflows
>that
> >are stuck in process.
> >It says  "Object is blocked....<billing document no.>" Trans VF01 Prog
> >RSM13000.
> >Maybe the data the RSNAST00 needs is locked and a return code is not
>being
> >returned.
> >
> >Many Thanks
> >David
> >
> >
> >-----Original Message-----
> >From: Michael Pokraka [mailto:workflow at quirky.me.uk]
> >Sent: 04 February 2004 11:16
> >To: SAP-WUG at MITVMA.MIT.EDU
> >Subject: Re: Task Stuck In Process
> >
> >
> >Hi David,
> >Can you reproduce it - i.e. if you reexecute the same task with the
>same
> >data
> >does it still get stuck? If so it's likely something with your report.
> >Otherwise check for short dumps or stuck TRFC's (SM58).
> >Cheers
> >Mike
> >
> >--- "Bibby, David" <david.bibby at Linklaters.com> wrote:
> > > I have a single step task that intermittently gets stuck In Process.
> > > This step calls our own copy of report RSNAST00 and takes input
> >parameters.
> > > Has anyone had a similar problem calling a report in background and
>the
> >task
> > > getting stuck in process and if so, what did you do to solve the
>problem
> >?
> > >
> > > This one is difficult to debug as the problem only occurs a small
> >percentage
> > > of the time.
> > >
> > > Thanks
> > > David
> > >
> > >
> > > ________________________________________________
> > > This message is confidential. It may also be privileged or
> > > otherwise protected by work product immunity or other legal
> > > rules. If you have received it by mistake please let us know
> > > by reply and then delete it from your system; you should not
> > > copy the message or disclose its contents to anyone. All
> > > messages sent to and from Linklaters may be monitored to
> > > ensure compliance with internal policies and to protect  our
> > > business.
> > >
> > > Please refer to http://www.linklaters.com/regulation for
> > > important information on the regulatory position of the firm.
> > >
> > >
>
>_________________________________________________________________
>It's fast, it's easy and it's free. Get MSN Messenger today!
>http://www.msn.co.uk/messenger
 
_________________________________________________________________
Stay in touch with absent friends - get MSN Messenger
http://www.msn.co.uk/messenger