I did turn on the server logs too. Still nothing being capture on the failure. BMC is also trying to figure this one out. But this is impacting our entire Helpdesk and we need all the help we can get Thank you,
Pascale Boyer Remedy Developer Daimler Trucks North America MP9 Portland, OR 503-745-8712 lj.longw...@gmail.com Sent by: arslist@ARSLIST.ORG 05/18/2009 10:02 AM Please respond to arslist@ARSLIST.ORG To arslist@ARSLIST.ORG cc Subject Re: API Call not being made ** Due to the fact that the client is timing out, it's never updating its logs...so to capture what's happening on this one you will need to turn on server logging to capture what's happening. Something on the server is taking more than the client (hard coded) 2 min timeout....so when you turn on server logging and perform the same action you should be able to see a bit more what's happening, and hopefully capture something in the logs that will lead you a bit further down the road. From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of pascale.bo...@daimler.com Sent: Monday, May 18, 2009 10:41 AM To: arslist@ARSLIST.ORG Subject: API Call not being made ** Hi all, Hope someone has a clue about this one... We are experiencing a sudden breakage on our production server. And as usual, no one did anything, nothing was changed by no one on the system, the server, the OS or the DB or the DB server... But this is what is going on. We have a basic workflow that does the following: Active link execute on Return on field Action: push field to from B Filter on form B Execute on Submit Consume web services. The results: arerr 92 time-out at the database ... server busy ... etc This is not happening once in a while, but constantly now. I ran the API, SQL and Filter logs If I compare the logs of working and not working with the exact same value being used, this is what I get: I see the AL being launched the push field started then nothing, not even the API CE being made. The system seems to go dead (timing out after 2 minutes) and returning the error 92. This is only happening on workflow pushing data to form B. The DBA checked the integrity of the tables (T, B H) and says that everything is fine there nothing. This is a tiny table of barely 2000 records. Since the DB itself was running low on memory (200Mb), we added 2 Gb this weekend. Still not working. Any one has a clue on where to look now? we are on AR 7.0.1 patch 003 WIN XP server MSSQL2005 DB on a WIN XP server Thank you, Pascale Boyer Remedy Developer Daimler Trucks North America MP9 Portland, OR 503-745-8712 If you are not the intended addressee, please inform us immediately that you have received this e-mail in error, and delete it. We thank you for your cooperation. _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers Are"_ _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers Are"_ If you are not the intended addressee, please inform us immediately that you have received this e-mail in error, and delete it. We thank you for your cooperation. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"