TestWER (Test Windows Error Reporting)
Article ID: CTX111901
Updated On:
Description
TestWER (Test Windows Error Reporting)
Version 2.0
Created Date: 12/06/2006
Updated Date: 02/02/2011
Where to download ?
Certain legacy Citrix tools are now available on request only. Please submit the request here - https://forms.gle/obA39PEz5qpDiSPq8
Once we verify your request, we will provide access to the download location.
Description
The TestWER (former TestDefaultDebugger) forces a crash on itself to test the presence and configuration of the default postmortem debugger (Dr. Watson, NTSD, or other) and/or Windows Error Reporting (WER). If the default debugger or WER is configured properly, the operating system launches it to save a dump of the TestWER.exe process.
Features:
• GUI and command line interfaces
• 32-bit and 64-bit executables to test 32-bit and 64-bit postmortem debuggers
• Additional .NET executable to test CLR exception handling
• New for version 2.0: ability to generate software exceptions (C++ exception via RaiseException) and an option to handle generated exceptions to test tools saving first-chance exception crash dumps
To configure a default postmortem debugger please refer to CTX105888 - How to Set the NT Symbolic Debugger as a Default Windows Postmortem Debugger. To configure WER to save full user crash dumps automatically please refer to CTX118614 - How to Use Windows Error Reporting (WER) to capture Application Crash Dumps (User Dumps) on Windows Server 2008, Windows Vista, and Windows 7.
Installing TestWER
Download the archive file to a local workstation, unzip it, and run TestWER.exe or TestWER64.exe from a command prompt or from within a session.
How to Use TestWER (GUI interface)
- Run TestWER.exe or TestWER64.exe on your workstation and/or inside the session desktop.
- Click the TestWER icon button:
- A postmortem debugger or WER saves a user crash dump. For example, if NTSD is set as a default postmortem debugger, we will see it saving a crash dump in a separate console window:
How to Use TestWER (Command line interface)
1. Command line syntax:
TestWER.exe now
-Or-
TestWER64.exe now
2. Remote execution example using PsExec.exe tool from www.sysinternals.com:
C:\tools\PsExec>psexec \\SERVER -u Administrator -p <password> -w c:\TestWER c:\TestWER\TestWER.exe now
Uninstalling TestWER
To uninstall this tool, delete executable files.
Disclaimer
These software applications are provided to you as is with no representations, warranties or conditions of any kind. You may use and distribute it at your own risk. CITRIX DISCLAIMS ALL WARRANTIES WHATSOEVER, EXPRESS, IMPLIED, WRITTEN, ORAL OR STATUTORY, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NONINFRINGEMENT. Without limiting the generality of the foregoing, you acknowledge and agree that (a) the software application may exhibit errors, design flaws or other problems, possibly resulting in loss of data or damage to property; (b) it may not be possible to make the software application fully functional; and (c) Citrix may, without notice or liability to you, cease to make available the current version and/or any future versions of the software application. In no event should the code be used to support of ultra-hazardous activities, including but not limited to life support or blasting activities. NEITHER CITRIX NOR ITS AFFILIATES OR AGENTS WILL BE LIABLE, UNDER BREACH OF CONTRACT OR ANY OTHER THEORY OF LIABILITY, FOR ANY DAMAGES WHATSOEVER ARISING FROM USE OF THE SOFTWARE APPLICATION, INCLUDING WITHOUT LIMITATION DIRECT, SPECIAL, INCIDENTAL, PUNITIVE, CONSEQUENTIAL OR OTHER DAMAGES, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. You agree to indemnify and defend Citrix against any and all claims arising from your use, modification or distribution of the code.
More Information
CTX105888 – How to Set the NT Symbolic Debugger as a Default Windows Postmortem Debugger
