Thanks Joe, I already have narrowed this down to the Email Message form. When sending an outgoing message it times out.
Rafael From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Joe Martin D'Souza Sent: Thursday, April 07, 2011 12:44 AM To: arslist@ARSLIST.ORG Subject: Re: 7.6.4 Upgrade ** It just may be possible that when a notification is created, that process runs a search over some form that is timed out?? I would take a workflow log and a SQL log when reproducing the condition that leads to this time out which may give you a clue to what search operation times out. Joe From: Rodriguez, Rafael J x23718<mailto:rafael.rodrig...@broadridge.com> Sent: Wednesday, April 06, 2011 2:11 PM Newsgroups: public.remedy.arsystem.general To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> Subject: Re: 7.6.4 Upgrade Thanks Joe, I have checked this already and we have enough space available. In working with BMC it appears that the AR Server is terminating while trying to do a filter notify action. Interesting if I disable filter that is trying to send notification the timeout issue is resolved. I tried creating a brand new notify filter and timeout is back. So it appears that for some reason after the upgrade the system crashes when trying to send out notification. Rafael From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Joe Martin D'Souza Sent: Wednesday, April 06, 2011 12:44 AM To: arslist@ARSLIST.ORG Subject: Re: 7.6.4 Upgrade ** First and foremost check your log files to see what may be going on.. Having said that here are a few tips to check certain things that could reduce your performance to the level its at.. Check the size of the transaction log file, and flush it. SQL server 2000 onwards does manage it automatically, with auto growth enabled, but maybe something is choking it? Make sure the disks where the log and data files of the AR System database reside have a healthy amount of free space.. Also check your disk space on the AR Server, sometimes log files if enabled and left enabled can grow large enough to fill up the disk, and this can choke the AR Server as it does require a significant of free disk space to run.. Hope this helps.. Cheers Joe From: LJ LongWing<mailto:lj.longw...@gmail.com> Sent: Tuesday, April 05, 2011 9:55 AM Newsgroups: public.remedy.arsystem.general To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> Subject: Re: 7.6.4 Upgrade ** Rafael, I recommend turning on API/Filter/SQL logging on the server and analyzing the timings of each call with something like AR Workflow Analyzer…it’ll tell you what api/sql calls took the longest and you can analyze from there to find out why…..the message in general just means that the client asked for a process and the server took longer than 2 min’s to respond….that’s ALL it means…it’s up to you to figure out why it took so long. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Rodriguez, Rafael J x23718 Sent: Tuesday, April 05, 2011 7:14 AM To: arslist@ARSLIST.ORG Subject: 7.6.4 Upgrade ** Hello list, I have recently upgraded to 7.6.4 from 7.5 Patch 7. Now when I try to submit I get the following timeout message: ARERR [92] Timeout during database update -- the operation has been accepted by the server and will usually complete successfully NOTE: The request does get created but I keep getting this. Has anyone experience this? ARS: 7.6.4 Server: Win 2008 DB: SQL 2008 Rafael _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
