<div>Hello Nash,</div>
<div> </div>
<div>Which version of SAP you are on?</div>
<div> </div>
<div>If you are in ECC 6+ Did you use any Blocks/Forks in your workflow ? .</div>
<div> </div>
<div>As Rick has suggested, try doing some dummy changes like change of descriptiosn etc. in DEV system and see if you have any issues in working with it in DEV.</div>
<div> </div>
<div>Before you do it, Please take an XML version in both 0.4 and Internal XML formats into your desktop ( Either from SWDD or PFTC ) .</div>
<div> </div>
<div>Because, if you are facing this issue in QAS you may very well face it in DEV too in future.</div>
<div> </div>
<div>Regards</div>
<div>Kesari.<br><br></div>
<div class="gmail_quote">On Fri, Nov 19, 2010 at 3:40 AM, Rick Bakker <span dir="ltr"><<a href="mailto:rbakker@gmail.com">rbakker@gmail.com</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">I would make another (dummy) change in DEV and transport it again.<br>
<div>
<div></div>
<div class="h5"><br>On Fri, Nov 19, 2010 at 6:05 AM, Sheldon Oxenberg <<a href="mailto:soxenber@csc.com">soxenber@csc.com</a>> wrote:<br>> Here are some things that you can try:<br>><br>> 1. Open the transport log, expand all sections, and look for any clues as<br>
> to what went wrong or what did not activate properly?<br>> 2. Use transaction SWUD (Workflow diagnosis) > Test environment ><br>> Consistency checks?<br>> 3. In transaction PFTC_DIS, select menu item Goto > Workflow Builder ><br>
> Choose version, and review the version history, status, and active version?<br>> 4. While transaction SWDD is clocking and you are waiting, find your<br>> system process id in transaction SM50, select Program > Debugging, and see<br>
> what SWDD is doing while it is clocking?<br>><br>> Regards.<br>><br>> SHELDON OXENBERG<br>> System Architect Principal Leader<br>> LMP Technical Architect, SAP Workflow<br>> CSC<br>><br>><br>
><br>> From: Nash John <<a href="mailto:emailtonash@gmail.com">emailtonash@gmail.com</a>><br>><br>> To: "SAP Workflow Users' Group" <<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>><br>
><br>> Date: 11/18/2010 01:31 PM<br>><br>> Subject: Re: SWDD- Unable to open workflow- Urgent :(<br>><br>><br>><br>><br>><br>><br>> This workflow is up and running in Production for few years without any<br>
> issue. Recently I had to add a new step to workflow and I did that<br>> in Development system after generating version. Then I transported it to<br>> QAS and issue started happening.<br>><br>> Ever open it before or just now occurring? Did you activate any tasks when<br>
> it hit QAS? Test it in Q?- YES<br>><br>> know you say 'we' can open other WFs but can someone else open this one?-<br>> OTHERS TOO UNABLE TO OPEN THIS PERTICULAR WF.<br>><br>> Thank you all for replying to my post.<br>
><br>><br>> On Thu, Nov 18, 2010 at 12:46 PM, Sample, Rick <<a href="mailto:Rick.Sample@graybar.com">Rick.Sample@graybar.com</a>><br>> wrote:<br>> No issues when you transported it … Transport logs?<br>
><br>><br>><br>><br>><br>> Ever open it before or just now occurring? Did you activate any tasks<br>> when it hit QAS? Test it in Q?<br>><br>><br>><br>><br>><br>> Nothing I can think of should stop you from at least opening up the WF.<br>
> Compile / activate is another story.<br>><br>><br>><br>><br>><br>> I know you say 'we' can open other WFs but can someone else open this<br>> one?<br>><br>><br>><br>><br>><br>
> Rick Sample<br>><br>><br>><br>><br>><br>> From: <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a> [mailto:<a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a>] On Behalf<br>
> Of Nash John<br>> Sent: Thursday, November 18, 2010 11:32 AM<br>><br>><br>><br>> To: SAP Workflow Users' Group; <a href="mailto:sap-wug-request@mit.edu">sap-wug-request@mit.edu</a><br>> Subject: SWDD- Unable to open workflow- Urgent :(<br>
><br>><br>><br>><br>><br>> Hi Freinds,<br>><br>><br>><br>><br>><br>> We are unable to open one particular workflow either through SWDD or<br>> PFTC. The workflow is a copy of standard workflow and opens fine in<br>
> Production and Development systems. Issue is only when we try to open it<br>> in QAS system.<br>><br>><br>><br>><br>><br>> Basically SWDD times out when we try to open this workflow. We are able<br>
> to open other workflows usinf SWDD<br>><br>><br>><br>><br>><br>> Any help would be really appreciated.<br>><br>><br>><br>><br>><br>> Thank you<br>><br>><br>><br>><br>
><br>> Nash<br>><br>> _______________________________________________<br>> SAP-WUG mailing list<br>> <a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>> <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
><br>> _______________________________________________<br>> SAP-WUG mailing list<br>> <a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>> <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
><br>><br>> _______________________________________________<br>> SAP-WUG mailing list<br>> <a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>> <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
><br><br>_______________________________________________<br>SAP-WUG mailing list<br><a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
</div></div></blockquote></div><br>