Or you man *think* it's the same active link because it almost looks similar to a human eye. Did you look at your AL log by looking for the AL name by doing a find by the exact name? There must be a sort of a duplicate with a similar name that you are seeing in your logs that is firing?
Or maybe you are disabling it in one environment and testing results in another? Cheers Joe -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of pascale.sterr...@daimler.com Sent: Friday, September 20, 2013 12:01 PM To: arslist@ARSLIST.ORG Subject: Re: A little bit early for Halloween or a little late for Friday the 13th That was one of our first step. And did not change anything. taufc...@gmail.com Sent by: arslist@ARSLIST.ORG 09/20/2013 08:48 AM Please respond to arslist@ARSLIST.ORG To arslist@ARSLIST.ORG cc Subject Re: A little bit early for Halloween or a little late for Friday the 13th It sounds like an issue with the server cache getting jacked up. I wonder what would've happened if you re-enabled the AL. That would force a recache (I think). Tauf Chowdhury > On Sep 20, 2013, at 9:44 AM, "pascale.sterr...@daimler.com" <pascale.sterr...@daimler.com> wrote: > > Hi all, > > This will sound like a Friday joke but it is not > > We just have a little bit of the spooky weird one here. And I wonder if > anyone else had this kind of weird behavior. > I just want to know if there is a step of cache clearing/cleaning we > missed > > We are 100% custom apps. > 7.6.4 SP5 mainly WUT > MSSQL 2005 > Win 2003 > > We are not using Best Practice Mode. So no Overlay > > #1 Weird occurrence: > > My colleague disabled an Active Link. But still it is triggering. In the > logs, we see the AL being triggered. It is the same name but with a bunch > of numbers following the name. If we do a search on Dev studio for that > particular name with those number we can't find it. Just the one without > the numbers. And that one is disabled in both Dev and Best Practice Mode. > > Regardless of restarting the server, closing the WUT and relogin, clearing > the WUT cache, the AL regardless is triggering and showing up in the Logs. > > > #2 occurrence > I deleted an AL (different one). Still in Dev mode. The AL still > triggered. Still showed in the logs. > Regardless of restarting the server, closing the WUT and relogin, clearing > the WUT cache, the AL regardless is triggering and showing up in the Logs. > > But if I looked for it in dev studio it was no longer there. > > #3 > This morning, the deleted AL is no longer showing in the logs and all is > working fine for now... > > > Anyone experienced ghostly AL? > > > Thank you, > > Pascale Sterrett > Kenavo ar wech all > > > If you are not the intended addressee, please inform us immediately that you have received this e-mail in error, and delete it. We thank you for your cooperation. > ____________________________________________________________________________ ___ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years" If you are not the intended addressee, please inform us immediately that you have received this e-mail in error, and delete it. We thank you for your cooperation. ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
