Article ID: 1320, created on Mar 30, 2009, last review on Aug 12, 2014

  • Applies to:
  • Plesk 12.0 for Windows
  • Virtuozzo containers for Windows

Consulta

¿Cómo puedo habilitar la generación de informes de la aplicación para poder capturar un volcado de un proceso con errores?

Respuesta

Servidores Windows 2003:

Inicie el siguiente servicio:

Error Reporting Service

Este servicio recopila, almacena e informa acerca de bloqueos o errores inesperados en Microsoft. Si se detiene este servicio, sólo se generarán informes de error para errores del kernel y para algunos tipos de errores en modo de usuario. Si se desactiva este servicio, no podrá iniciarse cualquier servicio que dependa de este de forma explícita.

Para activar este servicio, vaya al Panel de control > Herramientas administrativas > Servicios. En la lista de servicios, seleccione Error Reporting Service y seleccione la opción "Iniciar".

El informe de error se guardará en el siguiente directorio:

C:\WINDOWS\PCHEALTH\ERRORREP\UserDumps

Si no se crean volcados de memoria, le recomendamos configurar el servicio de la siguiente forma: cree un archivo *.reg, copie y pegue la configuración de registro que puede ver a continuación e importe el archivo al nodo hardware.

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

Servidores Windows 2008 [R2]:

Le recomendamos seguir las indicaciones que se detallan en el siguiente artículo de MSDN (EN):

Collecting User-Mode Dumps

A continuación encontrará un fragmento de dicho artículo:

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.

965b49118115a610e93635d21c5694a8 d02f9caf3e11b191a38179103495106f 2897d76d56d2010f4e3a28f864d69223 a914db3fdc7a53ddcfd1b2db8f5a1b9c 56797cefb1efc9130f7c48a7d1db0f0c ed7be2b984f9c27de1d2dc349dc19c6d 85a92ca67f2200d36506862eaa6ed6b8 a766cea0c28e23e978fa78ef81918ab8

Email subscription for changes to this article
Save as PDF