Now that we are using version 7 where I can set a character field to Drop-down instead of Edit mode I've found that I have no use for the menu pattern match any longer. It never worked quite right with search menus anyway and this new method works great. -Rick
________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Morrison, David A. Sent: Wednesday, December 03, 2008 9:18 AM To: [email protected] Subject: Re: Menu match stopped working after bouncing service ** This seems to be a popular bug. I ran into this yesterday myself. I had an issue on a form where I could not get three character fields to display. I tried everything I knew but could not get them to show up. I then imported the form def file again and they still would not display. Then all of a sudden I was getting calls saying two "different" forms were not being saved and were giving the MENU pattern error. Could not find anything in the logs to help. I went ahead and disabled the Menu attribute for the fields in question and that allowed the forms to be saved. I went to the BMC site to search for this bug, but the Knowledge Base search just locks up this morning. L I have found several posts on this list concerning this issue. I am not using ITSM either. I also remember running into this problem back in version 3.1.2. Again, just took the MENU attribute off. Concerning the original issue I had: I finally was able to get the fields to display by clicking on the spot where they were located and when the cursor switched to the sizing arrows, I clicked on it and the field suddenly appeared. I resized it and did the same to the other two fields and saved the form. I was then able to see them in the user client. However, I added some boxes on the form, and now they are not showing up. L It seems as though it is defaulting to hidden for no apparent reason?? VM Virtual server OS: Windows 2003 R2 Database: MS SQL Server 2005 (Remote) AR Server 7.1.00 patch 4 Mid-Tier 7.1.00 hosted on IIS 6 and Tomcat 5.5 servlet engine. AR Client 7.1.00 patch 4 David Morrison Remedy Administrator East Tennessee State University From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Matthew Perrault Sent: Wednesday, December 03, 2008 9:39 AM To: [email protected] Subject: Re: Menu match stopped working after bouncing service ** Rick, Nyall, We had and still have that issue on our Development and Test environments. We are running ITSM 7 which uses a lot of memory. I wonder if what Nyall wrote below is why we see it? It will be fine for a couple of weeks and then suddenly every form that has that (foundation has it everywhere) $MENU$ pattern matching will fail. We end up rebooting the server. There was/is a defect reported on this: ISS03247553 SW00284075 But BMC closed it because they said they couldn't reproduce it. Thanks, Matthew Perrault SIM Team Remedy Developer 763-764-2423 Click to contact the Service Desk or Make a Computer Related Request <http://infosys.genmills.com/Remedy/customerPortal.asp> From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Nyall McCavitt Sent: Wednesday, December 03, 2008 12:05 AM To: [email protected] Subject: Re: Menu match stopped working after bouncing service ** 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: ** Yesterday I was having some odd performance issues with my Mid-tier users and eventually my Admin tool kept locking up whenever I tried to open any form on my production server (7.0.1 p6 on Windows). I ended up bouncing the service and then for some reason all of my character fields that had the $MENU$ pattern match set refused to actually match anything. I had one user call me about a field on one particular form so I removed the pattern match and changed the field from Edit to Drop-Down (now that all the clients have been upgraded to version 7). Then a few hours later a different user reported the same problem on a field in a different form. By early this morning I had 3-4 other fields reported with the same problem. The pattern match on all of these fields worked fine before, does anybody have any idea why the $MENU$ pattern match would suddenly fail globally across multiple fields on multiple forms? I ended up exporting a full definition file and doing a search for the string "pattern : $-107$" which let me find all the remaining fields with the menu pattern match so that I could proactively fix those before getting user complaints. -Rick _________________________________ Rick Westbrock PETCO Telecom Engineer [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
