Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 26 Source: ApplicationPopup

Application popup: <application name> - Common Language Runtime Debugging Services : Application has generated an exception that could not be handled.

Process id=<PID in hex> (<PID>) Thread id=<thread in hex> (<thread>).

Click OK to terminate the application.
Click CANCEL to debug the application.
- Application: Add sequence.exe - A home-made VB.NET 1.1 program which had been working failed to start. Investigation found that the shortcut to the program had been changed from "C:\Program Files\My program\Add sequence.exe" to "\\ComputerName\c\Program Files\My program\Add sequence.exe" so the .NET framework was raising a permissions error as it no longer appeared to be on the local computer. Reverting the shortcut fixed the problem.
- Application: miiskmu.exe - This issue may occur if some applications, such as antivirus software, are running. See ME884192 for a hotfix that prevents the MIIS Key Management Utility from crashing.
If Microsoft Visual Studio .NET is installed, then used it to debug the program. If not, then download and install the Microsoft .NET Framework SDK for your version of Windows and use either the command line debugger or the GUI debugger to debug the program.

To use the command line debugger find the path to the file named cordbg.exe in the SDK (mine was in C:\Program Files\Microsoft.NET\SDK\v1.1\Bin). Alternate-click My Computer and click Properties. Click the Advanced tab. Click Environment Variables. In the System variables pane, select Path and click Edit. If the path just identified is not in the string then add it to the end (preceded by a ";") and click OK repeatedly to close all dialog boxes. Repeat the procedure that caused the error and when the Windows dialog box that accompanies this Event ID is displayed click Cancel (to debug the application). A Windows command prompt will be opened in which details of the line in the program that caused the error will be displayed.
To use the GUI debugger find the path to the file named DbgCLR.exe in the SDK (mine was in C:\Program Files\Microsoft.NET\SDK\v1.1\GuiDebug) and run it. On the menu click Debug -> Program To Debug. Enter the full path to the program named in this Event ID and click OK. Press F5 to run the program with debugging. When the “An unhandled exception” dialog box is displayed click Break. If no source code is available for the application then a dialog box will be displayed stating this. Click Show Disassembly. Details of the assembly code instruction that caused the error will be displayed.
Report the problem to the author or supplier of the product. Supply screen shots, etc. as required and wait for a fix. Try another version of the program or look for errors in its input data or configuration.

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to



Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.