Цитата:
Сообщение от
novic
Как определить причину, почему упал AOS ?
DAX2009
сейчас общаюсь с англоязычной поддержкой Microsoft EMEA - и вот что они советуют по этому вопросу:
Цитата:
1) You could install the Debug Diagnostic Tools 1.2. This is a GUI tool that will set up a service to monitor the AOS. If the AOS crashes, it will dump all the application memory into a file and we can review this. I will add details on how to install and configure it below.
2) Another way would be to configure the built-in Windows Error Reporting (WER) to monitor the AOS. Please be aware that WER is only available in Windows Server 2008 (R2).
далее еще была доп инфа про WER (иначе его информативность близка к нулю):
Цитата:
You are right, that the standard WER messages do not supply enough info. But we have the option to set a new registry key which will cause WER to specifically monitor the AOS service and create a crash memory dump file (like DD 1.2 would) in case that the AOS service stops with an error.
For this you will have to create a registry key and then restart the whole machine, though. That is the reason why I would prefer to use DD 1.2 instead.
You can find info on this here:
http://blogs.msdn.com/b/emeadaxsupport/archive/2010/05/12/possibilities-to-create-memory-dumps-from-crashing-processes.aspx
How to configure WER to create a memory dump of a crashing AOS service:
You have to create the following registry key in order to monitor the AOS service:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Windows Error Reporting\LocalDumps\Ax32Serv.exe
In addtion to that you will have to define the following value keys below this registry key:
- DumpFolder (Define the patch where the dump files should be created, e.g. %LOCALAPPDATA%\CrashDumps)
- DumpCount (Should be configured to 3-5. Once the number of dumps in the DumpFolder location exceed this value, the oldest will be replaced)
- DumpType (Please configure to value 0. 0 = Custom dump, 1 = Mini dump, 2 = Full dump)
- CustomDumpFlags (If DumpType is configured to 0, please set this value to 7015 decimal or 0x1B67 hexadecimal)
Additional info on this can be found in the following MSDN article:
http://msdn.microsoft.com/en-us/library/bb787181(VS.85).aspx