You didn't mention what kind of configuration you're using. for example: - Is your DB local or remote?
- Are there other databases using the same server? - What is your thread allocation like? - Are there scheduled or adhoc reports running against IM? - Are you updating your DB statistics regularly? - Have you modified the IM indexing at all? Just a few questions that come to mind. J Thanks & good luck! Matt R. From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Koyb P. Liabt Sent: Thursday, September 11, 2008 10:43 AM To: arslist@ARSLIST.ORG Subject: Incident Management 7.x Slow ** Hello all, We are on ITSM 7.0.3, patch 7. We are having issues with the Incident Management application only. When the user presses SAVE to create the ticket - it takes 5 minutes to process the transaction, and then the error message comes back and says: ARERR [92] Timeout during database update -- the operation has been accepted by the server and will usually complete successfully : server XYZ The process does not hang when submitting tickets via Asset, or Change Management. I generated logs and nothing jumped out. I noticed the latency happens when modify an incident record ticket also. Is there some bug with Incident Management? _____ Looking for spoilers and reviews on the new TV season? Get <http://television.aol.com/feature/fall_tv?ncid=aoletv00050000000037> AOL's ultimate guide to fall TV. __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"
