Here is our environment: Server OS: Windows 2003 ARS Version: 7.0.01 patch 001
On 3/18, we upgraded from version 6.3, patch 20. These first two weeks in production of the new server software we've been experiencing degradation of server performance. At first, it was barely noticeable as we perform actions such as submits, queries, and making changes to an active link or filter. But the gradual degradation eventually reached the point where twice last week and once this week (3/21, 3/23, and 3/27) the Remedy server service crashed and we were forced to reboot the server. Several observations: 1. There hasn't been any critical changes to any workflow. The reference above to changing an active link or filter was merely turning it on or off to test response times upon saving. 2. Just before the 3/21 crash, the memory used by the ARServer service was in the high 400 MBs and for the ARPlugin service it was in the 120MB range. Following a restart of the ARService it shrunk down to 382 MB and 23 MB, respectively. In the time that followed both services began to grab more and more memory with similar memory usage levels just before the other two crashes. We did not see this in our production environment before the upgrade. Additionally, our test and dev environments, which are duplicates of production, are also stable. 3. The arerror.log is recording the following at crash time: "Fri Mar 23 08:38:41 2007 390695 : AR System server terminated -- fatal error encountered (ARNOTE 21) Fri Mar 23 08:38:41 2007 390695 : AR System server terminated when a signal/exception was received by the server (ARNOTE 20) Fri Mar 23 08:38:41 2007 0xe06d7363" 4. Additionally, the MS Server Event Logs for our production server has a recurring Application Error message, which varies a bit, but is relatively consistent in language, and has persisted since the upgrade to 7. An example of the message is as follows: "Faulting application arplugin.exe, version 7.0.1.1, faulting module arfcbdata.dll, version 5.6.0.0, fault address 0x000056ea. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp."; We have been in contact with support on this. We have a temporary fix in place that will automatically recycle the arserver process during the overnight hours. Has anybody else run into this? I appreciate your help. Joe Kasell Network Management Integrator Telecommunications Division Navy Federal Credit Union _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
