Microsoft KB Archive/316305

= Send Error Report Dialog Box Is Not Displayed in Windows Server 2003 =

PSS ID Number: 316305

Article Last Modified on 12/18/2003

-

The information in this article applies to:


 * Microsoft Windows Server 2003, Standard Edition
 * Microsoft Windows Server 2003, Enterprise Edition
 * Microsoft Windows Server 2003, Datacenter Edition
 * Microsoft Windows Server 2003, 64-Bit Enterprise Edition
 * Microsoft Windows Server 2003, 64-Bit Datacenter Edition
 * Microsoft Windows Small Business Server 2003, Premium Edition
 * Microsoft Windows Small Business Server 2003, Standard Edition

-



This article was previously published under Q316305



IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



SYMPTOMS
If you experience a fatal program error (for example, an access violate error) on a Windows Server 2003-based server, the Send Error Report dialog box is not displayed. You can use the Send Error Report dialog box to send a debug report to Microsoft. If you experience a fatal program error, the programs may either disappear silently or suddenly stop running for no apparent reason.



CAUSE
This behavior can occur if the ForceQueueMode registry value in the following registry key is set to 1:

HKEY_LOCAL_MACHINE\Software\Microsoft\PCHealth\ErrorReporting

The ForceQueueMode registry value controls the Send Error Report functionality. If this value is set to 1 (the default setting), the Send Error Report dialog box is not displayed until an administrator logs back on to the server if a fatal program error occurs on a program that does not have its own exception handler. Programs such as Microsoft Office XP, MSN Explorer, and Microsoft Visual Studio .NET have their own exception handlers that create the program's specific error reporting dialog box.



RESOLUTION
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To resolve this behavior, use either of the following methods:  Edit the registry:  Start Registry Editor (Regedt32.exe). Locate and click the following registry key:

HKEY_LOCAL_MACHINE\Software\Microsoft\PCHealth\ErrorReporting

 Set the ForceQueueMode registry value to 0.  Change the settings in the System tool:  Click Start, point to Settings, and then click Control Panel.</li> Double-click System, and then click the Advanced tab.</li> Click Error Reporting, and then click to select the Force queue mode for program errors check box.</li></ol> </li></ul>

<div class="status_section">

STATUS
This behavior is by design.

<div class="moreinformation_section">

MORE INFORMATION
If a process stops because of an access violation, the only reason for the process to be displayed in the process list is so that the Send Error Report dialog box can be displayed. Typically, you are not constantly working on the server console if you are an administrator, and the Send Error Report dialog box may go unnoticed. Therefore, the faults are queued and the faulting process is terminated. When you log on to the server, the Send Error Report dialog box is displayed, and you can send the report of the fault to Microsoft.

The ForceQueueMode registry value does not exist in Windows XP Professional or Windows XP Home Edition by default. If you experience a fatal program error (for example, an access violate error) for any program on a Windows XP-based computer, the Send Error Report dialog box is immediately displayed, and you can send the debug report to Microsoft.

You can add the ForceQueueMode registry value to Windows XP. If you do so, the program faults are queued until you log on again. You cannot use the System tool to configure the error queue mode (as described in the &quot;Resolution&quot; section of this article); you must use Registry Editor if you want to change the default setting for the ForceQueueMode registry value.

Keywords: kbprb KB316305

Technology: kbSBServ2003Pre kbSBServ2003Search kbSBServ2003St kbSBServSearch kbWinServ2003Data kbWinServ2003Data64bit kbWinServ2003Data64bitSearch kbWinServ2003DataSearch kbWinServ2003Ent kbWinServ2003Ent64bit kbWinServ2003Ent64bitSearch kbWinServ2003EntSearch kbWinServ2003Search kbWinServ2003St

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© 2004 Microsoft Corporation. All rights reserved.