**
Hi, I had this issue with ARS V7.1. There were 2 workarounds that I found for this but these only partially succeeded. The first was to disable the $MENU$ pattern matching on the field concerned. Save the modification then re-apply $MENU$ pattern matching. This obviously only works for small numbers of fields and the problem reappeared after a certain time period. The second option is to stop and restart the Remedy service. Not always practical in a production environment. The final solution was to patch our ARS V7.1 server to patch 5. This resolved the problem which was to due to how the ARS Server was interacting with Oracle. Once a certain memory threshold had been reached then the problem would appear. I think that you should contact Remedy Support and see what patch level for ARS V7.0.1 does not have this issue. Hope that this helps. Nyall Rick Westbrock wrote: ** __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ |
- Menu match stopped working after bouncing service Rick Westbrock
- Re: Menu match stopped working after bouncing serv... Nyall McCavitt
- Re: Menu match stopped working after bouncing ... Matthew Perrault
- Re: Menu match stopped working after bounc... Ben Chernys
- Re: Menu match stopped working after b... Tony Worthington
- Re: Menu match stopped working after bounc... Morrison, David A.
- Re: Menu match stopped working after b... Rick Westbrock