Generally, in the approval logs, the section that reports an error will say why. Can you post that portion of the logs?
Axton Grams The opinions, statements, and/or suggested courses of action expressed in this E-mail do not necessarily reflect those of BMC Software, Inc. My voluntary participation in this forum is not intended to convey a role as a spokesperson, liaison or public relations representative for BMC Software, Inc. On Wed, May 6, 2009 at 12:44 PM, Pierson, Shawn <shawn.pier...@sug.com>wrote: > ** > > Axton, > > > > Thanks for the response. I just re-read my original post and I think I > worded it incorrectly. > > > > I’ll give more information here. I can see where in the log the approval > is being set to Closed, and that it says it is cleaning up the other > approvals on that change and setting them to Error (even though the status > becomes “Closed”), but I can’t see what is causing that to happen because it > looks like it is proceeding normally. What makes it worse is that there is > nothing I can reproduce, as these approval processes and approvers are able > to successfully approve things most of the time. > > > > Thanks, > > > > Shawn Pierson > > > > *From:* Action Request System discussion list(ARSList) [mailto: > arsl...@arslist.org] *On Behalf Of *Axton > *Sent:* Wednesday, May 06, 2009 12:23 PM > *To:* arslist@ARSLIST.ORG > *Subject:* Re: Approval Engine 7.1 Issues > > > > ** When looking at the approval logs, you need to know the 'Approval ID' > (from AP:Detail) and the Signature ID's (from AP:Signature) as well as the > Request ID (from the entry that has the approval process tied to it). > Something is setting it to closed, which I would wager is one of the > following: > > - The approval engine > - Workflow > - A user > > Check the logs for those three areas and you should find your answer. > > In the approval logs, find the place where the Detail record is created; > the find the place where the signature lines are created. > > Axton Grams > > The opinions, statements, and/or suggested courses of action expressed in > this E-mail do not necessarily reflect those of BMC Software, Inc. My > voluntary participation in this forum is not intended to convey a role as a > spokesperson, liaison or public relations representative for BMC Software, > Inc. > > On Wed, May 6, 2009 at 8:38 AM, Pierson, Shawn <shawn.pier...@sug.com> > wrote: > > ** > > Has anyone else run into issues where approval processes that normally > function fine on 7.0 don’t work correctly maybe 5% of the time on 7.1? > > > > We are having approval requests randomly put in a “Closed” status by the > approval engine, which is wreaking havoc on our Change Management process. > We haven’t made any changes other than upgrading to 7.1 patch 6, and BMC > support is being as “useful” as can be expected. > > > > By the way, I have enabled approval logging, but find nothing to show these > specific approvals being marked as Closed. > > > > Thanks, > > > > *Shawn Pierson * > > Remedy Developer | Southern Union > > > > > > Private and confidential as detailed > here<http://www.sug.com/disclaimers/default.htm#Mail>. > If you cannot access hyperlink, please e-mail sender. > > _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers > Are"_ > > > _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers > Are"_ > Private and confidential as detailed > here<http://www.sug.com/disclaimers/default.htm#Mail>. > If you cannot access hyperlink, please e-mail sender. > _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers > Are"_ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"
