[How To] How to enable application report generation

Refers to:

  • Plesk 12.0 for Windows

Created:

2016-11-16 12:42:20 UTC

Modified:

2016-12-21 19:01:05 UTC

0

Was this article helpful?


Have more questions?

Submit a request

[How To] How to enable application report generation

Question

How can I enable Application Report Generation to capture dump of a crashed process?

Answer

Windows 2003 servers:

You have to start the following service:

Error Reporting Service

This service collects, stores, and reports unexpected application crashes to Microsoft. If this service is stopped, then Error Reporting will occur only for kernel faults and some types of user mode faults. If this service is disabled, any services that explicitly depend on it will not start.

To enable this service, go to Control Panel > Administrative Tools > Services . From the list of displayed services, select the Error Reporting Service and select the " Start " option.

The error report will be saved in the following directory:

C:\\WINDOWS\\PCHEALTH\\ERRORREP\\UserDumps

If memory dumps are not created, it is recommended to configure the service as follows: create *.reg file, copy/paste the registry settings below, and import the file on the HW Node.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\AeDebug]
"Auto"="1"
"Debugger"="drwtsn32 -p %ld -e %ld -g"
"UserDebuggerHotKey"=dword:00000000

[HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\DrWatson]
"VisualNotification"=dword:00000001
"CreateCrashDump"=dword:00000001
"CrashDumpType"=dword:00000002
"DumpAllThreads"=dword:00000001

Windows 2008 [R2] servers:

It is recommended to follow MSDN article:

Collecting User-Mode Dumps

Below you may find snippet from the article:

Starting with Windows Server 2008 and Windows Vista with Service Pack 1 (SP1), Windows Error Reporting (WER) can be configured so that full user-mode dumps are collected and stored locally after a user-mode application crashes. Applications that do their own custom crash reporting, including .NET applications, are not supported by this feature.

This feature is not enabled by default. Enabling the feature requires administrator privileges. To enable and configure the feature, use the following registry values under the HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\Windows Error Reporting\\LocalDumps key.

These registry values represent the global settings. You can also provide per-application settings that override the global settings. To create a per-application setting, create a new key for your application under HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows\\Windows Error Reporting\\LocalDumps (for example, HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows\\Windows Error Reporting\\LocalDumps\\MyApplication.exe ). Add your dump settings under the MyApplication.exe key. If your application crashes, WER will first read the global settings, and then will override any of the settings with your application-specific settings.

After an application crashes and prior to its termination, the system will check the registry settings to determine whether a local dump is to be collected. After the dump collection has completed, the application will be allowed to terminate normally. If the application supports recovery, the local dump is collected before the recovery callback is called.

These dumps are configured and controlled independently of the rest of the WER infrastructure. You can make use of the local dump collection even if WER is disabled or if the user cancels WER reporting.

Have more questions? Submit a request
Please sign in to leave a comment.