You should try and get BMC to provide you with a debug version of arserverd (arserver.exe). The debug version should perform a memory dump that contains all the symbols necessary for debugging. BMC should then be able to use your memory dump to isolate the issue. I could see valid justification in BMC asking you to update to the latest (debug) patch for this though.
In the past, I've tracked these types of things down to specific form/field/workflow properties, and this will be an incremental step in attaining a fix from BMC. Something is happening, somewhere, that is causing this. Turn on the api logs with the overwrite option. Grab the last log after a crash and save a copy, it should point you to the right place to reproduce the issue. Axton Grams Heider, Stephen wrote: > I periodically see these errors in the arerror.log file. ARS apparently > restarts its NT service and continues functioning normally. There have > been no error messages popping up on client computers. I have log files > running but have not seen any correlation between workflow and this > particular error. The error message below is the exact text each time. > > Because there has been no sign of any problems caused by this error I am > not overly concerned. However, no errors are better than some errors. > Has anyone seen this before and is there a known fix or workaround? > > ------------------------------------------------ > Thread Id: 3660 > Version: 6.03.00 patch 016 Jan 20 2006 23:48:41 > Code: c0000005 > Operation: read > Access Addr: 00000001 > Stack Begin: > Addr: 005D6D38 > Addr: 093DCF78 > Stack End: > ------------------------------------------------ > > ARS 6.3 p16 > Windows Server 2003 > SQL Server 2000 > > > Stephen > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
