I disabled those filters but the arrecond process is still running and trying to promote my personal sandbox changes. I've gone so far as purging all records that were in my sandbax (BMC.AE.SB.<USERID>.1).
From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Matt Worsdell Sent: Monday, November 30, 2009 3:06 PM To: [email protected] Subject: Re: Atrium 7.6 Promote Sandbox Changes after server restart. ** ASI:SHR:SandboxCallReconEngine_999 From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of DCI Remedy Sent: 30 November 2009 8:56 PM To: [email protected] Subject: Re: Atrium 7.6 Promote Sandbox Changes after server restart. ** You wouldn't happen to know which filter? On Mon, Nov 30, 2009 at 12:07 PM, Matt Worsdell <[email protected]> wrote: ** If you are running Sandbox, and have made changes to a CI which then appears in the Sandbox, there is an OOTB filter which triggers the Sandbox Recon job. From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of DCI Remedy Sent: 30 November 2009 6:18 PM To: [email protected] Subject: Atrium 7.6 Promote Sandbox Changes after server restart. ** Hi List Just a quick question. Does anyone know why after a server restart, Atrium trys to promote Sandbox changes even though I didn't initiate it. Is there a way to cancel this process? Thanks Edward _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
